On Fri, Nov 20, 2020 at 06:51:07PM +, John Levon wrote:
>
> If we find a queue with an inconsistent guest index value, explicitly mark the
> device as needing a reset - and broken - via virtio_error().
>
> There's at least one driver implementation - the virtio-win NetKVM driver -
> that
>
No, but how about sending the patch to me and the mailing list?
I didn't get it through either channel.
On Mon, Nov 30, 2020 at 03:51:13PM +, John Levon wrote:
> On Fri, Nov 20, 2020 at 06:51:07PM +, John Levon wrote:
>
> > If we find a queue with an inconsistent guest index value,
On Fri, Nov 20, 2020 at 06:51:07PM +, John Levon wrote:
> If we find a queue with an inconsistent guest index value, explicitly mark the
> device as needing a reset - and broken - via virtio_error().
>
> There's at least one driver implementation - the virtio-win NetKVM driver -
> that
> is
If we find a queue with an inconsistent guest index value, explicitly mark the
device as needing a reset - and broken - via virtio_error().
There's at least one driver implementation - the virtio-win NetKVM driver - that
is able to handle a VIRTIO_CONFIG_S_NEEDS_RESET notification and
If we find a queue with an inconsistent guest index value, explicitly mark the
device as needing a reset - and broken - via virtio_error().
There's at least one driver implementation - the virtio-win NetKVM driver - that
is able to handle a VIRTIO_CONFIG_S_NEEDS_RESET notification and
