search for: rpoc

...> > > disable virtio 1.0 in transports that don't > > support it yet. > > I'd prefer if you disabled it for _every_ transport in this patch, > until the needed infrastructure is in place. Else this is a bit > confusing. Well the only transports left are pci and rpoc, and these only read the low 32 bit of the features from the device - so there's nothing to clear. E.g. the following would be even more confusing, would it not: u32 features; .... features &= ~BIT_ULL(VIRTIO_F_VERSION_1); Agree? > > We will gradually re-enable as support is ad...

...> > > disable virtio 1.0 in transports that don't > > support it yet. > > I'd prefer if you disabled it for _every_ transport in this patch, > until the needed infrastructure is in place. Else this is a bit > confusing. Well the only transports left are pci and rpoc, and these only read the low 32 bit of the features from the device - so there's nothing to clear. E.g. the following would be even more confusing, would it not: u32 features; .... features &= ~BIT_ULL(VIRTIO_F_VERSION_1); Agree? > > We will gradually re-enable as support is ad...

...in transports that don't > > > support it yet. > > > > I'd prefer if you disabled it for _every_ transport in this patch, > > until the needed infrastructure is in place. Else this is a bit > > confusing. > > Well the only transports left are pci and rpoc, and these only > read the low 32 bit of the features from the device - > so there's nothing to clear. > > E.g. the following would be even more confusing, would it not: > > u32 features; > .... > features &= ~BIT_ULL(VIRTIO_F_VERSION_1); > > Agree? Mayb...

...gt; > > support it yet. > > > > > > I'd prefer if you disabled it for _every_ transport in this patch, > > > until the needed infrastructure is in place. Else this is a bit > > > confusing. > > > > Well the only transports left are pci and rpoc, and these only > > read the low 32 bit of the features from the device - > > so there's nothing to clear. > > > > E.g. the following would be even more confusing, would it not: > > > > u32 features; > > .... > > features &= ~BIT_ULL(VIRT...

...gt; > > support it yet. > > > > > > I'd prefer if you disabled it for _every_ transport in this patch, > > > until the needed infrastructure is in place. Else this is a bit > > > confusing. > > > > Well the only transports left are pci and rpoc, and these only > > read the low 32 bit of the features from the device - > > so there's nothing to clear. > > > > E.g. the following would be even more confusing, would it not: > > > > u32 features; > > .... > > features &= ~BIT_ULL(VIRT...

disable virtio 1.0 in transports that don't support it yet. We will gradually re-enable as support is added. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/lguest/lguest_device.c | 3 ++- drivers/misc/mic/card/mic_virtio.c | 2 ++ drivers/s390/kvm/virtio_ccw.c | 3 ++- drivers/virtio/virtio_mmio.c | 2 ++ 4 files changed, 8 insertions(+), 2

disable virtio 1.0 in transports that don't support it yet. We will gradually re-enable as support is added. Signed-off-by: Michael S. Tsirkin <mst at redhat.com> --- drivers/lguest/lguest_device.c | 3 ++- drivers/misc/mic/card/mic_virtio.c | 2 ++ drivers/s390/kvm/virtio_ccw.c | 3 ++- drivers/virtio/virtio_mmio.c | 2 ++ 4 files changed, 8 insertions(+), 2