search for: agraf

From: Anthony PERARD <anthony.perard@citrix.com> Remove the call to xenstore_record_dm_state from xen_main_loop_prepare that is HVM specific. Add a new vm_change_state_handler shared between xen_pv and xen_hvm machines to record the VM state to xenstore. Signed-off-by: Anthony PERARD <anthony.perard@citrix.com> Signed-off-by: Stefano Stabellini

Currenty the ext_param field only distinguishes between "config change" and "vring interrupt". We can do a lot more with it though, so let's enable a full byte of possible values and constants to #defines while at it. Signed-off-by: Alexander Graf <agraf at suse.de> --- v1 -> v2: - move defines to virtio_s390.h --- arch/s390/include/asm/kvm_virtio.h | 6 ++++++ drivers/s390/kvm/kvm_virtio.c | 19 +++++++++++++------ 2 files changed, 19 insertions(+), 6 deletions(-) diff --git a/arch/s390/include/asm/kvm_virtio.h b/arch/s390/i...

Currenty the ext_param field only distinguishes between "config change" and "vring interrupt". We can do a lot more with it though, so let's enable a full byte of possible values and constants to #defines while at it. Signed-off-by: Alexander Graf <agraf at suse.de> --- v1 -> v2: - move defines to virtio_s390.h --- arch/s390/include/asm/kvm_virtio.h | 6 ++++++ drivers/s390/kvm/kvm_virtio.c | 19 +++++++++++++------ 2 files changed, 19 insertions(+), 6 deletions(-) diff --git a/arch/s390/include/asm/kvm_virtio.h b/arch/s390/i...

When running on PowerPC, we don''t have native PIO support. There are a few hacks around to enable PIO access on PowerPC nevertheless. The most typical one is the isa-mmio device. It takes MMIO requests and converts them to PIO requests on the (QEMU internal) PIO bus. This however is not how real hardware works and it limits us in the ability to spawn eventfd''s on PIO ports

...ing with a USB device, I saw that the sd node simply doesn't get free'd when a device gets forcefully removed. Imitate the same behavior for vd devices. This way broken vd devices simply are never free'd and newly attached ones keep working just fine. Signed-off-by: Alexander Graf <agraf at suse.de> --- drivers/block/virtio_blk.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index 0bdde8f..07a18e2 100644 --- a/drivers/block/virtio_blk.c +++ b/drivers/block/virtio_blk.c @@ -889,6 +889,7 @@ static...

...ing with a USB device, I saw that the sd node simply doesn't get free'd when a device gets forcefully removed. Imitate the same behavior for vd devices. This way broken vd devices simply are never free'd and newly attached ones keep working just fine. Signed-off-by: Alexander Graf <agraf at suse.de> --- drivers/block/virtio_blk.c | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/drivers/block/virtio_blk.c b/drivers/block/virtio_blk.c index 0bdde8f..07a18e2 100644 --- a/drivers/block/virtio_blk.c +++ b/drivers/block/virtio_blk.c @@ -889,6 +889,7 @@ static...

Currenty the ext_param field only distinguishes between "config change" and "vring interrupt". We can do a lot more with it though, so let's enable a full byte of possible values and constants to #defines while at it. Signed-off-by: Alexander Graf <agraf at suse.de> --- drivers/s390/kvm/kvm_virtio.c | 22 ++++++++++++++++------ 1 files changed, 16 insertions(+), 6 deletions(-) diff --git a/drivers/s390/kvm/kvm_virtio.c b/drivers/s390/kvm/kvm_virtio.c index 4e298bc..ada7e2c 100644 --- a/drivers/s390/kvm/kvm_virtio.c +++ b/drivers/s390/kvm/kvm...

Currenty the ext_param field only distinguishes between "config change" and "vring interrupt". We can do a lot more with it though, so let's enable a full byte of possible values and constants to #defines while at it. Signed-off-by: Alexander Graf <agraf at suse.de> --- drivers/s390/kvm/kvm_virtio.c | 22 ++++++++++++++++------ 1 files changed, 16 insertions(+), 6 deletions(-) diff --git a/drivers/s390/kvm/kvm_virtio.c b/drivers/s390/kvm/kvm_virtio.c index 4e298bc..ada7e2c 100644 --- a/drivers/s390/kvm/kvm_virtio.c +++ b/drivers/s390/kvm/kvm...

