From: Gerd Hoffmann <kraxel@redhat.com>
To: qemu-devel@nongnu.org
Cc: aarcange@redhat.com, Gerd Hoffmann <kraxel@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/2] fw_cfg: add etc/e820
Date: Tue, 22 Oct 2013 16:05:27 +0200 [thread overview]
Message-ID: <1382450729-6234-1-git-send-email-kraxel@redhat.com> (raw)
Hi,
Mini patch series adds a new file to fw_cfg, holding a e820 map with
both reservations and ram regions. The existing fw_cfg entry with e820
reservations only is left as-is.
This allows to (a) support more than 1TB of memory (which is impossible
using the current cmos entries) and (b) support non-contignous memory in
the furure without having to introduce a new interface for that.
please review,
Gerd
Gerd Hoffmann (2):
pc: add etc/e820 fw_cfg file
pc: register e820 entries for ram
hw/i386/pc.c | 41 ++++++++++++++++++++++++++++++-----------
1 file changed, 30 insertions(+), 11 deletions(-)
--
1.8.3.1
next reply other threads:[~2013-10-22 14:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 14:05 Gerd Hoffmann [this message]
2013-10-22 14:05 ` [Qemu-devel] [PATCH 1/2] pc: add etc/e820 fw_cfg file Gerd Hoffmann
2013-10-22 14:05 ` [Qemu-devel] [PATCH 2/2] pc: register e820 entries for ram Gerd Hoffmann
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=1382450729-6234-1-git-send-email-kraxel@redhat.com \
--to=kraxel@redhat.com \
--cc=aarcange@redhat.com \
--cc=qemu-devel@nongnu.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).