[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240122154255.GA389442@fedora>
Date: Mon, 22 Jan 2024 10:42:55 -0500
From: Stefan Hajnoczi <stefanha@...hat.com>
To: Yi Sun <yi.sun@...soc.com>
Cc: axboe@...nel.dk, mst@...hat.com, jasowang@...hat.com,
xuanzhuo@...ux.alibaba.com, pbonzini@...hat.com,
virtualization@...ts.linux.dev, linux-block@...r.kernel.org,
linux-kernel@...r.kernel.org, zhiguo.niu@...soc.com,
hongyu.jin@...soc.com, sunyibuaa@...il.com
Subject: Re: [PATCH 2/2] virtio-blk: Ensure no requests in virtqueues before
deleting vqs.
On Mon, Jan 22, 2024 at 07:07:22PM +0800, Yi Sun wrote:
> Ensure no remaining requests in virtqueues before resetting vdev and
> deleting virtqueues. Otherwise these requests will never be completed.
> It may cause the system to become unresponsive. So it is better to place
> blk_mq_quiesce_queue() in front of virtio_reset_device().
QEMU's virtio-blk device implementation completes all requests during
device reset. Most device implementations have to do the same to avoid
leaving dangling requests in flight across device reset.
Which device implementation are you using and why is it safe for the
device is simply drop requests across device reset?
Stefan
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists