Re: [RFC PATCH v2 1/5] virtio: introduce virtio_force_modern()

2021-11-16 Thread Halil Pasic
On Mon, 15 Nov 2021 17:57:28 +0100 Cornelia Huck wrote: > On Mon, Nov 15 2021, Halil Pasic wrote: > > > On Fri, 12 Nov 2021 16:37:20 +0100 > > Cornelia Huck wrote: > > > >> On Fri, Nov 12 2021, Halil Pasic wrote: > >> > >> > Legacy vs modern should be detected via transport specific mean

Re: [RFC PATCH v2 1/5] virtio: introduce virtio_force_modern()

2021-11-15 Thread Cornelia Huck
On Mon, Nov 15 2021, Halil Pasic wrote: > On Fri, 12 Nov 2021 16:37:20 +0100 > Cornelia Huck wrote: > >> On Fri, Nov 12 2021, Halil Pasic wrote: >> >> > Legacy vs modern should be detected via transport specific means. We >> > can't wait till feature negotiation is done. Let us introduce >> >

Re: [RFC PATCH v2 1/5] virtio: introduce virtio_force_modern()

2021-11-15 Thread Halil Pasic
On Fri, 12 Nov 2021 16:37:20 +0100 Cornelia Huck wrote: > On Fri, Nov 12 2021, Halil Pasic wrote: > > > Legacy vs modern should be detected via transport specific means. We > > can't wait till feature negotiation is done. Let us introduce > > virtio_force_modern() as a means for the transport c

Re: [RFC PATCH v2 1/5] virtio: introduce virtio_force_modern()

2021-11-12 Thread Cornelia Huck
On Fri, Nov 12 2021, Halil Pasic wrote: > Legacy vs modern should be detected via transport specific means. We > can't wait till feature negotiation is done. Let us introduce > virtio_force_modern() as a means for the transport code to signal > that the device should operate in modern mode (becau

[RFC PATCH v2 1/5] virtio: introduce virtio_force_modern()

2021-11-12 Thread Halil Pasic
Legacy vs modern should be detected via transport specific means. We can't wait till feature negotiation is done. Let us introduce virtio_force_modern() as a means for the transport code to signal that the device should operate in modern mode (because a modern driver was detected). A new callback