From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Fabiano Rosas" <farosas@suse.de>, <qemu-ppc@nongnu.org>
Cc: qemu-devel@nongnu.org,
"Christophe Leroy" <christophe.leroy@csgroup.eu>,
"BALATON Zoltan" <balaton@eik.bme.hu>,
"Harsh Prateek Bora" <harshpb@linux.ibm.com>,
"Daniel Henrique Barboza" <danielhb413@gmail.com>,
"Cédric Le Goater" <clg@kaod.org>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Greg Kurz" <groug@kaod.org>
Subject: Re: [PATCH 3/4] target/ppc: Move common check in machne check handlers to a function
Date: Sun, 25 Jun 2023 19:20:48 +1000 [thread overview]
Message-ID: <CTLMCKAEF701.1EU64K055P8A6@wheely> (raw)
In-Reply-To: <87edm2s4bh.fsf@suse.de>
On Fri Jun 23, 2023 at 11:20 PM AEST, Fabiano Rosas wrote:
> Nicholas Piggin <npiggin@gmail.com> writes:
>
> > From: BALATON Zoltan <balaton@eik.bme.hu>
> >
> > All powerpc exception handlers share some code when handling machine
> > check exceptions. Move this to a common function.
> >
>
> Maybe Machine Check is simple enough, but this kind of sharing of code
> has historically caused pain when people want to change something for
> the modern cpus and end up affecting the old cpus by mistake.
>
> There is also the inverse scenario where someone has access to the old
> HW and just want to make an one-off contribution, but the community gets
> insecure about it because it could also affect the new cpus.
>
> Then comes the obvious "solution" which is to bring in an artificial
> identifier (excp. model) to be able to have conditional code inside the
> common function. And that causes problems because no one really knows
> how it maps to actual hardware/ISA.
>
> No objection, just a little cautionary tale. =)
Thanks Fabiano, good point. I know you spent a lot of work on untangling
this mess. I'll think a bit more about it. Seems we need to at least make
a few fixes first before we can turn this on for upstream.
Thanks,
Nick
next prev parent reply other threads:[~2023-06-25 9:21 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-23 8:19 [PATCH 0/4] target/ppc: Catch invalid real address accesses Nicholas Piggin
2023-06-23 8:19 ` [PATCH 1/4] target/ppc: Machine check on invalid real address access Nicholas Piggin
2023-06-23 8:19 ` [PATCH 2/4] target/ppc: Add POWER9/10 invalid-real machine check codes Nicholas Piggin
2023-06-23 8:19 ` [PATCH 3/4] target/ppc: Move common check in machne check handlers to a function Nicholas Piggin
2023-06-23 13:20 ` Fabiano Rosas
2023-06-23 16:16 ` BALATON Zoltan
2023-06-25 9:20 ` Nicholas Piggin [this message]
2023-06-23 8:19 ` [PATCH 4/4] target/ppc: Make checkstop stop the system Nicholas Piggin
2023-06-23 11:51 ` BALATON Zoltan
2023-06-25 9:15 ` Nicholas Piggin
2023-06-23 9:10 ` [PATCH 0/4] target/ppc: Catch invalid real address accesses Peter Maydell
2023-06-23 12:37 ` Cédric Le Goater
2023-06-23 23:35 ` Philippe Mathieu-Daudé
2023-06-24 9:50 ` BALATON Zoltan
2023-06-26 13:35 ` Cédric Le Goater
2023-06-26 23:28 ` Nicholas Piggin
2023-06-27 6:49 ` Cédric Le Goater
2023-06-27 8:14 ` Mark Cave-Ayland
2023-06-27 10:28 ` Howard Spoelstra
2023-06-27 11:24 ` Mark Cave-Ayland
2023-06-27 12:05 ` Howard Spoelstra
2023-06-27 12:41 ` Cédric Le Goater
2023-06-27 20:26 ` Mark Cave-Ayland
2023-06-28 7:02 ` Cédric Le Goater
2023-06-28 7:17 ` Cédric Le Goater
2023-06-29 8:29 ` Mark Cave-Ayland
2023-06-29 9:05 ` Cédric Le Goater
2023-06-29 9:41 ` Nicholas Piggin
2023-06-27 12:03 ` Cédric Le Goater
2023-06-27 20:24 ` Mark Cave-Ayland
2023-06-25 9:18 ` Nicholas Piggin
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=CTLMCKAEF701.1EU64K055P8A6@wheely \
--to=npiggin@gmail.com \
--cc=balaton@eik.bme.hu \
--cc=christophe.leroy@csgroup.eu \
--cc=clg@kaod.org \
--cc=danielhb413@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=farosas@suse.de \
--cc=groug@kaod.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.