From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yu Zhao Subject: Re: [PATCH] [VTD] Remove PCI device enumeration for dom0 in Xen Date: Wed, 22 Oct 2008 23:39:02 +0800 Message-ID: <48FF4916.9070502@uniscape.net> References: <18687.7900.317457.856048@gargle.gargle.HOWL> <18687.9027.201750.98978@gargle.gargle.HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <18687.9027.201750.98978@gargle.gargle.HOWL> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Espen Skoglund Cc: "Kay, Allen M" , "Zhao, Yu" , xen-devel@lists.xensource.com, "Han, Weidong" , Keir Fraser List-Id: xen-devel@lists.xenproject.org Espen Skoglund wrote: > [Keir Fraser] >> On 22/10/08 13:38, "Espen Skoglund" wrote: > >>>> Xen 3.3 should continue to work with older dom0 kernels. However, >>>> now that iommu is *disabled* by default, will this mean that it >>>> would continue to work with older dom0 kernels so long as iommu is >>>> not enabled on the Xen command line? This should be tested and >>>> confirmed with this patch applied. If so, I would accept it. >>> Users of pci_lock_pdev() and pci_lock_domain_pdev() would not be >>> able to find the PCI device unless it has been registered by dom0. >>> Apart from the iommu code, the only user affected would be the MSI >>> code which looks up the PCI device before enabling MSIs on it. As >>> such, you would not be able to enable MSIs if you have an old dom0 >>> kernel. > >> Is there any disadvantage to keeping this legacy code in Xen, apart >> from it annoyingly sitting there? > > You would get a list of PCI devices in Xen containing entries that are > not necessarily in use. Some of the entries might even be bogus. > Apart from some annoying extra code and additional entries in the > IOMMU page tables, I don't think there is much of a problem. There > could be some potential problems if Xen at a future stage decides to > do some in-hypervisor cleverness with all known PCI devices (a not > very likely scenario IMHO). We would have bus number rebalance (hotplug, etc.) and PCI domain support in the future, which may require hypervisor to keep consistent device list with dom0 kernel. If we don't remove the code, we still have to fix the list up. Thanks, Yu