From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
seabios@seabios.org, qemu mailing list <qemu-devel@nongnu.org>,
KVM mailing list <kvm@vger.kernel.org>
Subject: [Qemu-devel] Re: [SeaBIOS] About cpu_set, CPU hotplug and related subjects
Date: Wed, 28 Apr 2010 11:31:00 +0200 [thread overview]
Message-ID: <4BD80054.9090409@redhat.com> (raw)
In-Reply-To: <20100422011200.GA10677@morn.localdomain>
On 04/22/10 03:12, Kevin O'Connor wrote:
> As I understand it, the hotplug support was only in the kvm copy of
> bochs bios. It also limited the number of cpus one could use (I think
> 16).
>
> The current smp support in SeaBIOS doesn't limit the number of cpus.
>
> So, there has been reluctance to just port the old kvm bios code
> forward.
I believe the number was limited to 15, due to limits in a certain
proprietary operating system.
The issue with the AML code in BOCHS vs the code in Seabios is a bit
tricky. The tables in BOCHS are a fair bit more complicated with the
hotplug code and therefore statically generated, whereas Seabios
generates them dynamically at boot time.
Generating the more complex tables dynamically would be preferred, but
it requires like half an AML compiler in Seabios, so it kinda stalled
there....
Cheers,
Jes
next prev parent reply other threads:[~2010-04-28 9:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 19:34 [Qemu-devel] About cpu_set, CPU hotplug and related subjects Lucas Meneghel Rodrigues
2010-04-22 1:12 ` [Qemu-devel] " Kevin O'Connor
2010-04-28 9:31 ` Jes Sorensen [this message]
2010-04-28 10:30 ` [Qemu-devel] Re: [SeaBIOS] " Gleb Natapov
2010-04-28 10:41 ` Jes Sorensen
2010-04-28 10:45 ` Gleb Natapov
2010-05-11 1:09 ` Carl-Daniel Hailfinger
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=4BD80054.9090409@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=kevin@koconnor.net \
--cc=kvm@vger.kernel.org \
--cc=lmr@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).