From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rusty Russell Subject: Re: [PATCH 1/3] virtio interface Date: Tue, 25 Sep 2007 20:54:58 +1000 Message-ID: <1190717698.27805.328.camel@localhost.localdomain> References: <1190625194.27805.199.camel@localhost.localdomain> <200709250018.12705.arnd@arndb.de> <1190677058.27805.225.camel@localhost.localdomain> <200709250836.29451.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org, virtualization To: Arnd Bergmann Return-path: In-Reply-To: <200709250836.29451.arnd-r2nGTMty4D4@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org On Tue, 2007-09-25 at 08:36 +0200, Arnd Bergmann wrote: > On Tuesday 25 September 2007, Rusty Russell wrote: > > I don't mind: we could expose it. > > What I mean with setting the parent appropriately is not to have a global > device that is used by the hv-specific probing code, but to make sure > that each of them provides their own one. The bus_type should either be > global or provide the wrappers for device_register and driver_register > that you have, but the host bridge device belongs with the code that > probes it. E.g. when all virtio devices are behind PCI bridges, there > does not need to be an empty /virtio or /lguest device node at all. Right, that makes sense. I'll shift this "virtio" device node out to the lguest code. Thanks! Rusty. ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/