All of lore.kernel.org
 help / color / mirror / Atom feed
From: BALATON Zoltan <balaton@eik.bme.hu>
To: Fabiano Rosas <farosas@linux.ibm.com>
Cc: danielhb413@gmail.com, qemu-ppc@nongnu.org,
	qemu-devel@nongnu.org, david@gibson.dropbear.id.au, clg@kaod.org
Subject: Re: [PATCH 00/11] target/ppc: powerpc_excp improvements [BookE] (6/n)
Date: Sat, 29 Jan 2022 01:07:42 +0100 (CET)	[thread overview]
Message-ID: <c9bb63f8-c2e8-31e5-fe24-b9923c2c1821@eik.bme.hu> (raw)
In-Reply-To: <20220128224018.1228062-1-farosas@linux.ibm.com>

On Fri, 28 Jan 2022, Fabiano Rosas wrote:
> This series handles the BookE exception code.
>
> Tested the following machines/CPUs:
>
> == bamboo ==
> 440ep, 460ex, 440-xilinx-w-dfpu
>
> == sam460ex ==
> 440ep, 460ex, 440-xilinx-w-dfpu

What OS did you test with? Other than the 460ex may not make much sense 
on this board but checking it never hurts. If you only tried Linux kernel 
then something else to give more coverage could be the same MorphOS iso 
that used for pegasos2 which should also boot on sam460ex as shown here:

http://zero.eik.bme.hu/~balaton/qemu/amiga/#morphos

or the AROS iso further up that page that should also boot on sam460ex.

Regards,
BALATON Zoltan

> == mpc8544ds ==
> e500v1, e500v2
>
> == ppce500 ==
> e500mc, e5500, e6500
>
> About the remaining CPUs:
>
> - The 440x4 have been partially removed in the past. I sent a separate
>  patch removing what's left of it.
>
> - The 440x5 (440-xilinx) boots with the bamboo machine but it
>  segfaults in userspace (also in master).
>
> - The e200 is broken in master due to an assert in _spr_register (the
>  DSRR0/1 registers are being registered twice). After fixing that
>  QEMU crashes due to lack of IRQ controller (there's a TODO in the
>  init_proc_e200).
>
> Fabiano Rosas (11):
>  target/ppc: Introduce powerpc_excp_booke
>  target/ppc: Simplify powerpc_excp_booke
>  target/ppc: booke: Critical exception cleanup
>  target/ppc: booke: Machine Check cleanups
>  target/ppc: booke: Data Storage exception cleanup
>  target/ppc: booke: Instruction storage exception cleanup
>  target/ppc: booke: External interrupt cleanup
>  target/ppc: booke: Alignment interrupt cleanup
>  target/ppc: booke: System Call exception cleanup
>  target/ppc: booke: Watchdog Timer interrupt
>  target/ppc: booke: System Reset exception cleanup
>
> target/ppc/excp_helper.c | 228 +++++++++++++++++++++++++++++++++++++++
> 1 file changed, 228 insertions(+)
>
>


  parent reply	other threads:[~2022-01-29  0:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-28 22:40 [PATCH 00/11] target/ppc: powerpc_excp improvements [BookE] (6/n) Fabiano Rosas
2022-01-28 22:40 ` [PATCH 01/11] target/ppc: Introduce powerpc_excp_booke Fabiano Rosas
2022-01-28 22:40 ` [PATCH 02/11] target/ppc: Simplify powerpc_excp_booke Fabiano Rosas
2022-01-28 22:40 ` [PATCH 03/11] target/ppc: booke: Critical exception cleanup Fabiano Rosas
2022-01-28 22:40 ` [PATCH 04/11] target/ppc: booke: Machine Check cleanups Fabiano Rosas
2022-01-28 22:40 ` [PATCH 05/11] target/ppc: booke: Data Storage exception cleanup Fabiano Rosas
2022-01-28 22:40 ` [PATCH 06/11] target/ppc: booke: Instruction storage " Fabiano Rosas
2022-01-28 22:40 ` [PATCH 07/11] target/ppc: booke: External interrupt cleanup Fabiano Rosas
2022-01-28 22:40 ` [PATCH 08/11] target/ppc: booke: Alignment " Fabiano Rosas
2022-01-28 22:40 ` [PATCH 09/11] target/ppc: booke: System Call exception cleanup Fabiano Rosas
2022-01-28 22:40 ` [PATCH 10/11] target/ppc: booke: Watchdog Timer interrupt Fabiano Rosas
2022-01-28 22:40 ` [PATCH 11/11] target/ppc: booke: System Reset exception cleanup Fabiano Rosas
2022-01-29  0:07 ` BALATON Zoltan [this message]
2022-02-01  8:10   ` [PATCH 00/11] target/ppc: powerpc_excp improvements [BookE] (6/n) Cédric Le Goater
2022-02-01 11:32     ` BALATON Zoltan
2022-02-01 12:54       ` Fabiano Rosas
2022-02-09  7:43 ` 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=c9bb63f8-c2e8-31e5-fe24-b9923c2c1821@eik.bme.hu \
    --to=balaton@eik.bme.hu \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=farosas@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.