From: Gleb Natapov <gleb@redhat.com>
To: Avi Kivity <avi@redhat.com>
Cc: seabios@seabios.org, qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [SeaBIOS] [PATCHv2] load hpet info for HPET ACPI table from qemu
Date: Tue, 15 Jun 2010 09:50:48 +0300 [thread overview]
Message-ID: <20100615065047.GL21797@redhat.com> (raw)
In-Reply-To: <4C1705FB.2040605@redhat.com>
On Tue, Jun 15, 2010 at 07:47:55AM +0300, Avi Kivity wrote:
> On 06/14/2010 10:38 PM, Anthony Liguori wrote:
> >
> >I think we can be pretty flexible as long as we're careful about
> >releases. For instance, I've applied Gleb's current patch but
> >won't update SeaBIOS until the interface is worked out. If we
> >decide to implement a new interface, there's no harm since we've
> >never had a qemu build that had a combination of SeaBIOS and
> >fw_cfg that didn't work.
>
> Or we can choose a new interface number if the interface changes.
>
> One of Kevin's points was that the ACPI tables are a documented
> interface. AFAIR, the firmware configuration interface isn't. We
> need to start documenting it (and reject patches without
> accompanying documentation).
>
ACPI tables are, indeed, documented interface (it doesn't make it good
interface though :)), but it is interface between firmware and OS, so
it may (and it does) have things like "if firmware support that, then
this bit should be set". Using it as interface to describe HW to
firmware is just plain abuse.
--
Gleb.
next prev parent reply other threads:[~2010-06-15 6:50 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 [this message]
2010-06-17 1:47 ` Kevin O'Connor
2010-06-17 3:58 ` Avi Kivity
2010-06-17 6:57 ` Peter Stuge
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=20100615065047.GL21797@redhat.com \
--to=gleb@redhat.com \
--cc=avi@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).