From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Han, Weidong" <weidong.han@intel.com>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
'Keir Fraser' <Keir.Fraser@eu.citrix.com>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>
Subject: Re: [pvops-dom0] [patch] Hook Linux's PCI probe and remove callbacks
Date: Fri, 17 Jul 2009 16:14:18 -0700 [thread overview]
Message-ID: <4A6105CA.1000904@goop.org> (raw)
In-Reply-To: <715D42877B251141A38726ABF5CABF2C0545AE597D@pdsmsx503.ccr.corp.intel.com>
On 07/15/09 22:15, Han, Weidong wrote:
> Hijack the pci_bus_type probe and remove callbacks. This option only
> requires modification to the Xen specific part of Linux.
>
> This is useful to add and remove pci device to Xen hypervisor when
> load and remove its driver. For example, when VFs are created by PF,
> they will be added to Xen hypervisor, and then can be assigned to guest.
>
> This patch is based on xen-tip-master branch of jeremy's pv-ops tree.
>
Yunhong Jiang sent me a version of this patch as part of his MSI work.
This kind of interception of pci_bus_type.probe is pretty ugly, and is
unlikely to be accepted upstream in this form (the patch may only touch
a Xen file, but it is changing a variable belonging to the PCI
subsystem). We need to work with the Linux PCI maintainers to find some
other way of achieving what we need here.
Can you explain what the functional requirements are here. Could we
defer registering the device with Xen until some other convenient hook,
or must it be done at this point in the code?
Thanks,
J
next prev parent reply other threads:[~2009-07-17 23:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 5:15 [pvops-dom0] [patch] Hook Linux's PCI probe and remove callbacks Han, Weidong
2009-07-16 7:18 ` Han, Weidong
2009-07-17 6:28 ` Andy Burns
2009-07-17 23:14 ` Jeremy Fitzhardinge [this message]
2009-07-17 23:42 ` Kay, Allen M
2009-07-19 11:55 ` Jiang, Yunhong
2009-07-20 9:03 ` Han, Weidong
2009-07-20 17:01 ` Jeremy Fitzhardinge
2009-07-20 17:12 ` Jesse Barnes
2009-07-20 17:00 ` Jeremy Fitzhardinge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A6105CA.1000904@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=allen.m.kay@intel.com \
--cc=weidong.han@intel.com \
--cc=xen-devel@lists.xensource.com \
--cc=yunhong.jiang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.