From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "wangyanan (Y)" <wangyanan55@huawei.com>
Cc: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, qemu-trivial@nongnu.org,
wanghaibin.wang@huawei.com, "Andrew Jones" <drjones@redhat.com>,
"Laurent Vivier" <laurent@vivier.eu>
Subject: Re: [PATCH 2/2] qemu-options: Add missing "sockets=2" to CLI "-smp 2"
Date: Tue, 28 Sep 2021 12:01:56 +0100 [thread overview]
Message-ID: <YVL2JDoQ2XNvmo+H@redhat.com> (raw)
In-Reply-To: <0508934a-f4d5-a7ed-310a-065aa823fb08@huawei.com>
On Tue, Sep 28, 2021 at 06:58:20PM +0800, wangyanan (Y) wrote:
>
> On 2021/9/28 18:46, Philippe Mathieu-Daudé wrote:
> > On 9/28/21 11:31, Yanan Wang wrote:
> > > There is one example of -smp CLI in qemu-options.hx currently
> > > using "-smp 2" and assuming that there will be 2 sockets.
> > > However now the actually calculation logic of missing sockets
> > > and cores is not immutable, we should use more explicit CLIs
> > > like "-smp 2,sockets=2" if we want multiple sockets.
> > >
> > > Signed-off-by: Yanan Wang <wangyanan55@huawei.com>
> > > ---
> > > qemu-options.hx | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/qemu-options.hx b/qemu-options.hx
> > > index dcd9595650..ff8917c5e1 100644
> > > --- a/qemu-options.hx
> > > +++ b/qemu-options.hx
> > > @@ -395,7 +395,7 @@ SRST
> > > -m 2G \
> > > -object memory-backend-ram,size=1G,id=m0 \
> > > -object memory-backend-ram,size=1G,id=m1 \
> > > - -smp 2 \
> > > + -smp 2,sockets=2,maxcpus=2 \
> > Is the addition of "maxcpus=2" intentional?
> Yes, but it's not necessary IMO. I just wanted to keep consistency
> with other numa config examples in the Doc. Should I remove it ?
I think it makes sense to be explicit, because the numa config
works in terms of maxcpus when splitting cpus between nodes
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
WARNING: multiple messages have this Message-ID (diff)
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "wangyanan (Y)" <wangyanan55@huawei.com>
Cc: "Andrew Jones" <drjones@redhat.com>,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
"Laurent Vivier" <laurent@vivier.eu>,
wanghaibin.wang@huawei.com,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH 2/2] qemu-options: Add missing "sockets=2" to CLI "-smp 2"
Date: Tue, 28 Sep 2021 12:01:56 +0100 [thread overview]
Message-ID: <YVL2JDoQ2XNvmo+H@redhat.com> (raw)
In-Reply-To: <0508934a-f4d5-a7ed-310a-065aa823fb08@huawei.com>
On Tue, Sep 28, 2021 at 06:58:20PM +0800, wangyanan (Y) wrote:
>
> On 2021/9/28 18:46, Philippe Mathieu-Daudé wrote:
> > On 9/28/21 11:31, Yanan Wang wrote:
> > > There is one example of -smp CLI in qemu-options.hx currently
> > > using "-smp 2" and assuming that there will be 2 sockets.
> > > However now the actually calculation logic of missing sockets
> > > and cores is not immutable, we should use more explicit CLIs
> > > like "-smp 2,sockets=2" if we want multiple sockets.
> > >
> > > Signed-off-by: Yanan Wang <wangyanan55@huawei.com>
> > > ---
> > > qemu-options.hx | 2 +-
> > > 1 file changed, 1 insertion(+), 1 deletion(-)
> > >
> > > diff --git a/qemu-options.hx b/qemu-options.hx
> > > index dcd9595650..ff8917c5e1 100644
> > > --- a/qemu-options.hx
> > > +++ b/qemu-options.hx
> > > @@ -395,7 +395,7 @@ SRST
> > > -m 2G \
> > > -object memory-backend-ram,size=1G,id=m0 \
> > > -object memory-backend-ram,size=1G,id=m1 \
> > > - -smp 2 \
> > > + -smp 2,sockets=2,maxcpus=2 \
> > Is the addition of "maxcpus=2" intentional?
> Yes, but it's not necessary IMO. I just wanted to keep consistency
> with other numa config examples in the Doc. Should I remove it ?
I think it makes sense to be explicit, because the numa config
works in terms of maxcpus when splitting cpus between nodes
Regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2021-09-28 11:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 9:31 [PATCH 0/2] qemu-options: Trivial doc fixes related to -smp Yanan Wang
2021-09-28 9:31 ` Yanan Wang
2021-09-28 9:31 ` [PATCH 1/2] qemu-options: Tweak [, maxcpus=cpus] to [, maxcpus=maxcpus] Yanan Wang
2021-09-28 9:31 ` Yanan Wang
2021-09-28 10:40 ` Damien Hedde
2021-09-28 9:31 ` [PATCH 2/2] qemu-options: Add missing "sockets=2" to CLI "-smp 2" Yanan Wang
2021-09-28 9:31 ` Yanan Wang
2021-09-28 10:46 ` Philippe Mathieu-Daudé
2021-09-28 10:58 ` wangyanan (Y)
2021-09-28 11:01 ` Daniel P. Berrangé [this message]
2021-09-28 11:01 ` Daniel P. Berrangé
2021-09-28 11:42 ` wangyanan (Y)
2021-09-28 11:42 ` wangyanan (Y)
2021-09-28 11:49 ` Philippe Mathieu-Daudé
2021-09-28 11:49 ` Philippe Mathieu-Daudé
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=YVL2JDoQ2XNvmo+H@redhat.com \
--to=berrange@redhat.com \
--cc=drjones@redhat.com \
--cc=laurent@vivier.eu \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=wanghaibin.wang@huawei.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 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.