Displaying 12 results from an estimated 12 matches for "config_wce".
2014 Oct 24
5
[PATCH RFC 00/11] qemu: towards virtio-1 host support
...irtIODevice *vdev, VirtQueue *vq)
static uint32_t get_features(VirtIODevice *vdev, unsigned int index, uint32_t f)
{
+ if (index == 1) {
+ f &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
+ }
return f;
}
> - blk has some features removed under 1.0,
> specifically CONFIG_WCE.
> - net header is different for 1.0
2014 Oct 24
5
[PATCH RFC 00/11] qemu: towards virtio-1 host support
...irtIODevice *vdev, VirtQueue *vq)
static uint32_t get_features(VirtIODevice *vdev, unsigned int index, uint32_t f)
{
+ if (index == 1) {
+ f &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
+ }
return f;
}
> - blk has some features removed under 1.0,
> specifically CONFIG_WCE.
> - net header is different for 1.0
2014 Oct 23
0
[PATCH RFC 00/11] qemu: towards virtio-1 host support
...com/cohuck/qemu virtio-1
>
> I've mainly focused on:
> - endianness handling
> - extended feature bits
> - virtio-ccw new/changed commands
So issues identified so far:
- devices not converted yet should not advertize 1.0
- blk has some features removed under 1.0,
specifically CONFIG_WCE.
- net header is different for 1.0
> Thanks go to Thomas for some preliminary work in this area.
>
> I've been able to start guests both with and without the virtio-1 patches
> in the linux guest patchset, with virtio-net and virtio-blk devices (with
> and without dataplane)....
2014 Oct 28
0
[PATCH RFC 00/11] qemu: towards virtio-1 host support
...t_features(VirtIODevice *vdev, unsigned int index, uint32_t f)
> {
> + if (index == 1) {
> + f &= ~(1 << (VIRTIO_F_VERSION_1 - 32));
> + }
> return f;
> }
>
>
>
> > - blk has some features removed under 1.0,
> > specifically CONFIG_WCE.
> > - net header is different for 1.0
2014 Dec 11
0
[PATCH RFC v6 03/20] virtio: feature bit manipulation helpers
...tures, VIRTIO_BLK_F_SEG_MAX);
+ virtio_add_feature(&features, VIRTIO_BLK_F_GEOMETRY);
+ virtio_add_feature(&features, VIRTIO_BLK_F_TOPOLOGY);
+ virtio_add_feature(&features, VIRTIO_BLK_F_BLK_SIZE);
+ virtio_add_feature(&features, VIRTIO_BLK_F_SCSI);
if (s->conf.config_wce) {
- features |= (1 << VIRTIO_BLK_F_CONFIG_WCE);
+ virtio_add_feature(&features, VIRTIO_BLK_F_CONFIG_WCE);
}
if (blk_enable_write_cache(s->blk)) {
- features |= (1 << VIRTIO_BLK_F_WCE);
+ virtio_add_feature(&features, VIRTIO_BLK_F_WCE);...
2014 Dec 11
0
[PATCH RFC v6 03/20] virtio: feature bit manipulation helpers
...tures, VIRTIO_BLK_F_SEG_MAX);
+ virtio_add_feature(&features, VIRTIO_BLK_F_GEOMETRY);
+ virtio_add_feature(&features, VIRTIO_BLK_F_TOPOLOGY);
+ virtio_add_feature(&features, VIRTIO_BLK_F_BLK_SIZE);
+ virtio_add_feature(&features, VIRTIO_BLK_F_SCSI);
if (s->conf.config_wce) {
- features |= (1 << VIRTIO_BLK_F_CONFIG_WCE);
+ virtio_add_feature(&features, VIRTIO_BLK_F_CONFIG_WCE);
}
if (blk_enable_write_cache(s->blk)) {
- features |= (1 << VIRTIO_BLK_F_WCE);
+ virtio_add_feature(&features, VIRTIO_BLK_F_WCE);...
2014 Oct 07
18
[PATCH RFC 00/11] qemu: towards virtio-1 host support
This patchset aims to get us some way to implement virtio-1 compliant
and transitional devices in qemu. Branch available at
git://github.com/cohuck/qemu virtio-1
I've mainly focused on:
- endianness handling
- extended feature bits
- virtio-ccw new/changed commands
Thanks go to Thomas for some preliminary work in this area.
I've been able to start guests both with and without the
2014 Oct 07
18
[PATCH RFC 00/11] qemu: towards virtio-1 host support
This patchset aims to get us some way to implement virtio-1 compliant
and transitional devices in qemu. Branch available at
git://github.com/cohuck/qemu virtio-1
I've mainly focused on:
- endianness handling
- extended feature bits
- virtio-ccw new/changed commands
Thanks go to Thomas for some preliminary work in this area.
I've been able to start guests both with and without the
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