qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Bharata B Rao <bharata@linux.vnet.ibm.com>
To: Thomas Huth <thuth@redhat.com>
Cc: mdroth@linux.vnet.ibm.com, aik@ozlabs.ru, agraf@suse.de,
	qemu-devel@nongnu.org, qemu-ppc@nongnu.org,
	tyreld@linux.vnet.ibm.com, imammedo@redhat.com,
	nfont@linux.vnet.ibm.com, afaerber@suse.de,
	David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [RFC PATCH v4 09/11] spapr: Support topologies with unfilled cores
Date: Wed, 9 Sep 2015 12:28:02 +0530	[thread overview]
Message-ID: <20150909065802.GH17433@in.ibm.com> (raw)
In-Reply-To: <55E95A09.8030700@redhat.com>

On Fri, Sep 04, 2015 at 10:44:57AM +0200, Thomas Huth wrote:
> On 04/09/15 09:01, David Gibson wrote:
> > On Thu, Aug 06, 2015 at 10:57:15AM +0530, Bharata B Rao wrote:
> >> QEMU currently supports CPU topologies where there can be cores
> >> which are not completely filled with all the threads as per the
> >> specifed SMT mode.
> >>
> >> Restore support for such topologies (Eg -smp 15,cores=4,threads=4)
> >> The last core will always have the deficit even when -device options are
> >> used to cold-plug the cores.
> >>
> >> Signed-off-by: Bharata B Rao <bharata@linux.vnet.ibm.com>
> > 
> > Is there a reason to support these silly toplogies, or should we just
> > error out if this is specified?

Only reason was to ensure that existing guest with such topologies
continue to boot like before.

> 
> FYI, I've recently submitted a patch that tries to catch such illegal
> SMP configurations and simply errors out in that case:
> 
> http://lists.nongnu.org/archive/html/qemu-devel/2015-07/msg04549.html
> 
> It's not upstream yet, but already in Eduardo's x86 branch. I think this
> will reject the bad topology from your example, too.

It does reject -smp 15,cores=4,threads=4, but with

-smp 15,cores=4,threads=4,maxcpus=16, the guest still boots with weird
topology.

[root@localhost ~]# lscpu
Architecture:          ppc64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Big Endian
CPU(s):                16
On-line CPU(s) list:   0-14
Off-line CPU(s) list:  15
Thread(s) per core:    3
Core(s) per socket:    1
Socket(s):             4
NUMA node(s):          1
Model:                 IBM pSeries (emulated by qemu)
L1d cache:             64K
L1i cache:             32K
NUMA node0 CPU(s):     0-14

[root@localhost ~]# ppc64_cpu --info
Core   0:    0*    1*    2*    3* 
Core   1:    4*    5*    6*    7* 
Core   2:    8*    9*   10*   11* 
Core   3:   12*   13*   14*   15

Should such topologies also be prevented from booting ?

Regards,
Bharata.

  reply	other threads:[~2015-09-09  6:58 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-06  5:27 [Qemu-devel] [RFC PATCH v4 00/11] sPAPR CPU hotplug Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 01/11] exec: Remove cpu from cpus list during cpu_exec_exit() Bharata B Rao
2015-09-04  5:31   ` David Gibson
2015-09-09  5:52     ` Bharata B Rao
2015-09-09  7:41       ` Zhu Guihua
2015-09-09  7:56         ` Bharata B Rao
2015-11-12  9:11           ` Zhu Guihua
2015-11-12  9:30             ` Bharata B Rao
2015-11-12  9:41               ` Zhu Guihua
2015-11-12  9:56               ` Andreas Färber
2015-11-12 11:40                 ` Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 02/11] exec: Do vmstate unregistration from cpu_exec_exit() Bharata B Rao
2015-09-04  6:03   ` David Gibson
2015-09-09  5:56     ` Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 03/11] cpus: Reclaim vCPU objects Bharata B Rao
2015-09-04  6:09   ` David Gibson
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 04/11] cpus: Add a sync version of cpu_remove() Bharata B Rao
2015-09-04  6:11   ` David Gibson
2015-09-09  5:57     ` Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 05/11] xics_kvm: Add cpu_destroy method to XICS Bharata B Rao
2015-08-07 11:33   ` Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 06/11] spapr: Create pseries-2.5 machine Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 07/11] spapr: Enable CPU hotplug for pseries-2.5 and add CPU DRC DT entries Bharata B Rao
2015-09-04  6:28   ` David Gibson
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 08/11] spapr: CPU hotplug support Bharata B Rao
2015-09-04  6:58   ` David Gibson
2015-09-09  6:52     ` Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 09/11] spapr: Support topologies with unfilled cores Bharata B Rao
2015-09-04  7:01   ` David Gibson
2015-09-04  8:44     ` Thomas Huth
2015-09-09  6:58       ` Bharata B Rao [this message]
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 10/11] spapr: CPU hot unplug support Bharata B Rao
2015-08-06  5:27 ` [Qemu-devel] [RFC PATCH v4 11/11] target-ppc: Enable CPU hotplug for POWER8 CPU family Bharata B Rao
2015-08-06  8:42 ` [Qemu-devel] [RFC PATCH v4 00/11] sPAPR CPU hotplug Zhu Guihua
2015-08-10  3:31   ` Bharata B Rao
2015-08-12  2:56 ` David Gibson

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=20150909065802.GH17433@in.ibm.com \
    --to=bharata@linux.vnet.ibm.com \
    --cc=afaerber@suse.de \
    --cc=agraf@suse.de \
    --cc=aik@ozlabs.ru \
    --cc=david@gibson.dropbear.id.au \
    --cc=imammedo@redhat.com \
    --cc=mdroth@linux.vnet.ibm.com \
    --cc=nfont@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --cc=thuth@redhat.com \
    --cc=tyreld@linux.vnet.ibm.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).