diff options
| author | Chris Wright <chrisw@sous-sol.org> | 2008-11-25 21:17:13 -0800 |
|---|---|---|
| committer | Jesse Barnes <jbarnes@virtuousgeek.org> | 2009-01-07 11:12:38 -0800 |
| commit | c70e0d9dfef3d826c8ae4f7544acc53887cb161d (patch) | |
| tree | e870ac2759edc8dbb2dc67b18c0c42e827283fc7 /drivers/pci/Makefile | |
| parent | 2debb4d2019fa05a0896f1591dea0e0dc21bc046 (diff) | |
| download | kernel_samsung_smdk4412-c70e0d9dfef3d826c8ae4f7544acc53887cb161d.zip kernel_samsung_smdk4412-c70e0d9dfef3d826c8ae4f7544acc53887cb161d.tar.gz kernel_samsung_smdk4412-c70e0d9dfef3d826c8ae4f7544acc53887cb161d.tar.bz2 | |
PCI: pci-stub module to reserve pci device
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
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>
Acked-by: Greg Kroah-Hartman <gregkh@suse.de>
Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>
Diffstat (limited to 'drivers/pci/Makefile')
| -rw-r--r-- | drivers/pci/Makefile | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/drivers/pci/Makefile b/drivers/pci/Makefile index af3bfe2..3d07ce2 100644 --- a/drivers/pci/Makefile +++ b/drivers/pci/Makefile @@ -53,6 +53,8 @@ obj-$(CONFIG_HOTPLUG) += setup-bus.o obj-$(CONFIG_PCI_SYSCALL) += syscall.o +obj-$(CONFIG_PCI_STUB) += pci-stub.o + ifeq ($(CONFIG_PCI_DEBUG),y) EXTRA_CFLAGS += -DDEBUG endif |