From: "Durrant, Paul" <xadimgnik@gmail.com>
To: Ross Lagerwall <ross.lagerwall@citrix.com>,
Stefano Stabellini <sstabellini@kernel.org>,
Anthony Perard <anthony.perard@citrix.com>,
Paul Durrant <paul@xen.org>
Cc: xen-devel@lists.xenproject.org, qemu-devel@nongnu.org
Subject: Re: [PATCH] xen-hvm: Avoid livelock while handling buffered ioreqs
Date: Sat, 6 Apr 2024 11:58:02 +0100 [thread overview]
Message-ID: <6fad8151-4bde-4a02-96fb-27b99d93757f@gmail.com> (raw)
In-Reply-To: <20240404140833.1557953-1-ross.lagerwall@citrix.com>
On 04/04/2024 15:08, Ross Lagerwall wrote:
> A malicious or buggy guest may generated buffered ioreqs faster than
> QEMU can process them in handle_buffered_iopage(). The result is a
> livelock - QEMU continuously processes ioreqs on the main thread without
> iterating through the main loop which prevents handling other events,
> processing timers, etc. Without QEMU handling other events, it often
> results in the guest becoming unsable and makes it difficult to stop the
> source of buffered ioreqs.
>
> To avoid this, if we process a full page of buffered ioreqs, stop and
> reschedule an immediate timer to continue processing them. This lets
> QEMU go back to the main loop and catch up.
>
Do PV backends potentially cause the same scheduling issue (if not using
io threads)?
> Signed-off-by: Ross Lagerwall <ross.lagerwall@citrix.com>
> ---
> hw/xen/xen-hvm-common.c | 26 +++++++++++++++++---------
> 1 file changed, 17 insertions(+), 9 deletions(-)
>
Reviewed-by: Paul Durrant <paul@xen.org>
next prev parent reply other threads:[~2024-04-06 10:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-04 14:08 [PATCH] xen-hvm: Avoid livelock while handling buffered ioreqs Ross Lagerwall
2024-04-06 10:58 ` Durrant, Paul [this message]
2024-04-08 13:00 ` Ross Lagerwall
2024-04-08 13:10 ` Paul Durrant
2024-04-08 13:12 ` Paul Durrant
2024-04-09 10:20 ` Anthony PERARD
2024-04-09 14:19 ` Ross Lagerwall
2024-04-09 14:35 ` Peter Maydell
2024-05-23 11:00 ` Ross Lagerwall
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6fad8151-4bde-4a02-96fb-27b99d93757f@gmail.com \
--to=xadimgnik@gmail.com \
--cc=anthony.perard@citrix.com \
--cc=paul@xen.org \
--cc=qemu-devel@nongnu.org \
--cc=ross.lagerwall@citrix.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).