qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Aditya Gupta <adityag@linux.ibm.com>
Cc: qemu-devel@nongnu.org, Mahesh J Salgaonkar <mahesh@linux.ibm.com>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Nicholas Piggin <npiggin@gmail.com>
Subject: Re: [PATCH 0/2] P11 support for QEMU
Date: Tue, 2 Apr 2024 08:56:02 +0200	[thread overview]
Message-ID: <c8a82773-04ff-44d4-9a75-1e1f9b4efa10@kaod.org> (raw)
In-Reply-To: <7dpmvbcarr2lbbjih3n6d6kaj23dzrmtowqme4lnyhbjeexffw@u3agsb3prq7b>

Hello Aditya,

On 4/2/24 08:39, Aditya Gupta wrote:
> Hello Cédric,
> 
> Thanks for reviewing this.
> 
> On Mon, Apr 01, 2024 at 10:25:31AM +0200, Cédric Le Goater wrote:
>> Hello Aditya,
>>
>> Please run ./scripts/get_maintainer.pl when sending a series. qemu-ppc should be
>> in Cc:
> 
> Tried it now, For some reason, get_maintainer.pl shows no maintainers:
> 
>      $ ./scripts/get_maintainer.pl -f 0002-ppc-powernv11-add-base-support-for-P11-PowerNV.patch
>      get_maintainer.pl: No maintainers found, printing recent contributors.
>      get_maintainer.pl: Do not blindly cc: them on patches!  Use common sense.
>      
>      qemu-devel@nongnu.org (open list:All patches CC here)

Weird. I downloaded your series with b4 and ran the get_maintainer.pl script :

$ ./scripts/get_maintainer.pl 20240401_adityag_p11_support_for_qemu.patches/0001_ppc_pseries_add_p11_cpu_type.patch 20240401_adityag_p11_support_for_qemu.patches/0002_ppc_powernv11_add_base_support_for_p11_powernv.patch

Nicholas Piggin <npiggin@gmail.com> (odd fixer:sPAPR (pseries))
Daniel Henrique Barboza <danielhb413@gmail.com> (reviewer:sPAPR (pseries))
David Gibson <david@gibson.dropbear.id.au> (reviewer:sPAPR (pseries))
Harsh Prateek Bora <harshpb@linux.ibm.com> (reviewer:sPAPR (pseries))
"Cédric Le Goater" <clg@kaod.org> (odd fixer:PowerNV Non-Virt...)
"Frédéric Barrat" <fbarrat@linux.ibm.com> (reviewer:PowerNV Non-Virt...)
qemu-ppc@nongnu.org (open list:sPAPR (pseries))
qemu-devel@nongnu.org (open list:All patches CC here)

  
> I checked the MAINTAINERS file, will add maintainers in Cc, thanks.
> 
>>
>> Briefly looking at this, please separate the changes using one patch per model,
>> that is : first CPU (target), LPC, OCC, PSI, SBE, PnvCore, SpaprCore. Last the
>> PnvChip and the machines, powernv11 and pseries. A minimum commit log describing
>> the HW is required.
> 
> Sure, I will split the changes and improve my commit descriptions.
> 
>> I don't see PHB6 or XIVE3. Why ?
> 
> Power11 core is same as Power10, so it supports till PHB5 and XIVE2,
> same as P10. That's why I have not added any code for them.

ok. That's typically the info the commit log should have.

>> Also, you will need an OPAL update. The above changes are pointless without it.
>> The minimum for now is a git commit from the opal repo, then you will need to
>> update QEMU with a binary.
> 
> Agreed. I will consult when we push it to public. Will update this in
> next series.
> 
> There might be some days delay in the next patch series.

We have entered the QEMU 9.1 cycle. There is time. I will comment more
the next respin.

Thanks,

C.



  reply	other threads:[~2024-04-02  6:56 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-01  5:55 [PATCH 0/2] P11 support for QEMU Aditya Gupta
2024-04-01  5:55 ` [PATCH 1/2] ppc: pseries: add P11 cpu type Aditya Gupta
2024-04-01  5:55 ` [PATCH 2/2] ppc: powernv11: add base support for P11 PowerNV Aditya Gupta
2024-04-01  8:25 ` [PATCH 0/2] P11 support for QEMU Cédric Le Goater
2024-04-02  6:39   ` Aditya Gupta
2024-04-02  6:56     ` Cédric Le Goater [this message]
2024-04-02  7:00       ` Aditya Gupta
2024-04-02  8:43         ` Cédric Le Goater
2024-04-03  4:26 ` 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=c8a82773-04ff-44d4-9a75-1e1f9b4efa10@kaod.org \
    --to=clg@kaod.org \
    --cc=adityag@linux.ibm.com \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@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).