qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Cédric Le Goater" <clg@kaod.org>
To: Chalapathi V <chalapathi.v@linux.ibm.com>, qemu-devel@nongnu.org
Cc: qemu-ppc@nongnu.org, fbarrat@linux.ibm.com, npiggin@gmail.com,
	calebs@us.ibm.com, chalapathi.v@ibm.com,
	saif.abrar@linux.vnet.ibm.com
Subject: Re: [PATCH v6 0/3] pnv nest1 chiplet model
Date: Tue, 28 Nov 2023 18:38:10 +0100	[thread overview]
Message-ID: <ed3e5f71-620c-48e7-a8c7-d083be78c192@kaod.org> (raw)
In-Reply-To: <20231127171307.5237-1-chalapathi.v@linux.ibm.com>

On 11/27/23 18:13, Chalapathi V wrote:
> Hello,
> 
> Thank you for the review and suggestions on V5.
> 
> The suggestions and changes requested from V5 are addressed in V6.
> 
> Updates in Version 6 of this series are:
> 1. adding a device-tree node in QEMU is removed as skiboot defines the
>     device-tree and QEMU should just follow it.
> 2. Renamed PnvPerv to PnvNestChipletPervasive in PATCH1 as the model provides
>     the common pervasive registers of all nest chiplets.
> 3. Nest1_chiplet model in PATCH2 is renamed to N1_chiplet to avoid the
>     confussions that may comeup later.
> 
> Hence the new qom-tree looks like below.
> (qemu) info qom-tree
> /machine (powernv10-machine)
>    /chip[0] (power10_v2.0-pnv-chip)
>      /n1_chiplet (pnv-N1-chiplet)
>        /nest_pervasive_common (pnv-nest-chiplet-pervasive)
>          /xscom-n1_chiplet-control-regs[0] (memory-region)
>        /xscom-n1_chiplet-pb-scom-eq-regs[0] (memory-region)
>        /xscom-n1_chiplet-pb-scom-es-regs[0] (memory-region)
> 
> Patches overview in V6.
> PATCH1: Create a common nest pervasive chiplet model with control chiplet scom
>          registers.
> PATCH2: Create a N1 chiplet model and implement powerbus scom registers.
>          Connect common nest pervasive model to N1 chiplet model to define
>          chiplet control scoms for N1 chiplet.
> PATCH3: Connect N1 chiplet model to p10 chip.
> 
> Test covered:
> These changes are tested on a single socket and 2 socket P10 machine.


It would be nice to add in tests/avocado/ppc_powernv.py a simple test case
for a 2 socket machine :

         self.vm.add_args('-smp', '8,sockets=2,cores=1,threads=4')
	...
	console_pattern = 'smp: Brought up 2 nodes, 8 CPUs'

Thanks,

C.



  parent reply	other threads:[~2023-11-28 17:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-27 17:13 [PATCH v6 0/3] pnv nest1 chiplet model Chalapathi V
2023-11-27 17:13 ` [PATCH v6 1/3] hw/ppc: Add pnv nest pervasive common " Chalapathi V
2023-11-28  2:04   ` Nicholas Piggin
2023-11-28 14:24   ` Cédric Le Goater
2023-11-27 17:13 ` [PATCH v6 2/3] hw/ppc: Add N1 " Chalapathi V
2023-11-28  2:05   ` Nicholas Piggin
2023-11-28  6:48   ` Cédric Le Goater
2023-12-06 10:01     ` Chalapathi V
2023-11-27 17:13 ` [PATCH v6 3/3] hw/ppc: N1 chiplet wiring Chalapathi V
2023-11-28  2:09   ` Nicholas Piggin
2023-11-28 17:38 ` Cédric Le Goater [this message]
2023-11-28 21:37   ` [PATCH v6 0/3] pnv nest1 chiplet model 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=ed3e5f71-620c-48e7-a8c7-d083be78c192@kaod.org \
    --to=clg@kaod.org \
    --cc=calebs@us.ibm.com \
    --cc=chalapathi.v@ibm.com \
    --cc=chalapathi.v@linux.ibm.com \
    --cc=fbarrat@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=saif.abrar@linux.vnet.ibm.com \
    /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).