From: Yanan Wang <wangyanan55@huawei.com>
To: <qemu-devel@nongnu.org>
Cc: "Andrew Jones" <drjones@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Eduardo Habkost" <ehabkost@redhat.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
wanghaibin.wang@huawei.com, "Yanan Wang" <wangyanan55@huawei.com>,
"Igor Mammedov" <imammedo@redhat.com>,
yuzenghui@huawei.com, "Paolo Bonzini" <pbonzini@redhat.com>
Subject: [RFC PATCH 0/6] machine: smp parsing fixes and improvement
Date: Fri, 2 Jul 2021 18:07:33 +0800 [thread overview]
Message-ID: <20210702100739.13672-1-wangyanan55@huawei.com> (raw)
Hello,
Here are some smp parsing fix and improvement, most of which is about
the smp parsing helpers. This series was arranged based on the latest
QEMU code since commit d940d468e29b.
Description:
Patch #1 improves the calculation of maxcpus.
Patch #2 and #3 adds the missing zero-check for values of sockets and dies.
Patch #4 allows us to uniformly use maxcpus for all calculations.
Patch #5 reject the configuration of dies more strictly for non-PC machines.
Patch #6 makes no functional change but tweaks the order of topology parameters.
Regards,
Yanan
Yanan Wang (6):
machine: Set the value of maxcpus to match cpus if specified as zero
machine: Perform zero-check for the computed value of sockets
pc/machine: Perform zero-check for the value of -smp dies
machine: Uniformly use maxcpus to calculate the missing values
pc/machine: Disallow any configuration of dies for non-PC machines
machine: Tweak the order of topology members in struct CpuTopology
hw/core/machine.c | 49 +++++++++++++++++++++++++--------------------
hw/i386/pc.c | 48 +++++++++++++++++++++++++-------------------
include/hw/boards.h | 7 ++++---
qapi/machine.json | 2 +-
4 files changed, 59 insertions(+), 47 deletions(-)
--
2.19.1
next reply other threads:[~2021-07-02 10:09 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-02 10:07 Yanan Wang [this message]
2021-07-02 10:07 ` [RFC PATCH 1/6] machine: Set the value of maxcpus to match cpus if specified as zero Yanan Wang
2021-07-12 14:57 ` Andrew Jones
2021-07-12 15:27 ` Daniel P. Berrangé
2021-07-02 10:07 ` [RFC PATCH 2/6] machine: Perform zero-check for the computed value of sockets Yanan Wang
2021-07-12 15:00 ` Andrew Jones
2021-07-12 15:30 ` Daniel P. Berrangé
2021-07-13 6:56 ` wangyanan (Y)
2021-07-02 10:07 ` [RFC PATCH 3/6] pc/machine: Perform zero-check for the value of -smp dies Yanan Wang
2021-07-12 15:04 ` Andrew Jones
2021-07-12 15:05 ` Andrew Jones
2021-07-12 15:27 ` Andrew Jones
2021-07-13 6:46 ` wangyanan (Y)
2021-07-02 10:07 ` [RFC PATCH 4/6] machine: Uniformly use maxcpus to calculate the missing values Yanan Wang
2021-07-12 15:25 ` Andrew Jones
2021-07-13 7:25 ` wangyanan (Y)
2021-07-13 7:49 ` wangyanan (Y)
2021-07-02 10:07 ` [RFC PATCH 5/6] pc/machine: Disallow any configuration of dies for non-PC machines Yanan Wang
2021-07-02 10:18 ` Daniel P. Berrangé
2021-07-05 9:03 ` wangyanan (Y)
2021-07-02 10:07 ` [RFC PATCH 6/6] machine: Tweak the order of topology members in struct CpuTopology Yanan Wang
2021-07-12 15:29 ` Andrew Jones
2021-07-12 19:46 ` Pankaj Gupta
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=20210702100739.13672-1-wangyanan55@huawei.com \
--to=wangyanan55@huawei.com \
--cc=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=wanghaibin.wang@huawei.com \
--cc=yuzenghui@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.