From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
Cc: Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
bharata@linux.vnet.ibm.com, benh@kernel.crashing.org
Subject: Re: [Qemu-devel] [PATCH] ppc/pnv: fix cores per chip for multiple cpus
Date: Fri, 22 Sep 2017 21:49:33 +1000 [thread overview]
Message-ID: <20170922114933.GU4998@umbus.fritz.box> (raw)
In-Reply-To: <42a1f20a-09d0-f510-c3be-4062b7ffdafe@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Fri, Sep 22, 2017 at 01:37:39PM +0200, Cédric Le Goater wrote:
> >> well, it would be good to be able to define chips with different
> >> numbers of cpus. That is something will we want to do for sure.
> >
> > You mean multiple chips in a single system with non-uniform numbers of
> > cores? Are there really such systems in the wild?
> >
>
> When CPU fail for some reason, yes. They are garded by the FW and next
> boot the system will have different numbers of CPUs on its chip.
Ok, but you can model that with max_cpus the full potential number,
then just don't have all of them on initially. The basic topology
remains uniform.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2017-09-22 12:00 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 8:27 [Qemu-devel] [PATCH] ppc/pnv: fix cores per chip for multiple cpus Nikunj A Dadhania
2017-09-08 6:38 ` Cédric Le Goater
2017-09-09 7:02 ` David Gibson
2017-09-11 5:10 ` Nikunj A Dadhania
2017-09-13 7:35 ` David Gibson
2017-09-14 5:12 ` Nikunj A Dadhania
2017-09-15 6:48 ` David Gibson
2017-09-15 8:23 ` Nikunj A Dadhania
2017-09-15 8:51 ` David Gibson
2017-09-15 9:09 ` Nikunj A Dadhania
2017-09-19 8:24 ` David Gibson
2017-09-20 4:20 ` Nikunj A Dadhania
2017-09-20 4:55 ` David Gibson
2017-09-20 5:13 ` Nikunj A Dadhania
2017-09-20 6:17 ` David Gibson
2017-09-20 6:40 ` Nikunj A Dadhania
2017-09-20 6:50 ` Nikunj A Dadhania
2017-09-20 6:57 ` David Gibson
2017-09-20 7:18 ` Nikunj A Dadhania
2017-09-20 8:12 ` Cédric Le Goater
2017-09-20 11:53 ` David Gibson
2017-09-21 3:54 ` Nikunj A Dadhania
2017-09-21 5:31 ` David Gibson
2017-09-22 6:00 ` Nikunj A Dadhania
2017-09-22 6:07 ` Cédric Le Goater
2017-09-22 10:12 ` David Gibson
2017-09-22 10:46 ` Cédric Le Goater
2017-09-22 11:20 ` David Gibson
2017-09-22 11:37 ` Cédric Le Goater
2017-09-22 11:49 ` David Gibson [this message]
2017-09-22 11:46 ` [Qemu-devel] [Qemu-ppc] " Greg Kurz
2017-09-22 10:56 ` [Qemu-devel] " Cédric Le Goater
2017-09-22 11:06 ` Nikunj A Dadhania
2017-09-22 11:36 ` David Gibson
2017-09-21 6:04 ` Cédric Le Goater
2017-09-21 7:42 ` Igor Mammedov
2017-09-22 10:09 ` David Gibson
2017-09-22 10:08 ` David Gibson
2017-09-22 10:52 ` Cédric Le Goater
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=20170922114933.GU4998@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=benh@kernel.crashing.org \
--cc=bharata@linux.vnet.ibm.com \
--cc=clg@kaod.org \
--cc=nikunj@linux.vnet.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
/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).