From: Jes Sorensen <Jes.Sorensen@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
Kevin O'Connor <kevin@koconnor.net>,
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 12:41:51 +0200 [thread overview]
Message-ID: <4BD810EF.5070601@redhat.com> (raw)
In-Reply-To: <20100428103020.GQ10044@redhat.com>
On 04/28/10 12:30, Gleb Natapov wrote:
> On Wed, Apr 28, 2010 at 11:31:00AM +0200, Jes Sorensen wrote:
>> On 04/22/10 03:12, Kevin O'Connor wrote:
>> Generating the more complex tables dynamically would be preferred, but
>> it requires like half an AML compiler in Seabios, so it kinda stalled
>> there....
>>
> We can try to be smart and generate most of the code statically and only
> minimum that absolutely required dynamically. Haven't looked at how
> simple dynamic part can be made.
I looked at it briefly and ran away screaming :) I am sure it can be
done, bit it would require pretty good understanding of the AML encodings.
The CPU declarations are particularly tricky as they get pretty big and
complex and need to live in the DSDT, whereas a lot of other things we
can shift off to separate SSDT tables and only put the minimum that
needs to be generated dynamically in it's own table.
Cheers,
Jes
next prev parent reply other threads:[~2010-04-28 10:42 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 ` [Qemu-devel] Re: [SeaBIOS] " Jes Sorensen
2010-04-28 10:30 ` Gleb Natapov
2010-04-28 10:41 ` Jes Sorensen [this message]
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=4BD810EF.5070601@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=gleb@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).