From: "Cédric Le Goater" <clg@kaod.org>
To: Greg Kurz <groug@kaod.org>, David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, qemu-devel@nongnu.org
Subject: Re: [PATCH 2/2] ppc/pnv: Use the CPU topology to compute the default number of chips
Date: Mon, 6 Jan 2020 08:25:40 +0100 [thread overview]
Message-ID: <2db93f13-2fa2-a569-d706-c92bc8adc06d@kaod.org> (raw)
In-Reply-To: <20191221112849.68769d69@bahia.lan>
On 12/21/19 11:28 AM, Greg Kurz wrote:
> On Sat, 21 Dec 2019 11:39:06 +1100
> David Gibson <david@gibson.dropbear.id.au> wrote:
>
>> 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.
>>
>
> I don't quite know why "num-chips" was introduced in the first place... so
> yes, if it turns out it isn't needed, I'll gladly drop the property.
I concur. We have some freedom on the PowerNV machine options.
Let's replace "num-chips" with "sockets".
Thanks,
C.
prev parent reply other threads:[~2020-01-06 7:26 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
2019-12-21 10:28 ` Greg Kurz
2020-01-06 7:25 ` Cédric Le Goater [this message]
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=2db93f13-2fa2-a569-d706-c92bc8adc06d@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--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).