...-ops for that. The io delay function already has a switch that can do nothing if you're so inclined. So here's a patch (stacked on top of the previous pv-ops series) that removes the io delay pv-ops hook and just sets the native io delay variable instead. Signed-off-by: Alexander Graf <agraf at suse.de> --- arch/x86/Kconfig | 14 -------------- arch/x86/kernel/kvm.c | 16 +++------------- 2 files changed, 3 insertions(+), 27 deletions(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 97d4f92..ebed686 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -527,20...

...-ops for that. The io delay function already has a switch that can do nothing if you're so inclined. So here's a patch (stacked on top of the previous pv-ops series) that removes the io delay pv-ops hook and just sets the native io delay variable instead. Signed-off-by: Alexander Graf <agraf at suse.de> --- arch/x86/Kconfig | 14 -------------- arch/x86/kernel/kvm.c | 16 +++------------- 2 files changed, 3 insertions(+), 27 deletions(-) diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig index 97d4f92..ebed686 100644 --- a/arch/x86/Kconfig +++ b/arch/x86/Kconfig @@ -527,20...

Paravirt ops is currently only capable of either replacing a lot of Linux internal code or none at all. The are users that don't need all of the possibilities pv-ops delivers though. On KVM for example we're perfectly fine not using the PV MMU, thus not touching any MMU code. That way we don't have to improve pv-ops to become fast, we just don't compile the MMU parts in! This

Paravirt ops is currently only capable of either replacing a lot of Linux internal code or none at all. The are users that don't need all of the possibilities pv-ops delivers though. On KVM for example we're perfectly fine not using the PV MMU, thus not touching any MMU code. That way we don't have to improve pv-ops to become fast, we just don't compile the MMU parts in! This

The 9p-virtio transport does zero copy on things larger than 1024 bytes in size. It accomplishes this by returning the physical addresses of pages to the virtio-pci device. At present, the translation is usually a bit shift. However, that approach produces an invalid page address when we read/write to vmalloc buffers, such as those used for Linux kernle modules. This causes QEMU to die printing:

The 9p-virtio transport does zero copy on things larger than 1024 bytes in size. It accomplishes this by returning the physical addresses of pages to the virtio-pci device. At present, the translation is usually a bit shift. However, that approach produces an invalid page address when we read/write to vmalloc buffers, such as those used for Linux kernle modules. This causes QEMU to die printing:

...VirtIO. Using this and my > patch to qemu, you can use paravirtualized graphics. > > This is especially important on machines that can't do MMIO, as all current > graphics implementations qemu emulates I'm aware of so far fail here. > > Signed-off-by: Alexander Graf <agraf at suse.de> Nice work. I think you want to Cc virtualization at lists.linux-foundation.org and Rusty. Cc added. Some comments below, some of them checkpatch.pl would find. I do not know much about framebuffer, so comments are from virtio usage perspective. Generally, I think locking is missi...

...VirtIO. Using this and my > patch to qemu, you can use paravirtualized graphics. > > This is especially important on machines that can't do MMIO, as all current > graphics implementations qemu emulates I'm aware of so far fail here. > > Signed-off-by: Alexander Graf <agraf at suse.de> Nice work. I think you want to Cc virtualization at lists.linux-foundation.org and Rusty. Cc added. Some comments below, some of them checkpatch.pl would find. I do not know much about framebuffer, so comments are from virtio usage perspective. Generally, I think locking is missi...

...gt; Alasdair McLeay <alasdair.mcleay@me.com> Alberto Garcia <agarcia@igalia.com> Alex Bligh <alex@alex.org.uk> Alex Horn <alex.horn@cs.ox.ac.uk> Alex Rozenman <Alex_Rozenman@mentor.com> Alex Williamson <alex.williamson@redhat.com> Alexander Graf <agraf@suse.de> Alexey Kardashevskiy <aik@ozlabs.ru> Alexey Korolev <akorolex@gmail.com> Alexey Zaytsev <alexey.zaytsev@gmail.com> Alin Tomescu <tomescu.alin@gmail.com> Alon Levy <alevy@redhat.com> Amadeusz Sławiński <amade@asmblr.net> Amit Shah <ami...

...gt; Alasdair McLeay <alasdair.mcleay@me.com> Alberto Garcia <agarcia@igalia.com> Alex Bligh <alex@alex.org.uk> Alex Horn <alex.horn@cs.ox.ac.uk> Alex Rozenman <Alex_Rozenman@mentor.com> Alex Williamson <alex.williamson@redhat.com> Alexander Graf <agraf@suse.de> Alexey Kardashevskiy <aik@ozlabs.ru> Alexey Korolev <akorolex@gmail.com> Alexey Zaytsev <alexey.zaytsev@gmail.com> Alin Tomescu <tomescu.alin@gmail.com> Alon Levy <alevy@redhat.com> Amadeusz Sławiński <amade@asmblr.net> Amit Shah <ami...

...gt; Alasdair McLeay <alasdair.mcleay@me.com> Alberto Garcia <agarcia@igalia.com> Alex Bligh <alex@alex.org.uk> Alex Horn <alex.horn@cs.ox.ac.uk> Alex Rozenman <Alex_Rozenman@mentor.com> Alex Williamson <alex.williamson@redhat.com> Alexander Graf <agraf@suse.de> Alexey Kardashevskiy <aik@ozlabs.ru> Alexey Korolev <akorolex@gmail.com> Alexey Zaytsev <alexey.zaytsev@gmail.com> Alin Tomescu <tomescu.alin@gmail.com> Alon Levy <alevy@redhat.com> Amadeusz Sławiński <amade@asmblr.net> Amit Shah <ami...

...84@googlemail.com> Alexander Bondar <alexander.bondar@intel.com> Alexander Boyko <alexander_boyko@xyratex.com> Alexander Clouter <alex@digriz.org.uk> Alexander Duyck <alexander.h.duyck@intel.com> Alexander Gordeev <agordeev@redhat.com> Alexander Graf <agraf@suse.de> Alexander Guy <alexander.guy@guy-engineering.com> Alexander Holler <holler@ahsoftware.de> Alexander Inyukhin <shurick@sectorb.msk.ru> Alexander Kartashov <alekskartashov@parallels.com> Alexander Lyakas <alex.bolshoy@gmail.com> Alexander Schremme...