From: Zenghui Yu <zenghui.yu@linux.dev>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-devel@nongnu.org, Mads Ynddal <mads@ynddal.dk>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, Alexander Graf <agraf@csgraf.de>
Subject: Re: [PATCH 2/2] target/arm: ensure PSCI register updates are flushed
Date: Tue, 9 Dec 2025 08:54:19 +0800 [thread overview]
Message-ID: <0c2f64fa-a635-4593-8631-12a40af4a79b@linux.dev> (raw)
In-Reply-To: <87zf7shped.fsf@draig.linaro.org>
On 2025/12/9 01:08, Alex Bennée wrote:
> Zenghui Yu <zenghui.yu@linux.dev> writes:
>
> > Hi Alex,
> >
> > On 2025/12/5 23:11, Alex Bennée wrote:
> > > When we handle a host call we report state back to the caller via
> > > registers. Set vcpu_dirty to indicate QEMU is currently the reference
> > > and hoist the flush_cpu_state() and make the call unconditional.
> > >
> > > Fixes: https://gitlab.com/qemu-project/qemu/-/issues/3228
> > > Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> >
> > This fixes the guest boot issue.
> >
> > However I notice that some (all?) HMP commands (e.g., "info registers")
> > don't return and result in guest hang. Haven't dig further though.
>
> Does this fix it:
>
> --8<---------------cut here---------------start------------->8---
> target/arm: make HV_EXIT_REASON_CANCELED leave main loop
>
> Without this we can spin tightly in the main HVF dispatch loop and
> never release the lock long enough.
>
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
>
> 1 file changed, 1 insertion(+)
> target/arm/hvf/hvf.c | 1 +
>
> modified target/arm/hvf/hvf.c
> @@ -2020,6 +2020,7 @@ static int hvf_handle_vmexit(CPUState *cpu, hv_vcpu_exit_t *exit)
> break;
> case HV_EXIT_REASON_CANCELED:
> /* we got kicked, no exit to process */
> + ret = -1;
> break;
> default:
> g_assert_not_reached();
> --8<---------------cut here---------------end--------------->8---
Yes it works. Please feel free to add
Tested-by: Zenghui Yu <zenghui.yu@linux.dev>
on it and patch #2. Thanks for the fixes!
Zenghui
next prev parent reply other threads:[~2025-12-09 0:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 15:11 [PATCH 0/2] target/arm: fix for hvf regression in v10.2-rc1 (#3228) Alex Bennée
2025-12-05 15:11 ` [PATCH 1/2] Revert "target/arm: Re-use arm_is_psci_call() in HVF" Alex Bennée
2025-12-09 7:02 ` Philippe Mathieu-Daudé
2025-12-05 15:11 ` [PATCH 2/2] target/arm: ensure PSCI register updates are flushed Alex Bennée
2025-12-08 15:30 ` Zenghui Yu
2025-12-08 17:08 ` Alex Bennée
2025-12-09 0:54 ` Zenghui Yu [this message]
2025-12-09 4:48 ` osy
2025-12-09 7:04 ` Philippe Mathieu-Daudé
2025-12-09 7:04 ` Philippe Mathieu-Daudé
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=0c2f64fa-a635-4593-8631-12a40af4a79b@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=agraf@csgraf.de \
--cc=alex.bennee@linaro.org \
--cc=mads@ynddal.dk \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.