From: Nicholas Piggin <npiggin@gmail.com>
To: qemu-ppc@nongnu.org
Cc: "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org, "Nicholas Piggin" <npiggin@gmail.com>,
"David Gibson" <david@gibson.dropbear.id.au>
Subject: [PATCH v1 0/3] ppc: LPCR synchronisation fixes
Date: Wed, 26 May 2021 19:16:23 +1000 [thread overview]
Message-ID: <20210526091626.3388262-1-npiggin@gmail.com> (raw)
These incoherencies have been around for a while, but they've started
to get noticed now because recent Linux guests crash when LPCR[AIL] is
not set correctly (scv requires it). This series fixes at least AIL and
DPFD incoherency between KVM and QEMU, and between different vCPUs.
Thanks,
Nick
Nicholas Piggin (3):
spapr: Remove stale comment about power-saving LPCR bits
spapr: Set LPCR to current AIL mode when starting a new CPU
target/ppc: Synchronize with KVM's LPCR value when creating a vCPU
hw/ppc/spapr_cpu_core.c | 9 ++++++---
hw/ppc/spapr_rtas.c | 15 +++++++++------
target/ppc/kvm.c | 34 ++++++++++++++++++++--------------
3 files changed, 35 insertions(+), 23 deletions(-)
--
2.23.0
next reply other threads:[~2021-05-26 9:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-26 9:16 Nicholas Piggin [this message]
2021-05-26 9:16 ` [PATCH v1 1/3] spapr: Remove stale comment about power-saving LPCR bits Nicholas Piggin
2021-05-26 15:18 ` Cédric Le Goater
2021-05-26 15:42 ` Greg Kurz
2021-05-27 1:28 ` David Gibson
2021-05-26 9:16 ` [PATCH v1 2/3] spapr: Set LPCR to current AIL mode when starting a new CPU Nicholas Piggin
2021-05-26 15:24 ` Cédric Le Goater
2021-05-26 16:03 ` Greg Kurz
2021-05-27 1:29 ` David Gibson
2021-05-26 9:16 ` [PATCH v1 3/3] target/ppc: Synchronize with KVM's LPCR value when creating a vCPU Nicholas Piggin
2021-05-27 1:48 ` David Gibson
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=20210526091626.3388262-1-npiggin@gmail.com \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).