Displaying 14 results from an estimated 14 matches for "virtio_bus_get_vdev_features_rev".
2014 Dec 11
0
[PATCH RFC v6 18/20] virtio: support revision-specific features
...rtio-ccw.c
+++ b/hw/s390x/virtio-ccw.c
@@ -699,6 +699,10 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
}
ret = 0;
dev->revision = revinfo.revision;
+ /* Re-evaluate which features the device wants to offer. */
+ dev->host_features =
+ virtio_bus_get_vdev_features_rev(&dev->bus, dev->host_features,
+ dev->revision >= 1 ? 1 : 0);
break;
default:
ret = -ENOSYS;
@@ -712,6 +716,9 @@ static void virtio_sch_disable_cb(SubchDev *sch)
VirtioCcwDevice *dev = sch->driver_data;...
2014 Dec 11
0
[PATCH RFC v6 18/20] virtio: support revision-specific features
...rtio-ccw.c
+++ b/hw/s390x/virtio-ccw.c
@@ -699,6 +699,10 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
}
ret = 0;
dev->revision = revinfo.revision;
+ /* Re-evaluate which features the device wants to offer. */
+ dev->host_features =
+ virtio_bus_get_vdev_features_rev(&dev->bus, dev->host_features,
+ dev->revision >= 1 ? 1 : 0);
break;
default:
ret = -ENOSYS;
@@ -712,6 +716,9 @@ static void virtio_sch_disable_cb(SubchDev *sch)
VirtioCcwDevice *dev = sch->driver_data;...
2014 Dec 02
0
[PATCH RFC v5 18/19] virtio: support revision-specific features
...rtio-ccw.c
+++ b/hw/s390x/virtio-ccw.c
@@ -699,6 +699,10 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
}
ret = 0;
dev->revision = revinfo.revision;
+ /* Re-evaluate which features the device wants to offer. */
+ dev->host_features =
+ virtio_bus_get_vdev_features_rev(&dev->bus, dev->host_features,
+ dev->revision >= 1 ? 1 : 0);
break;
default:
ret = -ENOSYS;
@@ -712,6 +716,9 @@ static void virtio_sch_disable_cb(SubchDev *sch)
VirtioCcwDevice *dev = sch->driver_data;...
2014 Dec 02
0
[PATCH RFC v5 18/19] virtio: support revision-specific features
...rtio-ccw.c
+++ b/hw/s390x/virtio-ccw.c
@@ -699,6 +699,10 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
}
ret = 0;
dev->revision = revinfo.revision;
+ /* Re-evaluate which features the device wants to offer. */
+ dev->host_features =
+ virtio_bus_get_vdev_features_rev(&dev->bus, dev->host_features,
+ dev->revision >= 1 ? 1 : 0);
break;
default:
ret = -ENOSYS;
@@ -712,6 +716,9 @@ static void virtio_sch_disable_cb(SubchDev *sch)
VirtioCcwDevice *dev = sch->driver_data;...
2014 Dec 28
2
[PATCH RFC v6 18/20] virtio: support revision-specific features
...w.c
> @@ -699,6 +699,10 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
> }
> ret = 0;
> dev->revision = revinfo.revision;
> + /* Re-evaluate which features the device wants to offer. */
> + dev->host_features =
> + virtio_bus_get_vdev_features_rev(&dev->bus, dev->host_features,
> + dev->revision >= 1 ? 1 : 0);
> break;
> default:
> ret = -ENOSYS;
> @@ -712,6 +716,9 @@ static void virtio_sch_disable_cb(SubchDev *sch)
> VirtioCcwDevice *de...
2014 Dec 28
2
[PATCH RFC v6 18/20] virtio: support revision-specific features
...w.c
> @@ -699,6 +699,10 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
> }
> ret = 0;
> dev->revision = revinfo.revision;
> + /* Re-evaluate which features the device wants to offer. */
> + dev->host_features =
> + virtio_bus_get_vdev_features_rev(&dev->bus, dev->host_features,
> + dev->revision >= 1 ? 1 : 0);
> break;
> default:
> ret = -ENOSYS;
> @@ -712,6 +716,9 @@ static void virtio_sch_disable_cb(SubchDev *sch)
> VirtioCcwDevice *de...
2014 Nov 27
4
[PATCH RFC v4 00/16] qemu: towards virtio-1 host support
On Thu, 27 Nov 2014 18:18:25 +0200
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> On Thu, Nov 27, 2014 at 05:06:51PM +0100, Cornelia Huck wrote:
> > So we should have a per-device callback into the transport layer, say
> > check_legacy()?
>
> I would just have 2 masks: legacy_features and features.
But these belong to the device type and the transport
2014 Nov 27
4
[PATCH RFC v4 00/16] qemu: towards virtio-1 host support
On Thu, 27 Nov 2014 18:18:25 +0200
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> On Thu, Nov 27, 2014 at 05:06:51PM +0100, Cornelia Huck wrote:
> > So we should have a per-device callback into the transport layer, say
> > check_legacy()?
>
> I would just have 2 masks: legacy_features and features.
But these belong to the device type and the transport
2015 Apr 13
2
[PATCH 2/2] virtio-balloon: virtio 1 support
On Mon, 13 Apr 2015 13:26:31 +0200
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> On Mon, Apr 13, 2015 at 10:02:58AM +0200, Cornelia Huck wrote:
> > Also, doesn't get_features need to be modified as well so that
> > VERSION_1 is advertised?
>
> virtio_pci_device_plugged seems to set it ATM. I'll re-test to confirm.
Indeed, pci sets it, but ccw
2015 Apr 13
2
[PATCH 2/2] virtio-balloon: virtio 1 support
On Mon, 13 Apr 2015 13:26:31 +0200
"Michael S. Tsirkin" <mst at redhat.com> wrote:
> On Mon, Apr 13, 2015 at 10:02:58AM +0200, Cornelia Huck wrote:
> > Also, doesn't get_features need to be modified as well so that
> > VERSION_1 is advertised?
>
> virtio_pci_device_plugged seems to set it ATM. I'll re-test to confirm.
Indeed, pci sets it, but ccw
2014 Dec 11
45
[PATCH RFC v6 00/20] qemu: towards virtio-1 host support
And yet another iteration of virtio-1 support in qemu, tested with the
latest virtio kernel patches. Find it at
git://github.com/cohuck/qemu virtio-1
Changes from v5:
- fixed stupid bug in "virtio: support more feature bits": we need to
define a proper prop backend for 64 bit wide handling...
- don't negotiate revision 1 unless VERSION_1 is offered
- use 64 bit wide features
2014 Dec 11
45
[PATCH RFC v6 00/20] qemu: towards virtio-1 host support
And yet another iteration of virtio-1 support in qemu, tested with the
latest virtio kernel patches. Find it at
git://github.com/cohuck/qemu virtio-1
Changes from v5:
- fixed stupid bug in "virtio: support more feature bits": we need to
define a proper prop backend for 64 bit wide handling...
- don't negotiate revision 1 unless VERSION_1 is offered
- use 64 bit wide features
2014 Dec 02
24
[PATCH RFC v5 00/19] qemu: towards virtio-1 host support
Another iteration of virtio-1 patches for qemu, as always available on
git://github.com/cohuck/qemu virtio-1
This one seems to work together with the current vhost-next patches
(well, I can ping :)
Changes from v4:
- add helpers for feature bit manipulation and checking
- use 64 bit feature bits instead of 32 bit arrays
- infrastructure to allow devices to offer different sets of feature
bits
2014 Dec 02
24
[PATCH RFC v5 00/19] qemu: towards virtio-1 host support
Another iteration of virtio-1 patches for qemu, as always available on
git://github.com/cohuck/qemu virtio-1
This one seems to work together with the current vhost-next patches
(well, I can ping :)
Changes from v4:
- add helpers for feature bit manipulation and checking
- use 64 bit feature bits instead of 32 bit arrays
- infrastructure to allow devices to offer different sets of feature
bits