qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Daniel Henrique Barboza" <danielhb413@gmail.com>,
	"Cédric Le Goater" <clg@kaod.org>,
	qemu-devel@nongnu.org
Cc: <qemu-ppc@nongnu.org>, "Harsh Prateek Bora" <harshpb@linux.ibm.com>
Subject: Re: [PATCH 0/2] target/ppc: Easy parts of the POWER chiptod series
Date: Sat, 01 Jul 2023 18:38:21 +1000	[thread overview]
Message-ID: <CTQP7BKWD8W3.MP8NCILJUWDQ@wheely> (raw)
In-Reply-To: <9989efc7-5ad9-0c31-e0af-b8a735dce353@gmail.com>

On Sat Jul 1, 2023 at 5:38 AM AEST, Daniel Henrique Barboza wrote:
>
>
> On 6/29/23 01:58, Cédric Le Goater wrote:
> > On 6/25/23 14:03, Nicholas Piggin wrote:
> >> Cedric kindly reviewed these already so I think they should be
> >> good to go now. This is just a rebase and slight rewording the
> >> changelog. Still haven't completed the main chiptod device yet.
> >>
> >> Thanks,
> >> Nick
> >>
> >> Nicholas Piggin (2):
> >>    target/ppc: Tidy POWER book4 SPR registration
> >>    target/ppc: Add TFMR SPR implementation with read and write helpers
> >>
> >>   target/ppc/cpu_init.c        | 82 ++++++++++++++++++++++++------------
> >>   target/ppc/helper.h          |  2 +
> >>   target/ppc/spr_common.h      |  2 +
> >>   target/ppc/timebase_helper.c | 13 ++++++
> >>   target/ppc/translate.c       | 10 +++++
> >>   5 files changed, 82 insertions(+), 27 deletions(-)
> >>
> > 
> > 
> > Daniel,
> > 
> > When you start building the next PPC PR, I think you can also take
> > this patch :
> > 
> >    [4/4] target/ppc: Implement core timebase state machine and TFMR
> >    https://patchwork.ozlabs.org/project/qemu-ppc/patch/20230603233612.125879-5-npiggin@gmail.com/
> > 
> > It belongs to the same series.
>
> That doesn't apply cleanly with these 2 patches and it didn't look trivial to
> me. As if there were some code missing.

Yeah, it actually uses some signals from the nest chiptod patch.

> If Nick re-send it rebased on top of ppc-next I can queue it. Since it's a
> rebase you can keep the r-b. Thanks,

I'll see how it goes, it may have to wait for next merge. SMT for
powernv is a little more important since it's more user-facing and it
would be nice to introduce SMT for both pseries and powernv together.

Chiptod for doesn't really do much except step through skiboot init
code, and getting more useful things wired up like TB fault / HMI
injection won't be ready before freeze.

Thanks,
Nick


  reply	other threads:[~2023-07-01  8:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-25 12:03 [PATCH 0/2] target/ppc: Easy parts of the POWER chiptod series Nicholas Piggin
2023-06-25 12:03 ` [PATCH 1/2] target/ppc: Tidy POWER book4 SPR registration Nicholas Piggin
2023-06-30 19:36   ` Daniel Henrique Barboza
2023-06-25 12:03 ` [PATCH 2/2] target/ppc: Add TFMR SPR implementation with read and write helpers Nicholas Piggin
2023-06-30 19:36   ` Daniel Henrique Barboza
2023-06-29  4:58 ` [PATCH 0/2] target/ppc: Easy parts of the POWER chiptod series Cédric Le Goater
2023-06-30 19:38   ` Daniel Henrique Barboza
2023-07-01  8:38     ` Nicholas Piggin [this message]
2023-07-01  9:03       ` 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=CTQP7BKWD8W3.MP8NCILJUWDQ@wheely \
    --to=npiggin@gmail.com \
    --cc=clg@kaod.org \
    --cc=danielhb413@gmail.com \
    --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 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).