From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Edmondson Subject: Re: Re: [Xen-changelog] [xen-3.1-testing] xend: fix server/netif.py so that it respects type=None. Date: Fri, 5 Oct 2007 18:36:22 +0100 Message-ID: <20071005173622.GN1326@enoexec.uk.sun.com> References: <20071005143301.GC1326@enoexec.uk.sun.com> <20071005160656.GC8249@redhat.com> <20071005161635.GG1326@enoexec.uk.sun.com> <20071005173048.GA30405@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20071005173048.GA30405@redhat.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Daniel P. Berrange" Cc: xen-devel@lists.xensource.com, John Levon List-Id: xen-devel@lists.xenproject.org On Fri, Oct 05, 2007 at 06:30:48PM +0100, Daniel P. Berrange wrote: > > The whole "PV and IOEMU" at the same time makes me uncomfortable, > > though it looks to be more problematic with disks than network > > devices. > > The key is that the Dom0 configuration of the guest should allow the > guest kernel to choose the drivers. Understood. > Obviously you don't want both drivers active at once, so one idea is > for the PV drivers to 'grab' the PCI resources associated with the > emulated NIC. That seems so wrong. In Solaris drivers are loaded as a result of a mapping from the PCI ID of the device to a driver name (I've no idea if it's the same in Linux). What happens if the RTL8139 driver gets in first? > So once you load the PV driver, there's no way for the RTL8139 > driver to get access to the NIC, thus ensuring only one is ever > active at once. The same principle applies to disk adapters.