From: Thomas Huth <thuth@redhat.com>
To: Programmingkid <programmingkidx@gmail.com>,
BALATON Zoltan <balaton@eik.bme.hu>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>,
"qemu-ppc@nongnu.org list:PowerPC" <qemu-ppc@nongnu.org>,
qemu-devel qemu-devel <qemu-devel@nongnu.org>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] [PATCH RFC 06/16] vl: move smp parsing to machine pre_init
Date: Wed, 15 Jun 2016 10:03:09 +0200 [thread overview]
Message-ID: <57610BBD.7070704@redhat.com> (raw)
In-Reply-To: <88030BF6-971D-43B5-84E3-7F0CF6CBDE33@gmail.com>
On 14.06.2016 23:32, Programmingkid wrote:
>
> On Jun 14, 2016, at 5:13 PM, BALATON Zoltan wrote:
>
>> On Tue, 14 Jun 2016, Programmingkid wrote:
>>> On Jun 14, 2016, at 7:39 AM, qemu-ppc-request@nongnu.org wrote:
>>>> smp_cores is only used by pseries and x86 machines. I expect machines
>>>> that must be single-socket to disregard smp_sockets altogether.
>>>
>>> Could smp support be added to the beigeg3 and mac99 targets?
>>
>> I think the machines these are emulating had no SMP so it would not make much sense. Maybe you'd need to create a new target emulating a Mac model with multiple CPUs instead or update mac99 to a newer model that had SMP?
>
> http://www.macworld.com/article/1002601/multiprocessor.html
> You will find this article enlightening.
>
>> But what would this bring besides more complexity and more possible bugs?
>
> - An emulator that can take better advantage of the host system's multiprocessor offering.
Please note that as long as the MTTCG patches are not included yet, this
point is currently not valid for QEMU yet (unless you use KVM as
accelerator).
Thomas
prev parent reply other threads:[~2016-06-15 8:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.7015.1465904373.1213.qemu-ppc@nongnu.org>
2016-06-14 14:44 ` [Qemu-devel] [Qemu-ppc] [PATCH RFC 06/16] vl: move smp parsing to machine pre_init Programmingkid
2016-06-14 21:13 ` BALATON Zoltan
2016-06-14 21:32 ` Programmingkid
2016-06-14 21:59 ` Paolo Bonzini
2016-06-15 8:03 ` Thomas Huth [this message]
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=57610BBD.7070704@redhat.com \
--to=thuth@redhat.com \
--cc=balaton@eik.bme.hu \
--cc=david@gibson.dropbear.id.au \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=programmingkidx@gmail.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).