From: David Gibson <david@gibson.dropbear.id.au>
To: Greg Kurz <groug@kaod.org>
Cc: qemu-ppc@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] ppc/pnv: Use the CPU topology to compute the default number of chips
Date: Sat, 21 Dec 2019 11:39:06 +1100 [thread overview]
Message-ID: <20191221003906.GC15511@umbus.fritz.box> (raw)
In-Reply-To: <157686070815.97184.16561911770080665569.stgit@bahia.lan>
[-- Attachment #1: Type: text/plain, Size: 3264 bytes --]
On Fri, Dec 20, 2019 at 05:51:48PM +0100, Greg Kurz wrote:
> Multi TCG mandates the CPU topology to be dimensioned to the actual
> number of CPUs, depending on the number of chips the user asked for.
> That is, '-machine num-chips=N' should always have a '-smp' companion
> with a topology that meats the resulting number of CPUs, typically
> '-smp sockets=N'.
>
> Simplify the command line for these setups by computing the default
> number of chips based on the CPU topology, ie. no need to explicitely
> set "num-chips" anymore. This must be done at machine init because
> smp_parse() is called after instance init.
>
> Signed-off-by: Greg Kurz <groug@kaod.org>
Is there actually any reason to retain num-chips at all? Or could we
just set the number of chips equal to the number of sockets, which
seems to make sense to me.
> ---
> hw/ppc/pnv.c | 23 ++++++++++++++++-------
> 1 file changed, 16 insertions(+), 7 deletions(-)
>
> diff --git a/hw/ppc/pnv.c b/hw/ppc/pnv.c
> index f8cf2b6d760f..9b777b7084a0 100644
> --- a/hw/ppc/pnv.c
> +++ b/hw/ppc/pnv.c
> @@ -768,6 +768,19 @@ static void pnv_init(MachineState *machine)
> exit(1);
> }
>
> + if (!pnv->num_chips) {
> + uint32_t num_chips =
> + machine->smp.max_cpus / (machine->smp.cores * machine->smp.threads);
> + Error *local_err = NULL;
> +
> + object_property_set_uint(OBJECT(pnv), num_chips, "num-chips",
> + &local_err);
> + if (local_err) {
> + error_report_err(local_err);
> + exit(1);
> + }
> + }
> +
> pnv->chips = g_new0(PnvChip *, pnv->num_chips);
> for (i = 0; i < pnv->num_chips; i++) {
> char chip_name[32];
> @@ -1722,6 +1735,9 @@ static void pnv_set_num_chips(Object *obj, Visitor *v, const char *name,
> */
> if (!is_power_of_2(num_chips) || num_chips > 4) {
> error_setg(errp, "invalid number of chips: '%d'", num_chips);
> + error_append_hint(errp,
> + "Set 'num-chips' implicitely with '-smp sockets=N'. "
> + "Valid values are : 1, 2 or 4.\n");
> return;
> }
>
> @@ -1735,12 +1751,6 @@ static void pnv_set_num_chips(Object *obj, Visitor *v, const char *name,
> pnv->num_chips = num_chips;
> }
>
> -static void pnv_machine_instance_init(Object *obj)
> -{
> - PnvMachineState *pnv = PNV_MACHINE(obj);
> - pnv->num_chips = 1;
> -}
> -
> static void pnv_machine_class_props_init(ObjectClass *oc)
> {
> object_class_property_add(oc, "num-chips", "uint32",
> @@ -1874,7 +1884,6 @@ static const TypeInfo types[] = {
> .parent = TYPE_MACHINE,
> .abstract = true,
> .instance_size = sizeof(PnvMachineState),
> - .instance_init = pnv_machine_instance_init,
> .class_init = pnv_machine_class_init,
> .class_size = sizeof(PnvMachineClass),
> .interfaces = (InterfaceInfo[]) {
>
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-12-21 1:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-20 16:51 [PATCH 0/2] ppc/pnv: Improve command line experience with multi-chip Greg Kurz
2019-12-20 16:51 ` [PATCH 1/2] ppc/pnv: Exit gracefully if CPU topology doesn't match the machine capacities Greg Kurz
2019-12-20 16:51 ` [PATCH 2/2] ppc/pnv: Use the CPU topology to compute the default number of chips Greg Kurz
2019-12-21 0:39 ` David Gibson [this message]
2019-12-21 10:28 ` Greg Kurz
2020-01-06 7:25 ` 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=20191221003906.GC15511@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--cc=groug@kaod.org \
--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).