From: Gavin Shan <gshan@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
peter.maydell@linaro.org, drjones@redhat.com,
richard.henderson@linaro.org, qemu-devel@nongnu.org,
zhenyzha@redhat.com, wangyanan55@huawei.com, qemu-arm@nongnu.org,
shan.gavin@gmail.com, imammedo@redhat.com
Subject: Re: [PATCH v5 1/4] qapi/machine.json: Add cluster-id
Date: Mon, 4 Apr 2022 18:40:52 +0800 [thread overview]
Message-ID: <896753a5-a40d-74e4-56a8-a46153e3ee26@redhat.com> (raw)
In-Reply-To: <YkqvGsdcnupeTMZR@redhat.com>
Hi Daniel,
On 4/4/22 4:40 PM, Daniel P. Berrangé wrote:
> On Mon, Apr 04, 2022 at 09:37:10AM +0100, Daniel P. Berrangé wrote:
>> On Sun, Apr 03, 2022 at 10:59:50PM +0800, Gavin Shan wrote:
>>> This adds cluster-id in CPU instance properties, which will be used
>>> by arm/virt machine. Besides, the cluster-id is also verified or
>>> dumped in various spots:
>>>
>>> * hw/core/machine.c::machine_set_cpu_numa_node() to associate
>>> CPU with its NUMA node.
>>>
>>> * hw/core/machine.c::machine_numa_finish_cpu_init() to associate
>>> CPU with NUMA node when no default association isn't provided.
>>>
>>> * hw/core/machine-hmp-cmds.c::hmp_hotpluggable_cpus() to dump
>>> cluster-id.
>>>
>>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>>> ---
>>> hw/core/machine-hmp-cmds.c | 4 ++++
>>> hw/core/machine.c | 16 ++++++++++++++++
>>> qapi/machine.json | 6 ++++--
>>> 3 files changed, 24 insertions(+), 2 deletions(-)
>>
>> Missing changes to hw/core/machine-smp.c similar to 'dies' in that
>> file.
>>
>> When 'dies' was added we added a 'dies_supported' flag, so we could
>> reject use of 'dies' when it was not supported - which is everywhere
>> except i386 target.
>>
>> We need the same for 'clusters_supported' machine property since
>> AFAICT only the arm 'virt' machine is getting supported in this
>> series.
>
> Oh, actually I'm mixing up cluster-id and clusters - the latter is
> already supported.
>
Yeah, @clusters_supported has been existing for a while.
Thanks,
Gavin
next prev parent reply other threads:[~2022-04-04 10:43 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 14:59 [PATCH v5 0/4] hw/arm/virt: Fix CPU's default NUMA node ID Gavin Shan
2022-04-03 14:59 ` [PATCH v5 1/4] qapi/machine.json: Add cluster-id Gavin Shan
2022-04-04 8:37 ` Daniel P. Berrangé
2022-04-04 8:40 ` Daniel P. Berrangé
2022-04-04 10:40 ` Gavin Shan [this message]
2022-04-13 11:49 ` wangyanan (Y) via
2022-04-14 0:06 ` Gavin Shan
2022-04-14 2:27 ` wangyanan (Y) via
2022-04-14 7:56 ` Gavin Shan
2022-04-14 9:33 ` wangyanan (Y) via
2022-04-19 15:59 ` Daniel P. Berrangé
2022-04-20 2:17 ` Gavin Shan
2022-04-03 14:59 ` [PATCH v5 2/4] hw/arm/virt: Consider SMP configuration in CPU topology Gavin Shan
2022-04-04 8:39 ` Daniel P. Berrangé
2022-04-04 10:48 ` Gavin Shan
2022-04-04 12:03 ` Igor Mammedov
2022-04-13 12:39 ` wangyanan (Y) via
2022-04-14 0:08 ` Gavin Shan
2022-04-14 2:27 ` wangyanan (Y) via
2022-04-14 2:37 ` Gavin Shan
2022-04-14 2:49 ` wangyanan (Y) via
2022-04-14 7:35 ` Gavin Shan
2022-04-14 9:29 ` wangyanan (Y) via
2022-04-15 6:08 ` Gavin Shan
2022-04-14 9:33 ` Jonathan Cameron via
2022-04-15 6:13 ` Gavin Shan
2022-04-03 14:59 ` [PATCH v5 3/4] hw/arm/virt: Fix CPU's default NUMA node ID Gavin Shan
2022-04-03 14:59 ` [PATCH v5 4/4] hw/acpi/aml-build: Use existing CPU topology to build PPTT table Gavin Shan
2022-04-12 15:40 ` Jonathan Cameron via
2022-04-13 2:15 ` Gavin Shan
2022-04-13 13:52 ` Igor Mammedov
2022-04-14 0:33 ` Gavin Shan
2022-04-14 2:56 ` wangyanan (Y) via
2022-04-14 7:39 ` Gavin Shan
2022-04-19 8:54 ` Igor Mammedov
2022-04-20 5:19 ` Gavin Shan
2022-04-20 8:10 ` Igor Mammedov
2022-04-20 10:22 ` Gavin Shan
2022-04-14 3:09 ` wangyanan (Y) via
2022-04-14 7:45 ` Gavin Shan
2022-04-14 9:22 ` wangyanan (Y) via
2022-04-11 6:48 ` [PATCH v5 0/4] hw/arm/virt: Fix CPU's default NUMA node ID Gavin Shan
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=896753a5-a40d-74e4-56a8-a46153e3ee26@redhat.com \
--to=gshan@redhat.com \
--cc=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=imammedo@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shan.gavin@gmail.com \
--cc=wangyanan55@huawei.com \
--cc=zhenyzha@redhat.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).