From: Alex Williamson <alex.williamson@redhat.com>
To: seabios@seabios.org
Cc: alex.williamson@redhat.com, allen.m.kay@intel.com,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: [Qemu-devel] [RFC PATCH v3 0/3] IGD assignment support for QEMU/vfio
Date: Fri, 12 Feb 2016 17:23:01 -0700 [thread overview]
Message-ID: <20160213001835.18456.46422.stgit@gimli.home> (raw)
Turns out that maybe we weren't done with IGD by simply reading a
new fw_cfg, copying it into a new reserved memory buffer and writing
back to the IGD device. We need another reserved memory buffer for
stolen memory. The hardware minimum size is 1MB, naturally aligned,
which means we need to be able to actually be able to allocate that.
We write the address of the buffer back to the BDSM register on IGD
so that QEMU can make use of it when doing fixups on vBIOS config
of the device. Previous comments on updating the size of the high
memory area suggest that any remaining free memory is returned, so
it appears there's no affect of increasing this limit for systems
without IGD. Thanks,
Alex
---
Alex Williamson (3):
fw/pci: Add support for mapping Intel IGD OpRegion via QEMU
Further increase maximum size of permanent high memory area.
fw/pci: Allocate IGD stolen memory
src/config.h | 2 +-
src/fw/pciinit.c | 41 +++++++++++++++++++++++++++++++++++++++++
2 files changed, 42 insertions(+), 1 deletion(-)
next reply other threads:[~2016-02-13 0:23 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 0:23 Alex Williamson [this message]
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
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=20160213001835.18456.46422.stgit@gimli.home \
--to=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.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).