Displaying 20 results from an estimated 4000 matches similar to: "[RFC PATCH] virt_mmio: fix signature checking for BE guests"
2015 Jan 20
4
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
This patch add a support for second version of the virtio-mmio device,
which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
specification.
Main changes:
1. The control register symbolic names use the new device/driver
nomenclature rather than the old guest/host one.
2. The driver detect the device version (version 1 is the pre-OASIS
spec, version 2 is compatible with
2015 Jan 20
4
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
This patch add a support for second version of the virtio-mmio device,
which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
specification.
Main changes:
1. The control register symbolic names use the new device/driver
nomenclature rather than the old guest/host one.
2. The driver detect the device version (version 1 is the pre-OASIS
spec, version 2 is compatible with
2014 Dec 19
5
[RFC] virtio-mmio: Update the device to OASIS spec version
This patch add a support for second version of the virtio-mmio device,
which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
specification.
Main changes:
1. The control register symbolic names use the new device/driver
nomenclature rather than the old guest/host one.
2. The driver detect the device version (version 1 is the pre-OASIS
spec, version 2 is compatible with
2014 Dec 19
5
[RFC] virtio-mmio: Update the device to OASIS spec version
This patch add a support for second version of the virtio-mmio device,
which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
specification.
Main changes:
1. The control register symbolic names use the new device/driver
nomenclature rather than the old guest/host one.
2. The driver detect the device version (version 1 is the pre-OASIS
spec, version 2 is compatible with
2014 Oct 25
0
[RFC PATCH 1/2] Add a new register offset let interrupt reason available
From: Li Liu <john.liuli at huawei.com>
Add a new register offset VIRTIO_MMIO_ISRMEM which help to
estblish a shared memory region between virtio-mmio driver
and qemu with two purposes:
1.Guest virtio-mmio driver can get the interrupt reason.
2.Check irqfd enabled or not to register different irq handler.
Signed-off-by: Li Liu <john.liuli at huawei.com>
---
2017 Dec 12
2
[PATCH] virtio_mmio: fix devm cleanup
Recent rework of the virtio_mmio probe path balanced a devm_ioremap()
with an iounmap() rather than its devm variant. This ends up corrupting
the devm datastructures, and results in the following boot failure on
arm64 under QEMU 2.9.0:
[ 3.450397] ------------[ cut here ]------------
[ 3.453822] Trying to vfree() nonexistent vm area (00000000c05b4844)
[ 3.460534] WARNING: CPU: 1 PID: 1
2017 Dec 12
2
[PATCH] virtio_mmio: fix devm cleanup
Recent rework of the virtio_mmio probe path balanced a devm_ioremap()
with an iounmap() rather than its devm variant. This ends up corrupting
the devm datastructures, and results in the following boot failure on
arm64 under QEMU 2.9.0:
[ 3.450397] ------------[ cut here ]------------
[ 3.453822] Trying to vfree() nonexistent vm area (00000000c05b4844)
[ 3.460534] WARNING: CPU: 1 PID: 1
2015 Mar 05
3
[PATCH] virtio_mmio: fix endian-ness for mmio
Going over the virtio mmio code, I noticed that it doesn't correctly
return device config values in LE format when using virtio 1.0.
Borrow code from virtio_pci_modern to do this correctly.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
Note: untested: QEMU doesn't support virtio 1.0 for virtio-mmio.
Pawel, could you please confirm this patch makes sense?
2015 Mar 05
3
[PATCH] virtio_mmio: fix endian-ness for mmio
Going over the virtio mmio code, I noticed that it doesn't correctly
return device config values in LE format when using virtio 1.0.
Borrow code from virtio_pci_modern to do this correctly.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
Note: untested: QEMU doesn't support virtio 1.0 for virtio-mmio.
Pawel, could you please confirm this patch makes sense?
2015 Mar 12
2
[PATCH] virtio_mmio: fix endian-ness for mmio
On Thu, Mar 12, 2015 at 12:33:36PM +1030, Rusty Russell wrote:
> "Michael S. Tsirkin" <mst at redhat.com> writes:
> > Going over the virtio mmio code, I noticed that it doesn't correctly
> > return device config values in LE format when using virtio 1.0.
> > Borrow code from virtio_pci_modern to do this correctly.
>
> AFAICT, it doesn't need to.
2015 Mar 12
2
[PATCH] virtio_mmio: fix endian-ness for mmio
On Thu, Mar 12, 2015 at 12:33:36PM +1030, Rusty Russell wrote:
> "Michael S. Tsirkin" <mst at redhat.com> writes:
> > Going over the virtio mmio code, I noticed that it doesn't correctly
> > return device config values in LE format when using virtio 1.0.
> > Borrow code from virtio_pci_modern to do this correctly.
>
> AFAICT, it doesn't need to.
2015 Jan 20
0
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
On Tue, Jan 20, 2015 at 06:12:11PM +0000, Pawel Moll wrote:
> This patch add a support for second version of the virtio-mmio device,
> which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
> specification.
>
> Main changes:
>
> 1. The control register symbolic names use the new device/driver
> nomenclature rather than the old guest/host one.
>
2015 Jan 20
0
[PATCH v2] virtio-mmio: Update the device to OASIS spec version
On Tue, Jan 20, 2015 at 06:12:11PM +0000, Pawel Moll wrote:
> This patch add a support for second version of the virtio-mmio device,
> which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
> specification.
>
> Main changes:
>
> 1. The control register symbolic names use the new device/driver
> nomenclature rather than the old guest/host one.
>
2015 Jan 15
0
[RFC] virtio-mmio: Update the device to OASIS spec version
On Fri, Dec 19, 2014 at 06:38:04PM +0000, Pawel Moll wrote:
> This patch add a support for second version of the virtio-mmio device,
> which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
> specification.
>
> Main changes:
>
> 1. The control register symbolic names use the new device/driver
> nomenclature rather than the old guest/host one.
>
2015 Jan 15
0
[RFC] virtio-mmio: Update the device to OASIS spec version
On Fri, Dec 19, 2014 at 06:38:04PM +0000, Pawel Moll wrote:
> This patch add a support for second version of the virtio-mmio device,
> which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
> specification.
>
> Main changes:
>
> 1. The control register symbolic names use the new device/driver
> nomenclature rather than the old guest/host one.
>
2015 Jan 20
1
[PATCH] virtio-mmio: Update the device to OASIS spec version
This patch add a support for second version of the virtio-mmio device,
which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
specification.
Main changes:
1. The control register symbolic names use the new device/driver
nomenclature rather than the old guest/host one.
2. The driver detect the device version (version 1 is the pre-OASIS
spec, version 2 is compatible with
2015 Jan 20
1
[PATCH] virtio-mmio: Update the device to OASIS spec version
This patch add a support for second version of the virtio-mmio device,
which follows OASIS "Virtual I/O Device (VIRTIO) Version 1.0"
specification.
Main changes:
1. The control register symbolic names use the new device/driver
nomenclature rather than the old guest/host one.
2. The driver detect the device version (version 1 is the pre-OASIS
spec, version 2 is compatible with
2015 Mar 12
1
[PATCH v2 log fixed] virtio_mmio: fix endian-ness for mmio
Subject: [PATCH] virtio_mmio: fix access width for mmio
Going over the virtio mmio code, I noticed that it doesn't correctly
access modern device config values using "natural" accessors: it uses
readb to get/set them byte by byte, while the virtio 1.0 spec explicitly states:
4.2.2.2 Driver Requirements: MMIO Device Register Layout
...
The driver MUST only
2015 Mar 12
1
[PATCH v2 log fixed] virtio_mmio: fix endian-ness for mmio
Subject: [PATCH] virtio_mmio: fix access width for mmio
Going over the virtio mmio code, I noticed that it doesn't correctly
access modern device config values using "natural" accessors: it uses
readb to get/set them byte by byte, while the virtio 1.0 spec explicitly states:
4.2.2.2 Driver Requirements: MMIO Device Register Layout
...
The driver MUST only
2015 Mar 05
3
[PATCH] virtio_mmio: generation support
virtio_mmio currently lacks generation support which
makes multi-byte field access racy.
Fix by getting the value at offset 0xfc for version 2
devices. Nothing we can do for version 1, so return
generation id 0.
Signed-off-by: Michael S. Tsirkin <mst at redhat.com>
---
Pawel, you mentioned you have a working virtio 1.0
hypervisor, can you pls confirm this works correctly?