From: Fabiano Rosas <farosas@linux.ibm.com>
To: BALATON Zoltan <balaton@eik.bme.hu>
Cc: danielhb413@gmail.com, qemu-ppc@nongnu.org,
qemu-devel@nongnu.org, david@gibson.dropbear.id.au, clg@kaod.org
Subject: Re: [PATCH v2 8/8] target/ppc: 74xx: Set SRRs directly in exception code
Date: Thu, 27 Jan 2022 19:52:28 -0300 [thread overview]
Message-ID: <877dakrdub.fsf@linux.ibm.com> (raw)
In-Reply-To: <f93bbb9-82d4-6437-ca29-6413fe4a7375@eik.bme.hu>
BALATON Zoltan <balaton@eik.bme.hu> writes:
> On Thu, 27 Jan 2022, Fabiano Rosas wrote:
>> The 74xx does not have alternate/hypervisor Save and Restore
>> Registers, so we can set SRR0 and SRR1 directly.
>>
>> Signed-off-by: Fabiano Rosas <farosas@linux.ibm.com>
>> ---
>> target/ppc/excp_helper.c | 13 ++-----------
>> 1 file changed, 2 insertions(+), 11 deletions(-)
>>
>> diff --git a/target/ppc/excp_helper.c b/target/ppc/excp_helper.c
>> index b7921c0956..4e6bb87b70 100644
>> --- a/target/ppc/excp_helper.c
>> +++ b/target/ppc/excp_helper.c
>> @@ -556,7 +556,6 @@ static void powerpc_excp_74xx(PowerPCCPU *cpu, int excp)
>> CPUState *cs = CPU(cpu);
>> CPUPPCState *env = &cpu->env;
>> target_ulong msr, new_msr, vector;
>> - int srr0, srr1;
>>
>> if (excp <= POWERPC_EXCP_NONE || excp >= POWERPC_EXCP_NB) {
>> cpu_abort(cs, "Invalid PowerPC exception %d. Aborting\n", excp);
>> @@ -575,10 +574,6 @@ static void powerpc_excp_74xx(PowerPCCPU *cpu, int excp)
>> */
>> new_msr = env->msr & ((target_ulong)1 << MSR_ME);
>>
>> - /* target registers */
>> - srr0 = SPR_SRR0;
>> - srr1 = SPR_SRR1;
>> -
>> /*
>> * Hypervisor emulation assistance interrupt only exists on server
>> * arch 2.05 server or later.
>> @@ -731,10 +726,6 @@ static void powerpc_excp_74xx(PowerPCCPU *cpu, int excp)
>> cpu_abort(cs, "Trying to deliver HV exception (MSR) %d with "
>> "no HV support\n", excp);
>> }
>
> If we have ho MSR_HVB why is this still here? Shouldn't it have been gone
> in patch 2? Or is this still reachable?
It is still reachable. Any of the individual exceptions above could set
the wrong bit. I have been keeping this block for all CPUs because I
intend to extract this sanity check to an outer function after I move
all CPU families.
In the long run I think we should validate MSR against the whole
msr_mask instead of just checking this single bit. But I am not
confident that today all the bits that are set are also present in the
corresponding location in the msr_mask.
>> - If (srr0 == SPR_HSRR0) {
>> - cpu_abort(cs, "Trying to deliver HV exception (HSRR) %d with "
>> - "no HV support\n", excp);
>> - }
>> }
>>
>> /*
>> @@ -746,10 +737,10 @@ static void powerpc_excp_74xx(PowerPCCPU *cpu, int excp)
>> }
>>
>> /* Save PC */
>> - env->spr[srr0] = env->nip;
>> + env->spr[SPR_SRR0] = env->nip;
>>
>> /* Save MSR */
>> - env->spr[srr1] = msr;
>> + env->spr[SPR_SRR1] = msr;
>>
>> powerpc_set_excp_state(cpu, vector, new_msr);
>> }
>>
next prev parent reply other threads:[~2022-01-27 22:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 20:11 [PATCH v2 0/8] target/ppc: powerpc_excp improvements [74xx] (5/n) Fabiano Rosas
2022-01-27 20:11 ` [PATCH v2 1/8] target/ppc: Introduce powerpc_excp_74xx Fabiano Rosas
2022-01-27 20:11 ` [PATCH v2 2/8] target/ppc: Simplify powerpc_excp_74xx Fabiano Rosas
2022-01-27 20:11 ` [PATCH v2 3/8] target/ppc: 74xx: Machine Check exception cleanup Fabiano Rosas
2022-01-27 20:11 ` [PATCH v2 4/8] target/ppc: 74xx: External interrupt cleanup Fabiano Rosas
2022-01-27 20:11 ` [PATCH v2 5/8] target/ppc: 74xx: Program exception cleanup Fabiano Rosas
2022-01-27 20:11 ` [PATCH v2 6/8] target/ppc: 74xx: System Call " Fabiano Rosas
2022-01-27 22:20 ` BALATON Zoltan
2022-01-27 20:11 ` [PATCH v2 7/8] target/ppc: 74xx: System Reset interrupt cleanup Fabiano Rosas
2022-01-27 20:11 ` [PATCH v2 8/8] target/ppc: 74xx: Set SRRs directly in exception code Fabiano Rosas
2022-01-27 22:28 ` BALATON Zoltan
2022-01-27 22:37 ` BALATON Zoltan
2022-01-27 22:52 ` Fabiano Rosas [this message]
2022-01-27 21:29 ` [PATCH v2 0/8] target/ppc: powerpc_excp improvements [74xx] (5/n) Mark Cave-Ayland
2022-01-27 22:58 ` BALATON Zoltan
2022-01-27 23:08 ` Fabiano Rosas
2022-01-27 23:16 ` Mark Cave-Ayland
2022-01-30 18:11 ` 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=877dakrdub.fsf@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=balaton@eik.bme.hu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--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).