All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabiano Rosas <farosas@linux.ibm.com>
To: "Cédric Le Goater" <clg@kaod.org>, qemu-devel@nongnu.org
Cc: danielhb413@gmail.com, qemu-ppc@nongnu.org, david@gibson.dropbear.id.au
Subject: Re: [PATCH 00/11] target/ppc: powerpc_excp improvements [6xx] (7/n)
Date: Fri, 04 Feb 2022 12:50:52 -0300	[thread overview]
Message-ID: <87r18i8wbn.fsf@linux.ibm.com> (raw)
In-Reply-To: <f8a83c3d-be90-30bc-5cdf-752fe3d1b04c@kaod.org>

Cédric Le Goater <clg@kaod.org> writes:

> On 2/3/22 21:09, Fabiano Rosas wrote:
>
>> This series handles the 6xx family: 603, 604, G2, G2LE, 
>
> What about the e300 ? I guess it's only a 603 variant for QEMU.

I forgot to mention.

>> MPC5xx and MPC8xx.
>
> These are linux-user only, no MMU. I wonder if we shouldn't simply
> drop support. At least we could remove POWERPC_MMU_MPC8xx.

I know nothing about linux-user use cases, sorry. We have other CPUs
that are linux-user only, though. And there's this TODO_USER_ONLY mess
in cpu-models as well. We could probably tackle all of it at once.


  reply	other threads:[~2022-02-04 15:59 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-03 20:09 [PATCH 00/11] target/ppc: powerpc_excp improvements [6xx] (7/n) Fabiano Rosas
2022-02-03 20:09 ` [PATCH 01/11] target/ppc: Merge exception model IDs for 6xx CPUs Fabiano Rosas
2022-02-03 20:09 ` [PATCH 02/11] target/ppc: Introduce powerpc_excp_6xx Fabiano Rosas
2022-02-03 20:09 ` [PATCH 03/11] target/ppc: Simplify powerpc_excp_6xx Fabiano Rosas
2022-02-03 20:09 ` [PATCH 04/11] target/ppc: 6xx: Critical exception cleanup Fabiano Rosas
2022-02-04 12:43   ` BALATON Zoltan
2022-02-04 15:42     ` Fabiano Rosas
2022-02-03 20:09 ` [PATCH 05/11] target/ppc: 6xx: Machine Check " Fabiano Rosas
2022-02-03 20:09 ` [PATCH 06/11] target/ppc: 6xx: External interrupt cleanup Fabiano Rosas
2022-02-03 20:09 ` [PATCH 07/11] target/ppc: 6xx: Program exception cleanup Fabiano Rosas
2022-02-03 20:09 ` [PATCH 08/11] target/ppc: 6xx: System Call " Fabiano Rosas
2022-02-03 20:09 ` [PATCH 09/11] target/ppc: 6xx: System Reset interrupt cleanup Fabiano Rosas
2022-02-03 20:09 ` [PATCH 10/11] target/ppc: 6xx: Software TLB exceptions cleanup Fabiano Rosas
2022-02-04 12:51   ` BALATON Zoltan
2022-02-04 15:46     ` Fabiano Rosas
2022-02-04 16:36       ` BALATON Zoltan
2022-02-03 20:09 ` [PATCH 11/11] target/ppc: 6xx: Set SRRs directly in exception code Fabiano Rosas
2022-02-04  6:42 ` [PATCH 00/11] target/ppc: powerpc_excp improvements [6xx] (7/n) Cédric Le Goater
2022-02-04 15:50   ` Fabiano Rosas [this message]
2022-02-09  7:44 ` 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=87r18i8wbn.fsf@linux.ibm.com \
    --to=farosas@linux.ibm.com \
    --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 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.