Displaying 11 results from an estimated 11 matches for "422,13".
Did you mean:
412,13
2014 Dec 11
0
[PATCH RFC v6 10/20] s390x/virtio-ccw: add virtio set-revision call
...if (dev->revision <= 0) {
+ features.features &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
+ }
} else {
/* Return zeroes if the guest supports more feature bits. */
features.features = 0;
@@ -406,6 +422,13 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
(vdev->guest_features & 0xffffffff00000000) |
features.features);
} else if (features.index == 1) {
+ /*
+ * The guest...
2014 Dec 11
0
[PATCH RFC v6 10/20] s390x/virtio-ccw: add virtio set-revision call
...if (dev->revision <= 0) {
+ features.features &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
+ }
} else {
/* Return zeroes if the guest supports more feature bits. */
features.features = 0;
@@ -406,6 +422,13 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
(vdev->guest_features & 0xffffffff00000000) |
features.features);
} else if (features.index == 1) {
+ /*
+ * The guest...
2014 Dec 02
0
[PATCH RFC v5 10/19] s390x/virtio-ccw: add virtio set-revision call
...if (dev->revision <= 0) {
+ features.features &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
+ }
} else {
/* Return zeroes if the guest supports more feature bits. */
features.features = 0;
@@ -406,6 +422,13 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
(vdev->guest_features & 0xffffffff00000000) |
features.features);
} else if (features.index == 1) {
+ /*
+ * The guest...
2014 Dec 02
0
[PATCH RFC v5 10/19] s390x/virtio-ccw: add virtio set-revision call
...if (dev->revision <= 0) {
+ features.features &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
+ }
} else {
/* Return zeroes if the guest supports more feature bits. */
features.features = 0;
@@ -406,6 +422,13 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
(vdev->guest_features & 0xffffffff00000000) |
features.features);
} else if (features.index == 1) {
+ /*
+ * The guest...
2014 Dec 04
1
[PATCH RFC v5 10/19] s390x/virtio-ccw: add virtio set-revision call
...n <= 0) {
> + features.features &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
> + }
> } else {
> /* Return zeroes if the guest supports more feature bits. */
> features.features = 0;
> @@ -406,6 +422,13 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
> (vdev->guest_features & 0xffffffff00000000) |
> features.features);
> } else if (features.index == 1) {
> + /*
> +...
2014 Dec 04
1
[PATCH RFC v5 10/19] s390x/virtio-ccw: add virtio set-revision call
...n <= 0) {
> + features.features &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
> + }
> } else {
> /* Return zeroes if the guest supports more feature bits. */
> features.features = 0;
> @@ -406,6 +422,13 @@ static int virtio_ccw_cb(SubchDev *sch, CCW1 ccw)
> (vdev->guest_features & 0xffffffff00000000) |
> features.features);
> } else if (features.index == 1) {
> + /*
> +...
2017 Jan 16
4
[RFC 0/2] Propose a new pointer trait.
Hi,
I'm part of an engineering team doing research on persistent memory support and
we have stumbled upon an interesting problem. The issue is, we would like to be
able to use the standard library containers in a persistent memory context
(think NVDIMM-N). What I mean is that you allocate a container from said
memory, use it like you normally would. After the application terminates,
expectedly
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
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