From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Harsh Prateek Bora" <harshpb@linux.ibm.com>
Cc: <qemu-ppc@nongnu.org>, <qemu-devel@nongnu.org>
Subject: Re: [PATCH 6/6] target/ppc: Implement HEIR SPR
Date: Mon, 15 May 2023 18:26:00 +1000 [thread overview]
Message-ID: <CSMPI9KZ5TT5.GAWG3D1ZUQ3H@wheely> (raw)
In-Reply-To: <ZFoXjN/PUyDhMDG1@li-1901474c-32f3-11b2-a85c-fc5ff2c001f3.ibm.com>
On Tue May 9, 2023 at 7:51 PM AEST, Harsh Prateek Bora wrote:
> On Thu, Mar 23, 2023 at 12:22:37PM +1000, Nicholas Piggin wrote:
> > The hypervisor emulation assistance interrupt modifies HEIR to
> > contain the value of the instruction which caused the exception.
> >
> > Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> > ---
> > target/ppc/cpu.h | 1 +
> > target/ppc/cpu_init.c | 23 +++++++++++++++++++++++
> > target/ppc/excp_helper.c | 12 +++++++++++-
> > 3 files changed, 35 insertions(+), 1 deletion(-)
> >
>
> <snip>
>
> > diff --git a/target/ppc/excp_helper.c b/target/ppc/excp_helper.c
> > index 2e0321ab69..d206903562 100644
> > --- a/target/ppc/excp_helper.c
> > +++ b/target/ppc/excp_helper.c
> > @@ -1614,13 +1614,23 @@ static void powerpc_excp_books(PowerPCCPU *cpu, int excp)
> > case POWERPC_EXCP_HDECR: /* Hypervisor decrementer exception */
> > case POWERPC_EXCP_HDSI: /* Hypervisor data storage exception */
> > case POWERPC_EXCP_SDOOR_HV: /* Hypervisor Doorbell interrupt */
> > - case POWERPC_EXCP_HV_EMU:
> > case POWERPC_EXCP_HVIRT: /* Hypervisor virtualization */
> > srr0 = SPR_HSRR0;
> > srr1 = SPR_HSRR1;
> > new_msr |= (target_ulong)MSR_HVB;
> > new_msr |= env->msr & ((target_ulong)1 << MSR_RI);
> > break;
> > + case POWERPC_EXCP_HV_EMU:
> > + env->spr[SPR_HEIR] = insn;
> > + if (is_prefix_excp(env, insn)) {
> > + uint32_t insn2 = ppc_ldl_code(env, env->nip + 4);
> > + env->spr[SPR_HEIR] |= (uint64_t)insn2 << 32;
> > + }
> > + srr0 = SPR_HSRR0;
> > + srr1 = SPR_HSRR1;
> > + new_msr |= (target_ulong)MSR_HVB;
> > + new_msr |= env->msr & ((target_ulong)1 << MSR_RI);
> > + break;
>
> Since there is a common code, this could be better written like:
> case POWERPC_EXCP_HV_EMU:
> env->spr[SPR_HEIR] = insn;
> if (is_prefix_excp(env, insn)) {
> uint32_t insn2 = ppc_ldl_code(env, env->nip + 4);
> env->spr[SPR_HEIR] |= (uint64_t)insn2 << 32;
> }
> /* fall through below common code for EXCP_HVIRT */
> case POWERPC_EXCP_HVIRT: /* Hypervisor virtualization */
> srr0 = SPR_HSRR0;
> srr1 = SPR_HSRR1;
> new_msr |= (target_ulong)MSR_HVB;
> new_msr |= env->msr & ((target_ulong)1 << MSR_RI);
> break;
That would be wrong for the other HSRR fallthroughs above it.
Thanks,
Nick
next prev parent reply other threads:[~2023-05-15 8:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 2:22 [PATCH 1/6] target/ppc: Fix width of some 32-bit SPRs Nicholas Piggin
2023-03-23 2:22 ` [PATCH 2/6] target/ppc: Better CTRL SPR implementation Nicholas Piggin
2023-03-23 2:22 ` [PATCH 3/6] target/ppc: Fix instruction loading endianness in alignment interrupt Nicholas Piggin
2023-03-24 13:30 ` Fabiano Rosas
2023-03-27 4:25 ` Nicholas Piggin
2023-03-23 2:22 ` [PATCH 4/6] target/ppc: Alignment faults do not set DSISR in ISA v3.0 onward Nicholas Piggin
2023-03-24 13:39 ` Fabiano Rosas
2023-03-27 4:26 ` Nicholas Piggin
2023-03-23 2:22 ` [PATCH 5/6] target/ppc: Add SRR1 prefix indication to interrupt handlers Nicholas Piggin
2023-03-23 2:22 ` [PATCH 6/6] target/ppc: Implement HEIR SPR Nicholas Piggin
2023-05-09 9:51 ` Harsh Prateek Bora
2023-05-15 8:26 ` Nicholas Piggin [this message]
2023-05-15 8:32 ` Harsh Prateek Bora
2023-05-15 9:32 ` Harsh Prateek Bora
2023-05-15 10:45 ` Nicholas Piggin
2023-05-15 10:54 ` Harsh Prateek Bora
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=CSMPI9KZ5TT5.GAWG3D1ZUQ3H@wheely \
--to=npiggin@gmail.com \
--cc=harshpb@linux.ibm.com \
--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).