[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221227042855-mutt-send-email-mst@kernel.org>
Date: Tue, 27 Dec 2022 04:31:08 -0500
From: "Michael S. Tsirkin" <mst@...hat.com>
To: Jason Wang <jasowang@...hat.com>
Cc: Xuan Zhuo <xuanzhuo@...ux.alibaba.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org,
virtualization@...ts.linux-foundation.org, eperezma@...hat.com,
edumazet@...gle.com, maxime.coquelin@...hat.com, kuba@...nel.org,
pabeni@...hat.com, davem@...emloft.net
Subject: Re: [PATCH 4/4] virtio-net: sleep instead of busy waiting for cvq
command
On Tue, Dec 27, 2022 at 05:17:20PM +0800, Jason Wang wrote:
> > > > In particular, we will also directly break the device.
> > > It's kind of hardening for malicious devices.
> > ATM no amount of hardening can prevent a malicious hypervisor from
> > blocking the guest. Recovering when a hardware device is broken would be
> > nice but I think if we do bother then we should try harder to recover,
> > such as by driving device reset.
>
>
> Probably, but as discussed in another thread, it needs co-operation in the
> upper layer (networking core).
To track all state? Yea, maybe. For sure it's doable just in virtio,
but if you can find 1-2 other drivers that do this internally
then factoring this out to net core will likely be accepted.
--
MST
Powered by blists - more mailing lists