From: Peter Stuge <peter@stuge.se>
To: Avi Kivity <avi@redhat.com>
Cc: Kevin O'Connor <kevin@koconnor.net>,
seabios@seabios.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [SeaBIOS] [PATCHv2] load hpet info for HPET ACPI table from qemu
Date: Thu, 17 Jun 2010 08:57:57 +0200 [thread overview]
Message-ID: <20100617065757.14138.qmail@stuge.se> (raw)
In-Reply-To: <4C199D68.8070204@redhat.com>
Avi Kivity wrote:
> In general, ACPI code can work with memory or device registers that have
> been initialized by the BIOS and depend on them. It's possible to write
> ACPI code that depends on preceding BIOS code.
It's also possible to write C code that makes extensive use of goto. :)
To be fair, ACPI bytecode for actual hardware may need to rely on the
firmware because of limitations in the hardware. But I think qemu is
one instance where any ACPI bytecode can be kept simple.
> I don't know if that's the case with our ACPI implementation.
Where is that code? Who has the ASL for qemu? Who wrote it? Is it big?
//Peter
next prev parent reply other threads:[~2010-06-17 6:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 8:30 [Qemu-devel] [PATCHv2] load hpet info for HPET ACPI table from qemu Gleb Natapov
2010-06-14 13:54 ` [Qemu-devel] Re: [SeaBIOS] " Kevin O'Connor
2010-06-14 14:09 ` Gleb Natapov
2010-06-14 14:40 ` Jamie Lokier
2010-06-14 16:03 ` Gleb Natapov
2010-06-14 14:51 ` Avi Kivity
2010-06-14 18:25 ` Kevin O'Connor
2010-06-14 18:56 ` Gleb Natapov
2010-06-14 20:12 ` Kevin O'Connor
2010-06-15 6:37 ` Gleb Natapov
2010-06-17 1:22 ` Kevin O'Connor
2010-06-17 7:45 ` Gleb Natapov
2010-06-17 1:58 ` Peter Stuge
2010-06-14 19:38 ` Anthony Liguori
2010-06-15 4:47 ` Avi Kivity
2010-06-15 6:50 ` Gleb Natapov
2010-06-17 1:47 ` Kevin O'Connor
2010-06-17 3:58 ` Avi Kivity
2010-06-17 6:57 ` Peter Stuge [this message]
2010-06-15 0:54 ` Paul Brook
2010-06-15 4:41 ` Avi Kivity
2010-06-17 0:55 ` Kevin O'Connor
2010-06-17 6:44 ` Gleb Natapov
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=20100617065757.14138.qmail@stuge.se \
--to=peter@stuge.se \
--cc=avi@redhat.com \
--cc=kevin@koconnor.net \
--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).