From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Gleb Natapov <gleb@redhat.com>
Cc: Jes Sorensen <Jes.Sorensen@redhat.com>,
Lucas Meneghel Rodrigues <lmr@redhat.com>,
seabios@seabios.org, qemu mailing list <qemu-devel@nongnu.org>,
KVM mailing list <kvm@vger.kernel.org>
Subject: Re: [SeaBIOS] About cpu_set, CPU hotplug and related subjects
Date: Tue, 11 May 2010 03:09:24 +0200 [thread overview]
Message-ID: <4BE8AE44.2050001@gmx.net> (raw)
In-Reply-To: <20100428104548.GS10044@redhat.com>
On 28.04.2010 12:45, Gleb Natapov wrote:
> On Wed, Apr 28, 2010 at 12:41:51PM +0200, Jes Sorensen wrote:
>
>> 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.
>>
>>
> We can generate complex code statically and call it from dynamically
> generated CPU declarations.
>
There is some ACPI code generator in coreboot. Not sure if it is usable
for those purposes. coreboot uses it to generate AMD CPU frequency tables.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
WARNING: multiple messages have this Message-ID (diff)
From: Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net>
To: Gleb Natapov <gleb@redhat.com>
Cc: Lucas Meneghel Rodrigues <lmr@redhat.com>,
Jes Sorensen <Jes.Sorensen@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: Tue, 11 May 2010 03:09:24 +0200 [thread overview]
Message-ID: <4BE8AE44.2050001@gmx.net> (raw)
In-Reply-To: <20100428104548.GS10044@redhat.com>
On 28.04.2010 12:45, Gleb Natapov wrote:
> On Wed, Apr 28, 2010 at 12:41:51PM +0200, Jes Sorensen wrote:
>
>> 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.
>>
>>
> We can generate complex code statically and call it from dynamically
> generated CPU declarations.
>
There is some ACPI code generator in coreboot. Not sure if it is usable
for those purposes. coreboot uses it to generate AMD CPU frequency tables.
Regards,
Carl-Daniel
--
http://www.hailfinger.org/
next prev parent reply other threads:[~2010-05-11 1:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-19 19:34 About cpu_set, CPU hotplug and related subjects Lucas Meneghel Rodrigues
2010-04-19 19:34 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-04-22 1:12 ` Kevin O'Connor
2010-04-22 1:12 ` [Qemu-devel] " Kevin O'Connor
2010-04-28 9:31 ` [SeaBIOS] " Jes Sorensen
2010-04-28 9:31 ` [Qemu-devel] " Jes Sorensen
2010-04-28 10:30 ` Gleb Natapov
2010-04-28 10:30 ` [Qemu-devel] " Gleb Natapov
2010-04-28 10:41 ` Jes Sorensen
2010-04-28 10:41 ` [Qemu-devel] " Jes Sorensen
2010-04-28 10:45 ` Gleb Natapov
2010-04-28 10:45 ` [Qemu-devel] " Gleb Natapov
2010-05-11 1:09 ` Carl-Daniel Hailfinger [this message]
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=4BE8AE44.2050001@gmx.net \
--to=c-d.hailfinger.devel.2006@gmx.net \
--cc=Jes.Sorensen@redhat.com \
--cc=gleb@redhat.com \
--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 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.