qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Jones <drjones@redhat.com>
To: Gavin Shan <gshan@redhat.com>
Cc: eduardo@habkost.net, peter.maydell@linaro.org, thuth@redhat.com,
	shan.gavin@gmail.com, pbonzini@redhat.com, mst@redhat.com,
	lvivier@redhat.com, armbru@redhat.com,
	richard.henderson@linaro.org, qemu-devel@nongnu.org,
	f4bug@amsat.org, wangyanan55@huawei.com, qemu-arm@nongnu.org,
	Jonathan.Cameron@huawei.com, ani@anisinha.ca,
	Igor Mammedov <imammedo@redhat.com>,
	eblake@redhat.com
Subject: Re: [PATCH v6 2/4] hw/arm/virt: Consider SMP configuration in CPU topology
Date: Thu, 21 Apr 2022 11:02:24 +0200	[thread overview]
Message-ID: <20220421090224.l6i3qcu53seiz5yf@gator> (raw)
In-Reply-To: <7f7ead25-a050-1e86-132a-a3e1e9b1e3b1@redhat.com>

On Wed, Apr 20, 2022 at 10:24:46PM +0800, Gavin Shan wrote:
...
> With amend to the command lines, the following one is used and below error
> is raised from the test. The error is mentioned in the commit log in
> PATCH[v7 2/4].
> 
>     -machine smp.cpus=2                                   \
>     -numa node,nodeid=0,memdev=ram -numa node,nodeid=1    \
>     -numa cpu,node-id=1,thread-id=0                       \
>     -numa cpu,node-id=0,thread-id=1
> 
>     qemu-system-aarch64: -numa cpu,node-id=0,thread-id=1: no match found
>     (reported from hw/core/machine.c::machine_set_cpu_numa_node())
> 
> After the changes to virt_possible_cpu_arch_ids() is applied, "thread-id=1"
> isn't valid any more. The CPU topology becomes like below. Note that
> mc->smp_props.prefer_sockets is true on arm/virt machine.

prefer_sockets is only true for mach-virt 6.1 and older. It's false for
6.2 and later.

Thanks,
drew

> 
>     index    socket   cluster    core    thread
>     --------------------------------------------
>       0        0        0         0        0
>       1        1        0         0        0
> 
> With the amended command lines, the topology changes again so
> that "thread-id=1" is valid:
> 
>     index    socket   cluster    core    thread
>     --------------------------------------------
>       0        0        0         0        0
>       1        0        0         0        1
> 
> It should be ok to split the test/qtest/aarch64_numa_cpu() changes into
> a separate patch and put it before this one. In that case, the specified
> smp.{socket, cluster, core, threads} isn't used by arm/virt machine yet,
> and 'thread-id=2' should be still valid. Lets do this if I need post v8.
> Otherwise, I guess it's also fine to squash the test/qtest/aarch64_numa_cpu()
> changes into PATCH[2/4], as we're doing.
> 
> > 
> > > 
> > > 
> > > > >            "-numa node,nodeid=0,memdev=ram -numa node,nodeid=1 "
> > > > >            "-numa cpu,node-id=1,thread-id=0 "
> > > > >            "-numa cpu,node-id=0,thread-id=1");
> 
> Thanks,
> Gavin
> 



  parent reply	other threads:[~2022-04-21  9:09 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-18  2:09 [PATCH v6 0/4] hw/arm/virt: Fix CPU's default NUMA node ID Gavin Shan
2022-04-18  2:09 ` [PATCH v6 1/4] qapi/machine.json: Add cluster-id Gavin Shan
2022-04-18  2:09 ` [PATCH v6 2/4] hw/arm/virt: Consider SMP configuration in CPU topology Gavin Shan
2022-04-20  8:32   ` Igor Mammedov
2022-04-20 10:31     ` Gavin Shan
2022-04-20 11:50       ` Igor Mammedov
2022-04-20 14:24         ` Gavin Shan
2022-04-20 14:50           ` Igor Mammedov
2022-04-21 11:22             ` Gavin Shan
2022-04-21  9:02           ` Andrew Jones [this message]
2022-04-21 11:28             ` Gavin Shan
2022-04-18  2:09 ` [PATCH v6 3/4] hw/arm/virt: Fix CPU's default NUMA node ID Gavin Shan
2022-04-18  2:09 ` [PATCH v6 4/4] hw/acpi/aml-build: Use existing CPU topology to build PPTT table 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=20220421090224.l6i3qcu53seiz5yf@gator \
    --to=drjones@redhat.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=ani@anisinha.ca \
    --cc=armbru@redhat.com \
    --cc=eblake@redhat.com \
    --cc=eduardo@habkost.net \
    --cc=f4bug@amsat.org \
    --cc=gshan@redhat.com \
    --cc=imammedo@redhat.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=pbonzini@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=thuth@redhat.com \
    --cc=wangyanan55@huawei.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).