qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Phil Dennis-Jordan <phil@philjordan.eu>, qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, philmd@linaro.org, akihiko.odaki@daynix.com
Subject: Re: [PATCH] system/runstate: Fix regression, clarify BQL status of exit notifiers
Date: Wed, 15 Jan 2025 19:01:14 +0100	[thread overview]
Message-ID: <876d003cfcb678d183f2a4ac349c3fb1c60eb5fd.camel@infradead.org> (raw)
In-Reply-To: <20250112212609.17996-1-phil@philjordan.eu>

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]

On Sun, 2025-01-12 at 22:26 +0100, Phil Dennis-Jordan wrote:
> By changing the way the main QEMU event loop is invoked, I inadvertently
> changed the BQL status of exit notifiers: some of them implicitly
> assumed they would be called with the BQL held; the BQL is however
> not held during the exit(status) call in qemu_default_main().
> 
> Instead of attempting to ensuring we always call exit() from the BQL -
> including any transitive calls - this change adds a BQL lock guard to
> qemu_run_exit_notifiers, ensuring the BQL will always be held in the
> exit notifiers.
> 
> Additionally, the BQL promise is now documented at the
> qemu_{add,remove}_exit_notifier() declarations.
> 
> Fixes: f5ab12caba4f ("ui & main loop: Redesign of system-specific main
> thread event handling")
> Resolves: https://gitlab.com/qemu-project/qemu/-/issues/2771
> Reported-by: David Woodhouse <dwmw2@infradead.org>
> Signed-off-by: Phil Dennis-Jordan <phil@philjordan.eu>

Reviewed-by: David Woodhouse <dwmw@amazon.co.uk>
Tested-by: David Woodhouse <dwmw@amazon.co.uk>

(Sorry, I thought I'd done that already).

Is someone else going to pick this up, or should I round it up with the
Xen fixes for which I'm likely to send a pull request tomorrow? 

[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5069 bytes --]

  reply	other threads:[~2025-01-15 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-12 21:26 [PATCH] system/runstate: Fix regression, clarify BQL status of exit notifiers Phil Dennis-Jordan
2025-01-15 18:01 ` David Woodhouse [this message]
2025-01-15 19:05 ` Paolo Bonzini
2025-01-15 19:17   ` Phil Dennis-Jordan
2025-01-16  8:34     ` David Woodhouse

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=876d003cfcb678d183f2a4ac349c3fb1c60eb5fd.camel@infradead.org \
    --to=dwmw2@infradead.org \
    --cc=akihiko.odaki@daynix.com \
    --cc=pbonzini@redhat.com \
    --cc=phil@philjordan.eu \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.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).