search for: f_bad

Displaying 5 results from an estimated 5 matches for "f_bad".

2015 May 13
1
[Qemu-devel] [PATCH RFC 4/7] vhost: set vring endianness for legacy virtio
...n just have a global mask. > > > > How would this work for transitional presenting a modern device - would > > you have a superset of bits and masks for legacy and modern? > > Basically we expose through modern interface a superset > of bits exposed through legacy. > F_BAD for pci is probably the only exception. ccw has F_BAD as well. NOTIFY_ON_EMPTY is in the MAY be offered category. I'm still wondering about the old legacy bits. Transitional devices not offering them is easiest to implement from the host side, but I'm wondering if all legacy devices will...
2015 May 13
1
[Qemu-devel] [PATCH RFC 4/7] vhost: set vring endianness for legacy virtio
...n just have a global mask. > > > > How would this work for transitional presenting a modern device - would > > you have a superset of bits and masks for legacy and modern? > > Basically we expose through modern interface a superset > of bits exposed through legacy. > F_BAD for pci is probably the only exception. ccw has F_BAD as well. NOTIFY_ON_EMPTY is in the MAY be offered category. I'm still wondering about the old legacy bits. Transitional devices not offering them is easiest to implement from the host side, but I'm wondering if all legacy devices will...
2015 May 12
2
[Qemu-devel] [PATCH RFC 4/7] vhost: set vring endianness for legacy virtio
On Tue, 12 May 2015 17:15:53 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Tue, May 12, 2015 at 03:25:30PM +0200, Cornelia Huck wrote: > > On Wed, 06 May 2015 14:08:02 +0200 > > Greg Kurz <gkurz at linux.vnet.ibm.com> wrote: > > > > > Legacy virtio is native endian: if the guest and host endianness differ, > > > we have to
2015 May 12
2
[Qemu-devel] [PATCH RFC 4/7] vhost: set vring endianness for legacy virtio
On Tue, 12 May 2015 17:15:53 +0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > On Tue, May 12, 2015 at 03:25:30PM +0200, Cornelia Huck wrote: > > On Wed, 06 May 2015 14:08:02 +0200 > > Greg Kurz <gkurz at linux.vnet.ibm.com> wrote: > > > > > Legacy virtio is native endian: if the guest and host endianness differ, > > > we have to
2015 May 12
0
[Qemu-devel] [PATCH RFC 4/7] vhost: set vring endianness for legacy virtio
...1, so maybe > > for now we can just have a global mask. > > How would this work for transitional presenting a modern device - would > you have a superset of bits and masks for legacy and modern? Basically we expose through modern interface a superset of bits exposed through legacy. F_BAD for pci is probably the only exception. > > > > We need to validate features at initialization time and make > > sure they make sense, fail if not (sometimes we need to mask > > features if they don't make sense - this is unfortunate > > but might be needed for...