From: Kevin O'Connor <kevin@koconnor.net>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: seabios@seabios.org, allen.m.kay@intel.com,
qemu-devel@nongnu.org, kvm@vger.kernel.org,
"Michael S. Tsirkin" <mst@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [RFC PATCH v3 3/3] fw/pci: Allocate IGD stolen memory
Date: Mon, 15 Feb 2016 09:15:09 -0500 [thread overview]
Message-ID: <20160215141509.GA29746@morn.lan> (raw)
In-Reply-To: <20160213180331.2aa0d010@t450s.home>
On Sat, Feb 13, 2016 at 06:03:31PM -0700, Alex Williamson wrote:
> On Sat, 13 Feb 2016 19:20:32 -0500
> "Kevin O'Connor" <kevin@koconnor.net> wrote:
> > This confuses me - why didn't the host system BIOS turn on the LCD
> > panel during host bootup?
>
> It turns off when we reset the device between VM instances or between
> VM boots. IGD supports Function Level Reset (FLR).
>
> > >Another desktop IvyBridge system
> > > doesn't really care about the vBIOS so long as we don't ask it to
> > > output anything before the guest native drivers are loaded. If we
> > > could, I think we'd just enable vBIOS for laptop panel support, but
> > > that's really not an option, it's going to run as a boot option ROM as
> > > well, so we need to fix the issues that it generates there.
> >
> > From my experience with coreboot, running the vga option rom multiple
> > times during a given boot is very fragile. (By multiple times, I mean
> > either the host running it and then a guest, or running it multiple
> > times from multiple guests.) YMMV.
>
> We do this regularly for graphics assignment, Nvidia, AMD, and now
> Intel. It generally works ok. Perhaps you've seen issues with the
> option ROM being run multiple times without resetting the device. I
> could certainly believe that.
Interesting. Using the FLR could be useful on some coreboot systems
where users want to run the option rom twice. Thanks.
-Kevin
WARNING: multiple messages have this Message-ID (diff)
From: Kevin O'Connor <kevin@koconnor.net>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
seabios@seabios.org, allen.m.kay@intel.com,
qemu-devel@nongnu.org, Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH v3 3/3] fw/pci: Allocate IGD stolen memory
Date: Mon, 15 Feb 2016 09:15:09 -0500 [thread overview]
Message-ID: <20160215141509.GA29746@morn.lan> (raw)
In-Reply-To: <20160213180331.2aa0d010@t450s.home>
On Sat, Feb 13, 2016 at 06:03:31PM -0700, Alex Williamson wrote:
> On Sat, 13 Feb 2016 19:20:32 -0500
> "Kevin O'Connor" <kevin@koconnor.net> wrote:
> > This confuses me - why didn't the host system BIOS turn on the LCD
> > panel during host bootup?
>
> It turns off when we reset the device between VM instances or between
> VM boots. IGD supports Function Level Reset (FLR).
>
> > >Another desktop IvyBridge system
> > > doesn't really care about the vBIOS so long as we don't ask it to
> > > output anything before the guest native drivers are loaded. If we
> > > could, I think we'd just enable vBIOS for laptop panel support, but
> > > that's really not an option, it's going to run as a boot option ROM as
> > > well, so we need to fix the issues that it generates there.
> >
> > From my experience with coreboot, running the vga option rom multiple
> > times during a given boot is very fragile. (By multiple times, I mean
> > either the host running it and then a guest, or running it multiple
> > times from multiple guests.) YMMV.
>
> We do this regularly for graphics assignment, Nvidia, AMD, and now
> Intel. It generally works ok. Perhaps you've seen issues with the
> option ROM being run multiple times without resetting the device. I
> could certainly believe that.
Interesting. Using the FLR could be useful on some coreboot systems
where users want to run the option rom twice. Thanks.
-Kevin
next prev parent reply other threads:[~2016-02-15 14:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 0:23 [RFC PATCH v3 0/3] IGD assignment support for QEMU/vfio Alex Williamson
2016-02-13 0:23 ` [Qemu-devel] " Alex Williamson
2016-02-13 0:23 ` [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] " Alex Williamson
2016-02-13 0:23 ` [RFC PATCH v3 2/3] Further increase maximum size of permanent high memory area Alex Williamson
2016-02-13 0:23 ` [Qemu-devel] " Alex Williamson
2016-02-13 0:23 ` [RFC PATCH v3 3/3] fw/pci: Allocate IGD stolen memory Alex Williamson
2016-02-13 0:23 ` [Qemu-devel] " Alex Williamson
2016-02-13 2:49 ` Kevin O'Connor
2016-02-13 2:49 ` [Qemu-devel] " Kevin O'Connor
2016-02-13 15:12 ` Alex Williamson
2016-02-13 15:12 ` [Qemu-devel] " Alex Williamson
2016-02-13 18:18 ` Kevin O'Connor
2016-02-13 18:18 ` [Qemu-devel] " Kevin O'Connor
2016-02-13 18:51 ` Alex Williamson
2016-02-13 18:51 ` [Qemu-devel] " Alex Williamson
2016-02-13 20:05 ` Kevin O'Connor
2016-02-13 20:05 ` [Qemu-devel] " Kevin O'Connor
2016-02-13 20:57 ` Alex Williamson
2016-02-13 20:57 ` [Qemu-devel] " Alex Williamson
2016-02-14 0:20 ` Kevin O'Connor
2016-02-14 0:20 ` [Qemu-devel] " Kevin O'Connor
2016-02-14 1:03 ` Alex Williamson
2016-02-14 1:03 ` [Qemu-devel] " Alex Williamson
2016-02-15 9:54 ` Igor Mammedov
2016-02-15 9:54 ` Igor Mammedov
2016-02-15 19:20 ` Alex Williamson
2016-02-15 19:20 ` Alex Williamson
2016-02-15 19:29 ` Michael S. Tsirkin
2016-02-15 19:29 ` Michael S. Tsirkin
2016-02-15 19:50 ` Kevin O'Connor
2016-02-15 19:50 ` Kevin O'Connor
2016-02-15 20:08 ` Michael S. Tsirkin
2016-02-15 20:08 ` Michael S. Tsirkin
2016-02-15 19:54 ` Alex Williamson
2016-02-15 19:54 ` Alex Williamson
2016-02-16 12:08 ` Gerd Hoffmann
2016-02-16 12:08 ` Gerd Hoffmann
2016-02-15 14:15 ` Kevin O'Connor [this message]
2016-02-15 14:15 ` Kevin O'Connor
2016-02-15 10:31 ` Gerd Hoffmann
2016-02-15 10:31 ` [Qemu-devel] " Gerd Hoffmann
2016-02-15 17:46 ` Alex Williamson
2016-02-15 17:46 ` [Qemu-devel] " Alex Williamson
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=20160215141509.GA29746@morn.lan \
--to=kevin@koconnor.net \
--cc=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.