From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KTjXC-0004Re-Lh for qemu-devel@nongnu.org; Thu, 14 Aug 2008 16:35:02 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KTjXC-0004RL-1j for qemu-devel@nongnu.org; Thu, 14 Aug 2008 16:35:02 -0400 Received: from [199.232.76.173] (port=46556 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KTjXB-0004RF-Ok for qemu-devel@nongnu.org; Thu, 14 Aug 2008 16:35:01 -0400 Received: from hera.kernel.org ([140.211.167.34]:51445) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1KTjXB-0001UH-6y for qemu-devel@nongnu.org; Thu, 14 Aug 2008 16:35:01 -0400 Message-ID: <48A496E9.2030800@kernel.org> Date: Thu, 14 Aug 2008 13:34:49 -0700 From: Max Krasnyansky MIME-Version: 1.0 References: <48A46033.3070200@codemonkey.ws> <48A489D3.5070900@kernel.org> <48A493DE.40506@codemonkey.ws> In-Reply-To: <48A493DE.40506@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Re: [PATCH 2/5] husb: support for USB host device auto connect. Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org Anthony Liguori wrote: > Max Krasnyansky wrote: >> Anthony Liguori wrote: >> >>> Max Krasnyansky wrote: >>> >>>> Anyway, it's implemented using a periodic timer that scans host devices >>>> and grabs those that match the filter. Timer is started when the first >>>> filter is added. >>>> >>> Again, there has to be a way to get notified of usb device add/remove in >>> Linux. >>> >> >> Yes the best way is probably registering with HAL via dbus. >> > I was afraid you would say that :-) :) >> Do you mind if we do something like that incrementally ? >> > > Yeah, I don't really want to have QEMU depend on dbus so in this case, > polling would be better. I'm thinking that maybe we could use 'inotify' on /proc/bus/usb. Would you be ok with 'inotify' ? Max