From: Richard Henderson <richard.henderson@linaro.org>
To: Peter Maydell <peter.maydell@linaro.org>, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
qemu-stable@nongnu.org,
"Aaron Lindsay" <aaron@os.amperecomputing.com>
Subject: Re: [PATCH] Revert "accel/tcg: Init TCG cflags in vCPU thread handler"
Date: Sat, 22 Oct 2022 19:40:09 +1000 [thread overview]
Message-ID: <321f6e49-8370-07d1-47d3-53267e7dc4d3@linaro.org> (raw)
In-Reply-To: <20221021163409.3674911-1-peter.maydell@linaro.org>
On 10/22/22 02:34, Peter Maydell wrote:
> Commit a82fd5a4ec24d was intended to be a code cleanup, but
> unfortunately it has a bug. It moves the initialization of the
> TCG cflags from the "start a new vcpu" function to the
> thread handler; this is fine when each vcpu has its own thread,
> but when we are doing round-robin of vcpus on a single thread
> we end up only initializing the cflags for CPU 0, not for any
> of the others.
>
> The most obvious effect of this bug is that running in icount
> mode with more than one CPU is broken; typically the guest
> hangs shortly after it brings up the secondary CPUs.
>
> This reverts commit a82fd5a4ec24d923ff1e6da128c0fd4a74079d99.
>
> Cc:qemu-stable@nongnu.org
> Signed-off-by: Peter Maydell<peter.maydell@linaro.org>
> ---
> accel/tcg/tcg-accel-ops-mttcg.c | 5 +++--
> accel/tcg/tcg-accel-ops-rr.c | 7 ++++---
> 2 files changed, 7 insertions(+), 5 deletions(-)
Sorry about that,
Reviewed-by: Richard Henderson <richard.henderson@linaro.org>
r~
next prev parent reply other threads:[~2022-10-22 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 16:34 [PATCH] Revert "accel/tcg: Init TCG cflags in vCPU thread handler" Peter Maydell
2022-10-22 9:40 ` Richard Henderson [this message]
2022-10-22 10:03 ` Richard Henderson
2022-10-23 20:58 ` 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=321f6e49-8370-07d1-47d3-53267e7dc4d3@linaro.org \
--to=richard.henderson@linaro.org \
--cc=aaron@os.amperecomputing.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).