This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


Re: [Xen-devel] [pvops-dom0] [patch] Hook Linux's PCI probe and remove c

To: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Subject: Re: [Xen-devel] [pvops-dom0] [patch] Hook Linux's PCI probe and remove callbacks
From: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
Date: Mon, 20 Jul 2009 10:12:53 -0700
Cc: "'xen-devel@xxxxxxxxxxxxxxxxxxx'" <xen-devel@xxxxxxxxxxxxxxxxxxx>, "Kay, Allen M" <allen.m.kay@xxxxxxxxx>, "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>, "Han, Weidong" <weidong.han@xxxxxxxxx>, Fraser' <Keir.Fraser@xxxxxxxxxxxxx>, 'Keir
Delivery-date: Mon, 20 Jul 2009 10:13:26 -0700
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=virtuousgeek.org; h=Received:Date:From:To:Cc:Subject:Message-ID:In-Reply-To:References:X-Mailer:Mime-Version:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=irHXOsRAQZGH/SUtRc2IaJREiEWLErU7CxLfJM3/nMLNrEjK9VAJ6kYpD1RDfQEKR73Nr6vvuLhZnRGFqSox/ivzCT19UIVA31l67AocPrB4EK++5jNTz33McH8yAnTx;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A64A2F1.2090303@xxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <715D42877B251141A38726ABF5CABF2C0545AE597D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A6105CA.1000904@xxxxxxxx> <57C9024A16AD2D4C97DC78E552063EA3A90A8D30@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <E2263E4A5B2284449EEBD0AAB751098402CD23912D@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> <4A64A2F1.2090303@xxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 20 Jul 2009 10:01:37 -0700
Jeremy Fitzhardinge <jeremy@xxxxxxxx> wrote:

> On 07/19/09 04:55, Jiang, Yunhong wrote:
> >  One consideration to is to split them into two item:
> > a) For all device that is not hot-pluged, we don't need this
> > hypercall, instead, Xen will do the scan and setup the mapping. b)
> > For those hot-plug device and SR-IOV devices, maybe we can use the
> > BUS_NOTIFY_ADD_DEVICE notifier to achieve ths purpose. We can just
> > add a notifier to it. I assume this is simlar to IOMMU in kernel,
> > which should requires this notify also. So a Xen specific notifier
> > should achieve our purpose without change to the PCI bus layer. 
> >
> > I checked the kernel code, and noticed that
> > arch/x86/kernel/amd_iommu.c register the notifier for
> > BUS_NOTIFY_ADD_DEVICE, but a bit strange why Intel IOMMU has no
> > such support, do you know if VT-d in kernel support device hotplug
> > already?
> >
> > Allen/Jeremy, any suggestion?
> >   
> Yes, this is exactly the kind of answer I was looking for.

Yeah if you can make that work for you it sounds like the best
approach.  If you have further questions or want some review on it,
please cc linux-pci@xxxxxxxxxxxxxxxx  There's an active hotplug
development community who may be willing to help.

Jesse Barnes, Intel Open Source Technology Center

Xen-devel mailing list