From: Gerd Hoffmann <kraxel@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: Alex Williamson <alex.williamson@redhat.com>,
seabios@seabios.org, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [SeaBIOS] [RFC PATCH v2] fw/pci: Add support for mapping Intel IGD OpRegion via QEMU
Date: Fri, 05 Feb 2016 08:58:11 +0100 [thread overview]
Message-ID: <1454659091.5539.16.camel@redhat.com> (raw)
In-Reply-To: <20160204175823.75cc7e25@nial.brq.redhat.com>
Hi,
> > + if (file->copy(file, opregion, file->size) < 0) {
> Is opregion content on host immutable?
> if not then copying it probably wrong and it should be passed-through.
The OpRegion is used for communication between bios and driver, it is
*not* something going directly to the hardware. There is also the VBT
(video bios table) with some configuration information (most notably
laptop panel info). The latter will be used by the guest driver.
To make stuff like brightness control work is is not enough to
pass-through the opregion, we would also have to somehow forward acpi
notifications and acpi calls between host and guest, so the guest driver
can talk to the host bios. That is seriously non-trivial, for little
(if any) gain.
cheers,
Gerd
prev parent reply other threads:[~2016-02-05 7:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 20:10 [Qemu-devel] [RFC PATCH v2] fw/pci: Add support for mapping Intel IGD OpRegion via QEMU Alex Williamson
2016-02-03 9:04 ` [Qemu-devel] [SeaBIOS] " Gerd Hoffmann
2016-02-03 19:43 ` Alex Williamson
2016-02-03 21:38 ` Alex Williamson
2016-02-03 22:09 ` Kevin O'Connor
2016-02-03 23:52 ` Alex Williamson
2016-02-04 7:52 ` Gerd Hoffmann
2016-02-04 16:01 ` Kevin O'Connor
2016-02-04 16:58 ` Igor Mammedov
2016-02-05 5:44 ` Alex Williamson
2016-02-05 7:58 ` Gerd Hoffmann [this message]
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=1454659091.5539.16.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=imammedo@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).