From: Peter Maydell <peter.maydell@linaro.org>
To: Joel Schopp <joel.schopp@amd.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] aarch64: raise max_cpus to 8
Date: Wed, 20 Aug 2014 16:55:42 +0100 [thread overview]
Message-ID: <CAFEAcA_oXU9ZKpO=ht1oF7d3ysO3Z45jZtpTk2Gum12hJR_X+A@mail.gmail.com> (raw)
In-Reply-To: <53F4B9D7.7010409@amd.com>
On 20 August 2014 16:08, Joel Schopp <joel.schopp@amd.com> wrote:
>
> On 08/19/2014 05:43 PM, Peter Maydell wrote:
>> On 19 August 2014 22:33, Joel Schopp <joel.schopp@amd.com> wrote:
>>> I'm running on a system with 8 cpus and it would be nice to have qemu
>>> support all of them. The attached patch does that and has been tested.
>>>
>>> That said, I'm not sure if 8 is enough or if we want to bump this even higher
>>> now before systems with many more cpus come along. 255 anyone?
>> 8 is the limit for a GICv2 system. But yes, we could have 8 CPUs
>> here; I think this was just copied over from the vexpress boards
>> (which have 4 because that hardware has 4.)
> So the question is do we want to wait for the GICv3 changes to be merged
> to bump this to 255? If we do want to wait then applying my patch that
> bumps it to 8 is the right thing to do now.
I'm not currently aware of any GICv3 support patches for QEMU
(I know there is some kernel work); it's the view the guest sees
that matters, and for QEMU based guests that has to be v2
currently.
So yes, we should bump to 8 for now.
-- PMM
next prev parent reply other threads:[~2014-08-20 15:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-19 21:33 [Qemu-devel] [PATCH] aarch64: raise max_cpus to 8 Joel Schopp
2014-08-19 22:43 ` Peter Maydell
2014-08-20 15:08 ` Joel Schopp
2014-08-20 15:55 ` Peter Maydell [this message]
2014-08-29 13:18 ` Peter Maydell
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='CAFEAcA_oXU9ZKpO=ht1oF7d3ysO3Z45jZtpTk2Gum12hJR_X+A@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--cc=joel.schopp@amd.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 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.