search for: status_failed

...+0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > What does it mean if rev 1 device does not set > VIRTIO_F_VERSION_1? E.g. is it native endian? > > Let's not even try to drive such devices: > skip attempts to finalize features or set status. Why not set status_failed? > virtio core will detect this and bail out. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > --- > drivers/s390/kvm/virtio_ccw.c | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > I'm not sure yet whether I like this approach. I'll think...

...+0200 "Michael S. Tsirkin" <mst at redhat.com> wrote: > What does it mean if rev 1 device does not set > VIRTIO_F_VERSION_1? E.g. is it native endian? > > Let's not even try to drive such devices: > skip attempts to finalize features or set status. Why not set status_failed? > virtio core will detect this and bail out. > > Signed-off-by: Michael S. Tsirkin <mst at redhat.com> > --- > drivers/s390/kvm/virtio_ccw.c | 15 +++++++++++++++ > 1 file changed, 15 insertions(+) > I'm not sure yet whether I like this approach. I'll think...

transports need to be able to detect legacy-only devices (ATM balloon only) to use legacy path to drive them. Add a core API to do just that. The implementation just blacklists balloon: not too pretty, but let's not over-engineer. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- include/linux/virtio.h | 2 ++ drivers/virtio/virtio.c | 6 ++++++ 2 files changed, 8

transports need to be able to detect legacy-only devices (ATM balloon only) to use legacy path to drive them. Add a core API to do just that. The implementation just blacklists balloon: not too pretty, but let's not over-engineer. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- include/linux/virtio.h | 2 ++ drivers/virtio/virtio.c | 6 ++++++ 2 files changed, 8