From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Kay, Allen M" <allen.m.kay@intel.com>
Cc: "'xen-devel@lists.xensource.com'" <xen-devel@lists.xensource.com>,
"Han, Weidong" <weidong.han@intel.com>,
'Keir Fraser' <Keir.Fraser@eu.citrix.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>,
"Jiang, Yunhong" <yunhong.jiang@intel.com>
Subject: Re: [pvops-dom0] [patch] Hook Linux's PCI probe and remove callbacks
Date: Mon, 20 Jul 2009 10:00:57 -0700 [thread overview]
Message-ID: <4A64A2C9.3060103@goop.org> (raw)
In-Reply-To: <57C9024A16AD2D4C97DC78E552063EA3A90A8D30@orsmsx505.amr.corp.intel.com>
On 07/17/09 16:42, Kay, Allen M wrote:
> These hooks for two purposes:
>
> 1) Enabling of a SR-IOV virtual function. The hypercall will tell xen to setup VT-d context entries for the BDF corresponding to the new virtual function. This is required for SR-IOV to work.
>
> 2) PCI hot-plug support when devices are hot added/removed. Vt-d context entries and data structures in Xen needs to be modified accordingly.
>
> These hooks needs to be enabled before either of these functions are performed - I assume after dom0 boots.
>
> Can you suggest a better way to do this?
>
The best person to ask is probably Jesse Barnes (cc:d).
In general the way to approach these things is to either find something
in the kernel which does something analogous and use the same
interfaces, possibly extending them a bit if necessary.
J
prev parent reply other threads:[~2009-07-20 17:00 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
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 [this message]
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=4A64A2C9.3060103@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=allen.m.kay@intel.com \
--cc=jbarnes@virtuousgeek.org \
--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.