From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
"Laurent Vivier" <laurent@vivier.eu>,
"Aleksandar Markovic" <amarkovic@wavecomp.com>,
"Michael Walle" <michael@walle.cc>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Aleksandar Rikalo" <aleksandar.rikalo@rt-rk.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
"Aurelien Jarno" <aurelien@aurel32.net>,
"Bastian Koppelmann" <kbastian@mail.uni-paderborn.de>
Subject: [PATCH 0/2] cpu: Avoid latent bug calling cpu_reset() on uninitialized vCPU
Date: Mon, 9 Mar 2020 13:11:01 +0100 [thread overview]
Message-ID: <20200309121103.20234-1-philmd@redhat.com> (raw)
Two trivial patches to avoid each (new) architecture to track
a bug already resolved once on ARM: cpu_reset() modify fields
in the CpuState while the state is not yet allocated.
Philippe Mathieu-Daudé (2):
cpu: Do not reset a vCPU before it is created
cpu: Assert a vCPU is created before resetting it
hw/core/cpu.c | 1 +
target/cris/cpu.c | 2 +-
target/lm32/cpu.c | 3 +--
target/m68k/cpu.c | 2 +-
target/mips/cpu.c | 2 +-
target/sh4/cpu.c | 2 +-
target/tilegx/cpu.c | 2 +-
target/tricore/cpu.c | 2 +-
8 files changed, 8 insertions(+), 8 deletions(-)
--
2.21.1
next reply other threads:[~2020-03-09 12:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 12:11 Philippe Mathieu-Daudé [this message]
2020-03-09 12:11 ` [PATCH 1/2] cpu: Do not reset a vCPU before it is created Philippe Mathieu-Daudé
2020-03-09 13:08 ` Laurent Vivier
2020-03-09 13:09 ` Peter Maydell
2020-03-09 13:13 ` Laurent Vivier
2020-03-09 13:18 ` Peter Maydell
2020-03-09 13:28 ` Laurent Vivier
2020-03-09 12:11 ` [PATCH 2/2] cpu: Assert a vCPU is created before resetting it Philippe Mathieu-Daudé
2020-03-09 13:10 ` Peter Maydell
2020-03-09 15:30 ` 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=20200309121103.20234-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=aleksandar.rikalo@rt-rk.com \
--cc=amarkovic@wavecomp.com \
--cc=aurelien@aurel32.net \
--cc=edgar.iglesias@gmail.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=kbastian@mail.uni-paderborn.de \
--cc=laurent@vivier.eu \
--cc=michael@walle.cc \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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).