From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jesse Barnes <jbarnes@virtuousgeek.org>
Cc: xen-devel@lists.xensource.com, linux-pci@vger.kernel.org,
yunhong.jiang@intel.com, allen.m.kay@intel.com,
Keir.Fraser@eu.citrix.com, Weidong Han <weidong.han@intel.com>
Subject: Re: [PATCH] pv-ops: register xen pci notifier
Date: Tue, 28 Jul 2009 10:57:39 -0700 [thread overview]
Message-ID: <4A6F3C13.9000906@goop.org> (raw)
In-Reply-To: <20090728092715.64059b28@jbarnes-g45>
On 07/28/09 09:27, Jesse Barnes wrote:
> On Mon, 27 Jul 2009 09:56:48 +0800
> Weidong Han <weidong.han@intel.com> wrote:
>
>
>> Register the notifier to handle hot-plug devices and SR-IOV devices
>> for Xen hypervisor. When a device is hot added or removed, it adds
>> or removes it to Xen via hypercalls.
>>
>> Signed-off-by: Weidong Han <weidong.han@intel.com>
>> ---
>> drivers/xen/Makefile | 5 +-
>> drivers/xen/pci.c | 105
>> +++++++++++++++++++++++++++++++++++++++
>> include/xen/interface/physdev.h | 21 ++++++++ 3 files changed, 129
>> insertions(+), 2 deletions(-) create mode 100644 drivers/xen/pci.c
>>
>
> Did you want this to come through the PCI tree? Or do you just want
> some extra review on it before pushing it through the Xen tree?
>
I'll put it through the Xen tree, since I don't think it makes much
sense standalone. Are you happy to Ack/Reviewed-by it?
J
next prev parent reply other threads:[~2009-07-28 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-27 1:56 [PATCH] pv-ops: register xen pci notifier Weidong Han
2009-07-28 16:27 ` Jesse Barnes
2009-07-28 17:57 ` Jeremy Fitzhardinge [this message]
2009-07-28 18:11 ` Jeremy Fitzhardinge
2009-07-29 1:33 ` Han, Weidong
2009-07-29 17:27 ` Jeremy Fitzhardinge
2009-07-30 5:48 ` Jiang, Yunhong
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=4A6F3C13.9000906@goop.org \
--to=jeremy@goop.org \
--cc=Keir.Fraser@eu.citrix.com \
--cc=allen.m.kay@intel.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-pci@vger.kernel.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.