From: Igor Mammedov <imammedo@redhat.com>
To: Gavin Shan <gshan@redhat.com>
Cc: peter.maydell@linaro.org, drjones@redhat.com,
"Daniel P. Berrangé" <berrange@redhat.com>,
richard.henderson@linaro.org, qemu-devel@nongnu.org,
zhenyzha@redhat.com, wangyanan55@huawei.com, qemu-arm@nongnu.org,
shan.gavin@gmail.com
Subject: Re: [PATCH v5 2/4] hw/arm/virt: Consider SMP configuration in CPU topology
Date: Mon, 4 Apr 2022 14:03:18 +0200 [thread overview]
Message-ID: <20220404140318.5afd6c58@redhat.com> (raw)
In-Reply-To: <17bd5453-ef36-6bbc-3913-d806e0ed7a38@redhat.com>
On Mon, 4 Apr 2022 18:48:00 +0800
Gavin Shan <gshan@redhat.com> wrote:
> Hi Daniel,
>
> On 4/4/22 4:39 PM, Daniel P. Berrangé wrote:
> > On Sun, Apr 03, 2022 at 10:59:51PM +0800, Gavin Shan wrote:
> >> Currently, the SMP configuration isn't considered when the CPU
> >> topology is populated. In this case, it's impossible to provide
> >> the default CPU-to-NUMA mapping or association based on the socket
> >> ID of the given CPU.
> >>
> >> This takes account of SMP configuration when the CPU topology
> >> is populated. The die ID for the given CPU isn't assigned since
> >> it's not supported on arm/virt machine yet.
> >>
> >> Signed-off-by: Gavin Shan <gshan@redhat.com>
> >> ---
> >> hw/arm/virt.c | 16 +++++++++++++++-
> >> 1 file changed, 15 insertions(+), 1 deletion(-)
> >>
> >> diff --git a/hw/arm/virt.c b/hw/arm/virt.c
> >> index d2e5ecd234..3174526730 100644
> >> --- a/hw/arm/virt.c
> >> +++ b/hw/arm/virt.c
> >> @@ -2505,6 +2505,7 @@ static const CPUArchIdList *virt_possible_cpu_arch_ids(MachineState *ms)
> >> int n;
> >> unsigned int max_cpus = ms->smp.max_cpus;
> >> VirtMachineState *vms = VIRT_MACHINE(ms);
> >> + MachineClass *mc = MACHINE_GET_CLASS(vms);
> >>
> >> if (ms->possible_cpus) {
> >> assert(ms->possible_cpus->len == max_cpus);
> >> @@ -2518,8 +2519,21 @@ static const CPUArchIdList *virt_possible_cpu_arch_ids(MachineState *ms)
> >> ms->possible_cpus->cpus[n].type = ms->cpu_type;
> >> ms->possible_cpus->cpus[n].arch_id =
> >> virt_cpu_mp_affinity(vms, n);
> >> +
> >> + assert(!mc->smp_props.dies_supported);
> >> + ms->possible_cpus->cpus[n].props.has_socket_id = true;
> >> + ms->possible_cpus->cpus[n].props.socket_id =
> >> + (n / (ms->smp.clusters * ms->smp.cores * ms->smp.threads)) %
> >> + ms->smp.sockets;
> >> + ms->possible_cpus->cpus[n].props.has_cluster_id = true;
> >> + ms->possible_cpus->cpus[n].props.cluster_id =
> >> + (n / (ms->smp.cores * ms->smp.threads)) % ms->smp.clusters;
> >> + ms->possible_cpus->cpus[n].props.has_core_id = true;
> >> + ms->possible_cpus->cpus[n].props.core_id =
> >> + (n / ms->smp.threads) % ms->smp.cores;
> >> ms->possible_cpus->cpus[n].props.has_thread_id = true;
> >> - ms->possible_cpus->cpus[n].props.thread_id = n;
> >> + ms->possible_cpus->cpus[n].props.thread_id =
> >> + n % ms->smp.threads;
> >
> > Does this need to be conditionalized d behind a machine property, so that
> > we don't change behaviour of existing machine type versions ?
> >
>
> I think we probably needn't to do that because the default NUMA node
> for the given CPU is returned based on the socket ID in next patch.
> The socket ID is calculated in this patch. Otherwise, we will see
> CPU topology broken warnings in Linux guest. I think we need to fix
> this issue for all machine type versions.
Agreed.
Also guest-wise it's ACPI only change, which is 'firmware' part of QEMU,
and by default we don't to version those changes unless we a pressed
into it (i.e the same policy that goes for bundled firmware)
> Thanks,
> Gavin
>
next prev parent reply other threads:[~2022-04-04 12:04 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
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 [this message]
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=20220404140318.5afd6c58@redhat.com \
--to=imammedo@redhat.com \
--cc=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=gshan@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).