From: Jes Sorensen <jes@sgi.com>
To: Paul Brook <paul@codesourcery.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [patch] move MAX_CPUS to cpu.h
Date: Tue, 23 Sep 2008 14:53:30 +0200 [thread overview]
Message-ID: <48D8E6CA.9040802@sgi.com> (raw)
In-Reply-To: <200809231350.34178.paul@codesourcery.com>
Paul Brook wrote:
> On Tuesday 23 September 2008, Jes Sorensen wrote:
>> Paul> Anything using the value to allocate per-cpu structures will be
>> Paul> wrong.
>>
>> What do you mean? There's plenty places where you will want to only
>> allocate enough space for the number of cpus you want to support.
>
> Some ARM boards have 4 cpus, they just don't use the -smp option.
So what you're saying is that we need to distinguish between number of
possible CPUs and how many we allow for a given type of emulation? It
seems to me that using MAX_CPUS to be the maximum possible for an
architecture is fair and we should then maybe put it into the machine
description to set the upper limit for actual runtime ones?
Cheers,
Jes
next prev parent reply other threads:[~2008-09-23 12:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-23 11:44 [Qemu-devel] [patch] move MAX_CPUS to cpu.h Jes Sorensen
2008-09-23 12:08 ` Paul Brook
2008-09-23 12:10 ` Jes Sorensen
2008-09-23 12:50 ` Paul Brook
2008-09-23 12:53 ` Jes Sorensen [this message]
2008-09-23 13:04 ` Paul Brook
2008-09-23 13:10 ` Jes Sorensen
2008-09-25 15:21 ` [Qemu-devel] [patch] Introduce per machine based max_cpu variable Jes Sorensen
2008-09-30 14:47 ` Anthony Liguori
2008-09-30 15:06 ` Jes Sorensen
2008-09-30 15:18 ` Anthony Liguori
2008-10-01 13:22 ` Jes Sorensen
2008-09-30 15:19 ` Jes Sorensen
2008-10-02 15:45 ` Paul Brook
2008-10-03 9:40 ` Jes Sorensen
2008-09-23 14:13 ` [Qemu-devel] [patch] move MAX_CPUS to cpu.h M. Warner Losh
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=48D8E6CA.9040802@sgi.com \
--to=jes@sgi.com \
--cc=aliguori@us.ibm.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@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).