From: Harsh Prateek Bora <harshpb@linux.ibm.com>
To: Nicholas Piggin <npiggin@gmail.com>, qemu-ppc@nongnu.org
Cc: qemu-devel@nongnu.org, Daniel Henrique Barboza <danielhb413@gmail.com>
Subject: Re: [PATCH] target/ppc: Add ISA v3.1 LEV indication in SRR1 for system call interrupts
Date: Wed, 21 Jun 2023 14:01:27 +0530 [thread overview]
Message-ID: <a3dce513-d55a-7116-c6f8-5d30e4f3d131@linux.ibm.com> (raw)
In-Reply-To: <20230620131321.169261-1-npiggin@gmail.com>
On 6/20/23 18:43, Nicholas Piggin wrote:
> System call interrupts in ISA v3.1 CPUs add a LEV indication in SRR1
> that corresponds with the LEV field of the instruction that caused the
> interrupt.
>
Did we encounter any issue without this patch leading to this fix?
If so, it will be great to talk about it in short if possible.
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
> ---
> This is unchanged, just taken out of the bigger series since it is
> independent.
>
> Thanks,
> Nick
>
> target/ppc/excp_helper.c | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/target/ppc/excp_helper.c b/target/ppc/excp_helper.c
> index 77bfc18734..c7550fea13 100644
> --- a/target/ppc/excp_helper.c
> +++ b/target/ppc/excp_helper.c
> @@ -1591,6 +1591,10 @@ static void powerpc_excp_books(PowerPCCPU *cpu, int excp)
> vhc->hypercall(cpu->vhyp, cpu);
> return;
> }
> + if (env->insns_flags2 & PPC2_ISA310) {
> + /* ISAv3.1 puts LEV into SRR1 */
> + msr |= lev << 20;
Since LEV values greater than 2 are reserved, should we do:
msr |= (lev <= 2) ? lev << 20 : 0;
Otherwise,
Reviewed-by: Harsh Prateek Bora <harshpb@linux.ibm.com>
> + }
> if (lev == 1) {
> new_msr |= (target_ulong)MSR_HVB;
> }
next prev parent reply other threads:[~2023-06-21 9:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-20 13:13 [PATCH] target/ppc: Add ISA v3.1 LEV indication in SRR1 for system call interrupts Nicholas Piggin
2023-06-21 8:31 ` Harsh Prateek Bora [this message]
2023-06-21 10:13 ` Nicholas Piggin
2023-06-23 9:32 ` 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=a3dce513-d55a-7116-c6f8-5d30e4f3d131@linux.ibm.com \
--to=harshpb@linux.ibm.com \
--cc=danielhb413@gmail.com \
--cc=npiggin@gmail.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).