From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Shawn Anastasio" <sanastasio@raptorengineering.com>,
"Cédric Le Goater" <clg@kaod.org>,
qemu-ppc@nongnu.org
Cc: <qemu-devel@nongnu.org>, "Greg Kurz" <groug@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Timothy Pearson" <tpearson@raptorengineering.com>,
"Frederic Barrat" <fbarrat@linux.ibm.com>
Subject: Re: [PATCH v2] target/ppc: Generate storage interrupts for radix RC changes
Date: Fri, 21 Jul 2023 12:38:01 +1000 [thread overview]
Message-ID: <CU7I2BT516P3.1NJPQWALJTVR@wheely> (raw)
In-Reply-To: <1004ffbe-8855-75d1-45e7-65360bfd1807@raptorengineering.com>
On Thu Jul 13, 2023 at 3:35 AM AEST, Shawn Anastasio wrote:
> On 7/12/23 11:56 AM, Cédric Le Goater wrote:
> > Hello Shawn,
> >
> > On 7/12/23 18:13, Shawn Anastasio wrote:
> >> Change radix model to always generate a storage interrupt when the R/C
> >> bits are not set appropriately in a PTE instead of setting the bits
> >> itself. According to the ISA both behaviors are valid, but in practice
> >> this change more closely matches behavior observed on the POWER9 CPU.
> >
> > How did you spotted this dark corner case in emulation ? Do you have
> > MMU unit tests ?
>
> I'm currently porting Xen to Power and have been using QEMU's powernv
> model extensively for early bring up. I noticed the issue when my radix
> implementation worked in QEMU but failed on actual hardware since I
> didn't have a proper storage interrupt handler implemented.
Cool. This was on my todo list because we rely on it for nested HV
KVM too.
I actually didn't know about that odd effLIPD=0 exception, but it
looks right. How did you test that, by running with MSR[HV]=0 and
LPIDR=0 ?
For the patch,
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
Thanks,
Nick
next prev parent reply other threads:[~2023-07-21 2:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-12 16:13 [PATCH v2] target/ppc: Generate storage interrupts for radix RC changes Shawn Anastasio
2023-07-12 16:56 ` Cédric Le Goater
2023-07-12 17:35 ` Shawn Anastasio
2023-07-21 2:38 ` Nicholas Piggin [this message]
2023-07-21 16:08 ` Daniel Henrique Barboza
2023-07-21 16:27 ` Cédric Le Goater
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=CU7I2BT516P3.1NJPQWALJTVR@wheely \
--to=npiggin@gmail.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=fbarrat@linux.ibm.com \
--cc=groug@kaod.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sanastasio@raptorengineering.com \
--cc=tpearson@raptorengineering.com \
/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).