Kernel KVM virtualization development
 help / color / mirror / Atom feed
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 v4] fw/pci: Add support for mapping Intel IGD via QEMU
Date: Wed, 11 May 2016 11:19:25 -0400	[thread overview]
Message-ID: <20160511151924.GB14689@morn.lan> (raw)
In-Reply-To: <20160510091952.23c9e0d2@t450s.home>

On Tue, May 10, 2016 at 09:19:52AM -0600, Alex Williamson wrote:
> On Tue, 23 Feb 2016 10:22:33 -0500
> "Kevin O'Connor" <kevin@koconnor.net> wrote:
> 
> > On Tue, Feb 16, 2016 at 02:39:27PM -0700, Alex Williamson wrote:
> > > QEMU provides two fw_cfg files to support IGD.  The first holds the
> > > OpRegion data which holds the Video BIOS Table (VBT).  This needs to
> > > be copied into reserved memory and the address stored in the ASL
> > > Storage register of the device at 0xFC offset in PCI config space.
> > > The OpRegion is generally 8KB.  This file is named "etc/igd-opregion".
> > > 
> > > The second file tells us the required size of the stolen memory space
> > > for the device.  This is a dummy file, it has no backing so we only
> > > allocate the space without copying anything into it.  This space
> > > requires 1MB alignment and is generally either 1MB or 2MB, depending
> > > on the hardware config.  If the user has opted in QEMU to expose
> > > additional stolen memory beyond the GTT (GGMS), the GMS may add an
> > > additional 32MB to 512MB.  The base address of the reserved memory
> > > allocated for this is written back to the Base Data of Stolen Memory
> > > register (BDSM) at PCI config offset 0x5C on the device.  This file is
> > > named "etc/igd-bdsm".  
> > 
> > Thanks.  I'd be interested in seeing how the discussion with Michael
> > and Igor works out (wrt using a standardized interface for
> > communicating addresses between qemu and firmware) before adopting
> > this interface in SeaBIOS.
> 
> Apologies if I missed it, but I haven't seen any work in this
> direction, please point me to it if I'm wrong.  Now that QEMU 2.6 is
> wrapping up, I'd like to get IGD assignment support in for 2.7, but we
> can't do that without BIOS support.  How shall we proceed?  Thanks,

If there's no consensus on standardizing the qemu/firmware interface
for addresses then I'm okay with the custom solution you last
proposed.  So, I'd say submit your patches and if they are accepted in
QEMU then I will follow suit and apply them to SeaBIOS.

-Kevin

  parent reply	other threads:[~2016-05-11 15:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-16 21:39 [RFC PATCH v4] fw/pci: Add support for mapping Intel IGD via QEMU Alex Williamson
2016-02-17 11:09 ` Tian, Kevin
2016-02-17 13:49   ` Alex Williamson
2016-02-18  6:43     ` Tian, Kevin
2016-02-23 15:22 ` Kevin O'Connor
2016-05-10 15:19   ` Alex Williamson
2016-05-11 10:07     ` [Qemu-devel] " Igor Mammedov
2016-05-11 15:19     ` Kevin O'Connor [this message]
2016-05-11 18:39       ` 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=20160511151924.GB14689@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox