From: Gerd Hoffmann <kraxel@redhat.com>
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, Kevin O'Connor <kevin@koconnor.net>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH v3 3/3] fw/pci: Allocate IGD stolen memory
Date: Tue, 16 Feb 2016 13:08:56 +0100 [thread overview]
Message-ID: <1455624536.7504.76.camel@redhat.com> (raw)
In-Reply-To: <20160215122023.737c7781@t450s.home>
Hi,
> I don't mind the allocation of guest memory issue, the fact that guest
> memory is consumed by built-in devices is exactly what happens on bare
> metal.
And following in qemu what happens on bare metal usually works best
long-term.
> to pre-populate it, we could. It at least puts QEMU in control, but
> relaying back the address via a device specific register is still a bit
> ugly.
It is the usual way. We do the same for a few other addresses too
(mmconfig xbar, acpi registers). Firmware programs the hardware, and
qemu picks up the addresses from there (and puts them into the generated
acpi tables for example).
Main advantage is that we don't need a paravirtual firmware <=> qemu
interface for each address.
Yes, each firmware (seabios/ovmf/...) needs to handle it then. But if
we allocate the stolen memory from guest ram the firmware has to handle
it _anyway_ so it is marked reserved in e820 etc.
cheers,
Gerd
next prev parent reply other threads:[~2016-02-16 12:09 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 [this message]
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=1455624536.7504.76.camel@redhat.com \
--to=kraxel@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=allen.m.kay@intel.com \
--cc=imammedo@redhat.com \
--cc=kevin@koconnor.net \
--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;
as well as URLs for NNTP newsgroup(s).