From: Greg KH <greg@kroah.com>
To: Chris Wright <chrisw@sous-sol.org>
Cc: jbarnes@virtuousgeek.org, linux-pci@vger.kernel.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
allen.m.kay@intel.com, jun.nakajima@intel.com
Subject: Re: [PATCH 2/2] PCI: pci-stub module to reserve pci device
Date: Tue, 25 Nov 2008 20:19:46 -0800 [thread overview]
Message-ID: <20081126041946.GA18816@kroah.com> (raw)
In-Reply-To: <20081126033839.GC19881@sequoia.sous-sol.org>
On Tue, Nov 25, 2008 at 07:38:39PM -0800, Chris Wright wrote:
> When doing device assignment with KVM there's currently nothing to
> protect the device from having a driver in the host as well as the guest.
> This trivial module just binds the pci device on the host to a stub
> driver so that a real host driver can't bind to the device. It has no
> pci id table, it supports only dynamic ids.
>
> # echo "8086 10f5" > /sys/bus/pci/drivers/pci-stub/new_id
> # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/e1000e/unbind
> # echo -n 0000:00:19.0 > /sys/bus/pci/drivers/pci-stub/bind
> # ls -l /sys/bus/pci/devices/0000:00:19.0/driver
> lrwxrwxrwx 1 root root 0 2008-11-25 19:10 /sys/bus/pci/devices/0000:00:19.0/driver -> ../../../bus/pci/drivers/pci-stub
You might want to put this somewhere in the .c or documentation files
somewhere as well.
>
> Cc: "Kay, Allen M" <allen.m.kay@intel.com>
> Cc: "Nakajima, Jun" <jun.nakajima@intel.com>
> Signed-off-by: Chris Wright <chrisw@sous-sol.org>
> ---
> drivers/pci/Kconfig | 9 +++++++++
> drivers/pci/Makefile | 2 ++
> drivers/pci/pci-stub.c | 38 ++++++++++++++++++++++++++++++++++++++
> 3 files changed, 49 insertions(+), 0 deletions(-)
> create mode 100644 drivers/pci/pci-stub.c
>
> diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
> index e1ca425..f6183df 100644
> --- a/drivers/pci/Kconfig
> +++ b/drivers/pci/Kconfig
> @@ -42,6 +42,15 @@ config PCI_DEBUG
>
> When in doubt, say N.
>
> +config PCI_STUB
> + tristate "PCI Stub driver"
> + depends on PCI
> + help
> + Say Y or M here if you want be able to reserve a PCI device
> + when it is going to be assigned to a guest.
"guest operating system"? Otherwise, just "guest" doesn't mean much
here in this context.
Other than that minor thing, looks great.
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
thanks,
greg k-h
next prev parent reply other threads:[~2008-11-26 4:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-26 3:36 [PATCH 1/2] PCI: allow pci driver to support only dynids Chris Wright
2008-11-26 3:38 ` [PATCH 2/2] PCI: pci-stub module to reserve pci device Chris Wright
2008-11-26 4:19 ` Greg KH [this message]
2008-11-26 5:07 ` Chris Wright
2008-11-26 5:17 ` [PATCH 2/2 v2] " Chris Wright
2008-11-26 8:28 ` [PATCH 1/2] PCI: allow pci driver to support only dynids Jean Delvare
2008-11-26 15:19 ` Chris Wright
2008-11-26 20:34 ` Jean Delvare
2008-11-26 21:07 ` Chris Wright
2008-12-01 20:41 ` Jesse Barnes
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=20081126041946.GA18816@kroah.com \
--to=greg@kroah.com \
--cc=allen.m.kay@intel.com \
--cc=chrisw@sous-sol.org \
--cc=jbarnes@virtuousgeek.org \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox