search for: 5a4c63c

Displaying 8 results from an estimated 8 matches for "5a4c63c".

2012 Jun 26
6
[PATCH] Add a page cache-backed balloon device driver.
...pages from the cache and touching the page. + + If unsure, say N. + config VIRTIO_MMIO tristate "Platform bus driver for memory mapped virtio devices (EXPERIMENTAL)" depends on HAS_IOMEM && EXPERIMENTAL diff --git a/drivers/virtio/Makefile b/drivers/virtio/Makefile index 5a4c63c..7ca0a3f 100644 --- a/drivers/virtio/Makefile +++ b/drivers/virtio/Makefile @@ -3,3 +3,4 @@ obj-$(CONFIG_VIRTIO_RING) += virtio_ring.o obj-$(CONFIG_VIRTIO_MMIO) += virtio_mmio.o obj-$(CONFIG_VIRTIO_PCI) += virtio_pci.o obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o +obj-$(CONFIG_VIRTIO_FILEBAL...
2012 Jun 26
6
[PATCH] Add a page cache-backed balloon device driver.
...pages from the cache and touching the page. + + If unsure, say N. + config VIRTIO_MMIO tristate "Platform bus driver for memory mapped virtio devices (EXPERIMENTAL)" depends on HAS_IOMEM && EXPERIMENTAL diff --git a/drivers/virtio/Makefile b/drivers/virtio/Makefile index 5a4c63c..7ca0a3f 100644 --- a/drivers/virtio/Makefile +++ b/drivers/virtio/Makefile @@ -3,3 +3,4 @@ obj-$(CONFIG_VIRTIO_RING) += virtio_ring.o obj-$(CONFIG_VIRTIO_MMIO) += virtio_mmio.o obj-$(CONFIG_VIRTIO_PCI) += virtio_pci.o obj-$(CONFIG_VIRTIO_BALLOON) += virtio_balloon.o +obj-$(CONFIG_VIRTIO_FILEBAL...
2012 Jul 23
4
[RFC 0/2] virtio: provide a way for host to monitor critical events in the device
As it was discussed recently, there's currently no way for the guest to notify the host about panics. Further more, there's no reasonable way to notify the host of other critical events such as an OOM kill. This short patch series introduces a new device named virtio-notifier which does two simple things: 1. Provide a simple interface for the guest to notify the host of critical
2012 Jul 23
4
[RFC 0/2] virtio: provide a way for host to monitor critical events in the device
As it was discussed recently, there's currently no way for the guest to notify the host about panics. Further more, there's no reasonable way to notify the host of other critical events such as an OOM kill. This short patch series introduces a new device named virtio-notifier which does two simple things: 1. Provide a simple interface for the guest to notify the host of critical
2012 Jul 25
0
No subject
...gt;> config VIRTIO_MMIO > >> tristate "Platform bus driver for memory mapped virtio devices (EXPERIMENTAL)" > >> depends on HAS_IOMEM && EXPERIMENTAL > >> diff --git a/drivers/virtio/Makefile b/drivers/virtio/Makefile > >> index 5a4c63c..7ca0a3f 100644 > >> --- a/drivers/virtio/Makefile > >> +++ b/drivers/virtio/Makefile > >> @@ -3,3 +3,4 @@ obj-$(CONFIG_VIRTIO_RING) += virtio_ring.o > >> obj-$(CONFIG_VIRTIO_MMIO) += virtio_mmio.o > >> obj-$(CONFIG_VIRTIO_PCI) += virtio_pci.o > &gt...
2012 Jul 25
0
No subject
...gt;> config VIRTIO_MMIO > >> tristate "Platform bus driver for memory mapped virtio devices (EXPERIMENTAL)" > >> depends on HAS_IOMEM && EXPERIMENTAL > >> diff --git a/drivers/virtio/Makefile b/drivers/virtio/Makefile > >> index 5a4c63c..7ca0a3f 100644 > >> --- a/drivers/virtio/Makefile > >> +++ b/drivers/virtio/Makefile > >> @@ -3,3 +3,4 @@ obj-$(CONFIG_VIRTIO_RING) += virtio_ring.o > >> obj-$(CONFIG_VIRTIO_MMIO) += virtio_mmio.o > >> obj-$(CONFIG_VIRTIO_PCI) += virtio_pci.o > &gt...
2011 Oct 27
1
[PATCH v3] virtio: Add platform bus driver for memory mapped virtio device
On Mon, 2011-10-24 at 03:33 +0100, Rusty Russell wrote: > No, that's it I think. Please send a diff for the documentation, since > I'm updating the LyX master and I've already applied your previous > version. Here it goes (below). Also do you think you would be able to merge the driver (corresponding v4 patch follows) in the 3.2 merge window that seems to have just opened?
2011 Oct 27
1
[PATCH v3] virtio: Add platform bus driver for memory mapped virtio device
On Mon, 2011-10-24 at 03:33 +0100, Rusty Russell wrote: > No, that's it I think. Please send a diff for the documentation, since > I'm updating the LyX master and I've already applied your previous > version. Here it goes (below). Also do you think you would be able to merge the driver (corresponding v4 patch follows) in the 3.2 merge window that seems to have just opened?