* Gregory Haskins <[email protected]> wrote:
> This will generally be used for hypervisors to publish any host-side
> virtual devices up to a guest. The guest will have the opportunity
> to consume any devices present on the vbus-proxy as if they were
> platform devices, similar to existing buses like PCI.
>
> Signed-off-by: Gregory Haskins <[email protected]>
> ---
>
> MAINTAINERS | 6 ++
> arch/x86/Kconfig | 2 +
> drivers/Makefile | 1
> drivers/vbus/Kconfig | 14 ++++
> drivers/vbus/Makefile | 3 +
> drivers/vbus/bus-proxy.c | 152
> +++++++++++++++++++++++++++++++++++++++++++
> include/linux/vbus_driver.h | 73 +++++++++++++++++++++
> 7 files changed, 251 insertions(+), 0 deletions(-)
> create mode 100644 drivers/vbus/Kconfig
> create mode 100644 drivers/vbus/Makefile
> create mode 100644 drivers/vbus/bus-proxy.c
> create mode 100644 include/linux/vbus_driver.h
Is there a consensus on this with the KVM folks? (i've added the KVM
list to the Cc:)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html