From: Alex Williamson <alex.williamson@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: allen.m.kay@intel.com, Kevin O'Connor <kevin@koconnor.net>,
seabios@seabios.org, qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH v3 3/3] fw/pci: Allocate IGD stolen memory
Date: Mon, 15 Feb 2016 10:46:35 -0700 [thread overview]
Message-ID: <20160215104635.00814fb3@t450s.home> (raw)
In-Reply-To: <1455532301.7504.17.camel@redhat.com>
On Mon, 15 Feb 2016 11:31:41 +0100
Gerd Hoffmann <kraxel@redhat.com> wrote:
> Hi,
>
> > The issue is in the VM and it occurs every time the option ROM is
> > executed. Standard VGA text mode displays fine (ex. SeaBIOS version
> > string and boot menu), but any sort of extended graphics mode (ex. live
> > CD boot menu) tries to make use of the host memory area which
> > corresponds to the stolen memory area of the physical device.
>
> I'm wondering whenever we can just use seavgabios (and support standard
> vga modes only).
The reason we need the vBIOS is to turn on the LCD panel, which in turn
has this dependency on the stolen memory area. I'd be pretty surprised
if a generic VGA BIOS affected the panel in any way. Maybe seavgabios
could be used for desktop IGD assignment, though I don't really know
how to detect an attached panel. Thanks,
Alex
prev parent reply other threads:[~2016-02-15 17:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 0:23 [Qemu-devel] [RFC PATCH v3 0/3] IGD assignment support for QEMU/vfio Alex Williamson
2016-02-13 0:23 ` [Qemu-devel] [RFC PATCH v3 1/3] fw/pci: Add support for mapping Intel IGD OpRegion via QEMU Alex Williamson
2016-02-13 0:23 ` [Qemu-devel] [RFC PATCH v3 2/3] Further increase maximum size of permanent high memory area Alex Williamson
2016-02-13 0:23 ` [Qemu-devel] [RFC PATCH v3 3/3] fw/pci: Allocate IGD stolen memory Alex Williamson
2016-02-13 2:49 ` Kevin O'Connor
2016-02-13 15:12 ` Alex Williamson
2016-02-13 18:18 ` Kevin O'Connor
2016-02-13 18:51 ` Alex Williamson
2016-02-13 20:05 ` Kevin O'Connor
2016-02-13 20:57 ` Alex Williamson
2016-02-14 0:20 ` Kevin O'Connor
2016-02-14 1:03 ` Alex Williamson
2016-02-15 9:54 ` Igor Mammedov
2016-02-15 19:20 ` Alex Williamson
2016-02-15 19:29 ` Michael S. Tsirkin
2016-02-15 19:50 ` Kevin O'Connor
2016-02-15 20:08 ` Michael S. Tsirkin
2016-02-15 19:54 ` Alex Williamson
2016-02-16 12:08 ` Gerd Hoffmann
2016-02-15 14:15 ` Kevin O'Connor
2016-02-15 10:31 ` Gerd Hoffmann
2016-02-15 17:46 ` Alex Williamson [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=20160215104635.00814fb3@t450s.home \
--to=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=kevin@koconnor.net \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--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).