From: "Cédric Le Goater" <clg@kaod.org>
To: Nicholas Piggin <npiggin@gmail.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>
Cc: "Frédéric Barrat" <fbarrat@linux.ibm.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
qemu-stable@nongnu.org
Subject: Re: [PATCH 0/2] target/ppc: Fixes for hash MMU for ISA v3.0
Date: Fri, 21 Jul 2023 09:27:47 +0200 [thread overview]
Message-ID: <1ca45add-ef4a-db03-f033-e3fafd6203eb@kaod.org> (raw)
In-Reply-To: <20230721050255.100090-1-npiggin@gmail.com>
Hello Nick,
On 7/21/23 07:02, Nicholas Piggin wrote:
> This fixes a couple of deficiencies in the v3.0 and later (POWER9, 10)
> HPT MMU implementation. With these fixes, KVM is unable to boot hash
> guests on powernv9/10 machines. Bare metal hash or pseries machine with
> hash works, because VRMA is only used when a real hypervisor is
> virtualizing a hash guest's real mode addressing.
>
> Thanks,
> Nick
Could please add Fixes tags to your 'fix' patches ? No need to resend
just reply on the mailing list with :
Fixes: <commit> "subject"
Also for the "target/ppc: Fix pending HDEC when entering PM state" patch.
Thanks,
C.
> Nicholas Piggin (2):
> target/ppc: Implement ASDR register for ISA v3.0 for HPT
> target/ppc: Fix VRMA page size for ISA v3.0
>
> target/ppc/mmu-hash64.c | 68 ++++++++++++++++++++++++++++++-----------
> 1 file changed, 51 insertions(+), 17 deletions(-)
>
prev parent reply other threads:[~2023-07-21 7:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-21 5:02 [PATCH 0/2] target/ppc: Fixes for hash MMU for ISA v3.0 Nicholas Piggin
2023-07-21 5:02 ` [PATCH 1/2] target/ppc: Implement ASDR register for ISA v3.0 for HPT Nicholas Piggin
2023-07-21 5:02 ` [PATCH 2/2] target/ppc: Fix VRMA page size for ISA v3.0 Nicholas Piggin
2023-07-21 7:27 ` Cédric Le Goater [this message]
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=1ca45add-ef4a-db03-f033-e3fafd6203eb@kaod.org \
--to=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=fbarrat@linux.ibm.com \
--cc=groug@kaod.org \
--cc=harshpb@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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).