From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin O'Connor <kevin@koconnor.net>
Cc: seabios@seabios.org, qemu-devel@nongnu.org,
Gleb Natapov <gleb@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/2] Get system state configuration from QEMU and patcth DSDT with it.
Date: Thu, 17 May 2012 12:01:35 +0200 [thread overview]
Message-ID: <4FB4CC7F.40001@redhat.com> (raw)
In-Reply-To: <20120517002453.GB19382@morn.localdomain>
Il 17/05/2012 02:24, Kevin O'Connor ha scritto:
>> > Can we build an SSDT that includes the contents of fw_cfg (e.g.
>> > FW_CFG_SIGNATURE at offset 0, FW_CFG_UUID at offset 4, FW_CFG_NOGRAPHIC
>> > at offset 16... the entry <-> offset mapping and the defaults would be
>> > part of SeaBIOS), and then read that data from normal DSDT methods?
>> >
>> > That would be similar to Gerd's patch, but without letting the OSPM use
>> > the real fw_cfg device.
> I'm not sure I understand your proposal. Are you suggesting reading
> every fw_cfg "port" into memory and then passing that memory into an
> SSDT? If so, that wouldn't be easy (we don't necessarily know the
> size of each "port") and could potentially waste a lot of memory
> (think a vmlinuz stored in fw_cfg).
No, only entries and/or files that are needed by the DSDT (PCI region
and sleep data).
Paolo
next prev parent reply other threads:[~2012-05-17 10:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 12:35 [Qemu-devel] [PATCH 1/2] Add ACPI_EXTRACT_PKG_START macro parsing Gleb Natapov
2012-05-14 12:35 ` [Qemu-devel] [PATCH 2/2] Get system state configuration from QEMU and patcth DSDT with it Gleb Natapov
2012-05-15 1:43 ` Kevin O'Connor
2012-05-15 8:06 ` Gleb Natapov
2012-05-15 23:18 ` Kevin O'Connor
2012-05-16 13:46 ` Gleb Natapov
2012-05-16 15:50 ` Paolo Bonzini
2012-05-16 16:40 ` Gleb Natapov
2012-05-16 16:47 ` Paolo Bonzini
2012-05-16 17:01 ` Gleb Natapov
2012-05-17 0:24 ` Kevin O'Connor
2012-05-17 10:01 ` Paolo Bonzini [this message]
2012-05-17 0:20 ` Kevin O'Connor
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=4FB4CC7F.40001@redhat.com \
--to=pbonzini@redhat.com \
--cc=gleb@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).