From: Fabiano Rosas <farosas@linux.ibm.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, qemu-devel@nongnu.org
Cc: danielhb413@gmail.com, qemu-ppc@nongnu.org, clg@kaod.org,
david@gibson.dropbear.id.au
Subject: Re: [PATCH 0/8] target/ppc: powerpc_excp improvements [74xx] (5/n)
Date: Thu, 27 Jan 2022 12:16:55 -0300 [thread overview]
Message-ID: <87a6fhqkd4.fsf@linux.ibm.com> (raw)
In-Reply-To: <d592e76d-cb1f-7594-39ae-895fb4811242@ilande.co.uk>
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> writes:
> On 26/01/2022 16:41, Fabiano Rosas wrote:
>
>> This handles the exception code for the 74xx family, i.e. 7400, 7410,
>> 7440, 7445, 7450, 7455, 7457.
>>
>> This is another family that is quite well known, so it should be
>> straight-forward as well.
>>
>> Based on legoater/ppc-7.0
>>
>> Fabiano Rosas (8):
>> target/ppc: Introduce powerpc_excp_74xx
>> target/ppc: Simplify powerpc_excp_74xx
>> target/ppc: 74xx: Machine Check exception cleanup
>> target/ppc: 74xx: External interrupt cleanup
>> target/ppc: 74xx: Program exception cleanup
>> target/ppc: 74xx: System Call exception cleanup
>> target/ppc: 74xx: System Reset interrupt cleanup
>> target/ppc: 74xx: Set SRRs directly in exception code
>>
>> target/ppc/excp_helper.c | 175 +++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 175 insertions(+)
>
> I'm not overly familiar with PPC exception handling detail, so I can't offer much in
> the way of review I'm afraid. I could do a quick test and make sure nothing breaks
> with my MacOS images though?
Sure, no problem. This is more of an FYI and so you know whom to yell at
in case anything breaks for you.
I have some MacOS images I can use to test as well. I'll do a thorough
pass before sending the v2.
> Also any thoughts on Christophe's question re: e300 PVRs at
> https://lists.gnu.org/archive/html/qemu-ppc/2022-01/msg00592.html? I can handle
> merging the OpenBIOS changes if someone can come up with a suitable fix.
I believe Cédric has been looking at the 60x, maybe he has some
input. We currently can only run the 604 if I'm not mistaken, so there's
some work to be done to bring all of the 60x back to life. The e300 will
be in the mix.
next prev parent reply other threads:[~2022-01-27 16:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 16:41 [PATCH 0/8] target/ppc: powerpc_excp improvements [74xx] (5/n) Fabiano Rosas
2022-01-26 16:41 ` [PATCH 1/8] target/ppc: Introduce powerpc_excp_74xx Fabiano Rosas
2022-01-26 16:41 ` [PATCH 2/8] target/ppc: Simplify powerpc_excp_74xx Fabiano Rosas
2022-01-26 16:41 ` [PATCH 3/8] target/ppc: 74xx: Machine Check exception cleanup Fabiano Rosas
2022-01-26 16:41 ` [PATCH 4/8] target/ppc: 74xx: External interrupt cleanup Fabiano Rosas
2022-01-26 16:41 ` [PATCH 5/8] target/ppc: 74xx: Program exception cleanup Fabiano Rosas
2022-01-26 16:41 ` [PATCH 6/8] target/ppc: 74xx: System Call " Fabiano Rosas
2022-01-26 16:41 ` [PATCH 7/8] target/ppc: 74xx: System Reset interrupt cleanup Fabiano Rosas
2022-01-26 16:42 ` [PATCH 8/8] target/ppc: 74xx: Set SRRs directly in exception code Fabiano Rosas
2022-01-26 17:55 ` [PATCH 0/8] target/ppc: powerpc_excp improvements [74xx] (5/n) BALATON Zoltan
2022-01-26 18:23 ` Cédric Le Goater
2022-01-26 20:00 ` BALATON Zoltan
2022-01-26 21:58 ` Fabiano Rosas
2022-01-27 14:40 ` Mark Cave-Ayland
2022-01-27 15:16 ` Fabiano Rosas [this message]
2022-01-27 16:51 ` 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=87a6fhqkd4.fsf@linux.ibm.com \
--to=farosas@linux.ibm.com \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=mark.cave-ayland@ilande.co.uk \
--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).