From: Peter Maydell <peter.maydell@linaro.org>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Yicong Yang <yangyicong@huawei.com>,
imammedo@redhat.com, ani@anisinha.ca, eduardo@habkost.net,
marcel.apfelbaum@gmail.com, f4bug@amsat.org,
wangyanan55@huawei.com, qemu-devel@nongnu.org,
jonathan.cameron@huawei.com, linuxarm@huawei.com,
yangyicong@hisilicon.com, prime.zeng@huawei.com,
hesham.almatary@huawei.com, ionela.voinescu@arm.com,
darren@os.amperecomputing.com
Subject: Re: [PATCH v4 0/6] Only generate cluster node in PPTT when specified
Date: Thu, 10 Nov 2022 13:10:38 +0000 [thread overview]
Message-ID: <CAFEAcA_9eiMiGRPimtLc4UrfTktPO33cbs6gRhR1D+jH8eJ_SA@mail.gmail.com> (raw)
In-Reply-To: <20221102040935-mutt-send-email-mst@kernel.org>
On Wed, 2 Nov 2022 at 08:17, Michael S. Tsirkin <mst@redhat.com> wrote:
>
> On Tue, Nov 01, 2022 at 03:10:42PM +0800, Yicong Yang wrote:
> > From: Yicong Yang <yangyicong@hisilicon.com>
> >
> > This series mainly change the policy for building a cluster topology node
> > in PPTT. Previously we'll always build a cluster node in PPTT without
> > asking the user, after this set the cluster node will be built only the
> > the user specify through "-smp clusters=X".
> >
> > One problem is related to this but not fully caused by this, see the
> > discussion in [*]. When booting the VM with `-smp 8` and 4 numa nodes,
> > the linux scheduling domains in the VM misses the NUMA domains. It's
> > because the MC level span extends to Cluster level (which is generated
> > by the Qemu by default) that spans all the cpus in the system, then the
> > scheduling domain building stops at MC level since it already includes all
> > the cpus.
> >
> > Considering cluster is an optional level and most platforms don't have it,
> > they may even don't realize this is built and a always build policy cannot
> > emulate the real topology on these platforms. So in this series improve the
> > policy to only generate cluster when the user explicitly want it.
> >
> > Update the tests and test tables accordingly.
>
> I think we can classify this as a bugfix and so allow after
> the freeze, however, this needs ack from ARM maintainers then.
I don't use, test or understand any of the ACPI related code :-)
I'm happy to leave it up to your judgement whether this should go
into this release or wait for 8.0.
thanks
-- PMM
next prev parent reply other threads:[~2022-11-10 13:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-01 7:10 [PATCH v4 0/6] Only generate cluster node in PPTT when specified Yicong Yang via
2022-11-01 7:10 ` [PATCH v4 1/6] tests: virt: Allow changes to PPTT test table Yicong Yang via
2022-11-02 7:02 ` wangyanan (Y) via
2022-11-01 7:10 ` [PATCH v4 2/6] hw/acpi/aml-build: Only generate cluster node in PPTT when specified Yicong Yang via
2022-11-02 7:36 ` wangyanan (Y) via
2022-11-01 7:10 ` [PATCH v4 3/6] tests: virt: Update expected ACPI tables for virt test Yicong Yang via
2022-11-02 7:36 ` wangyanan (Y) via
2022-11-01 7:10 ` [PATCH v4 4/6] tests: acpi: Add and whitelist *.topology blobs Yicong Yang via
2022-11-02 7:42 ` wangyanan (Y) via
2022-11-01 7:10 ` [PATCH v4 5/6] tests: acpi: aarch64: Add topology test for aarch64 Yicong Yang via
2022-11-02 7:53 ` wangyanan (Y) via
2022-11-01 7:10 ` [PATCH v4 6/6] tests: acpi: aarch64: Add *.topology tables Yicong Yang via
2022-11-02 8:19 ` wangyanan (Y) via
2022-11-02 8:17 ` [PATCH v4 0/6] Only generate cluster node in PPTT when specified Michael S. Tsirkin
2022-11-03 12:18 ` Yicong Yang via
2022-11-10 13:10 ` Peter Maydell [this message]
2022-12-21 6:27 ` Michael S. Tsirkin
2022-12-21 9:13 ` Yicong Yang via
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=CAFEAcA_9eiMiGRPimtLc4UrfTktPO33cbs6gRhR1D+jH8eJ_SA@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=ani@anisinha.ca \
--cc=darren@os.amperecomputing.com \
--cc=eduardo@habkost.net \
--cc=f4bug@amsat.org \
--cc=hesham.almatary@huawei.com \
--cc=imammedo@redhat.com \
--cc=ionela.voinescu@arm.com \
--cc=jonathan.cameron@huawei.com \
--cc=linuxarm@huawei.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=prime.zeng@huawei.com \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.com \
--cc=yangyicong@hisilicon.com \
--cc=yangyicong@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).