From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Wei Liu <wei.liu2@citrix.com>
Cc: xen-devel@lists.xenproject.org
Subject: Re: [PATCH RFC 4/4] hvmloader:ovmf: setup E820 map
Date: Tue, 19 Nov 2013 14:56:31 -0500 [thread overview]
Message-ID: <20131119195631.GA7921@phenom.dumpdata.com> (raw)
In-Reply-To: <1384531165-3600-5-git-send-email-wei.liu2@citrix.com>
On Fri, Nov 15, 2013 at 03:59:25PM +0000, Wei Liu wrote:
> E820 map will be used by OVMF to create memory map.
>
> Signed-off-by: Wei Liu <wei.liu2@citrix.com>
> ---
> tools/firmware/hvmloader/ovmf.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/tools/firmware/hvmloader/ovmf.c b/tools/firmware/hvmloader/ovmf.c
> index c253083..52ccd0d 100644
> --- a/tools/firmware/hvmloader/ovmf.c
> +++ b/tools/firmware/hvmloader/ovmf.c
> @@ -128,6 +128,17 @@ static void ovmf_create_smbios_tables(void)
> SMBIOS_PHYSICAL_END);
> }
>
> +static void ovmf_setup_e820(void)
> +{
> + struct ovmf_info *info = (void *)OVMF_INFO_PHYSICAL_ADDRESS;
> + struct e820entry *e820 = scratch_alloc(sizeof(struct e820entry)*16, 0);
16? Why not 128 (the default in most kernels)?
> + info->e820 = (uint32_t)e820;
> +
> + /* OVMF doesn't load bios image below 0x100000 */
> + info->e820_nr = build_e820_table(e820, 0, 0xfffff);
> + dump_e820_table(e820, info->e820_nr);
> +}
> +
> struct bios_config ovmf_config = {
> .name = "OVMF",
>
> @@ -142,7 +153,7 @@ struct bios_config ovmf_config = {
> .bios_info_setup = ovmf_setup_bios_info,
> .bios_info_finish = ovmf_finish_bios_info,
>
> - .e820_setup = NULL,
> + .e820_setup = ovmf_setup_e820,
>
> .acpi_build_tables = ovmf_acpi_build_tables,
> .create_mp_tables = NULL,
> --
> 1.7.10.4
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2013-11-19 19:56 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 15:59 [PATCH RFC 0/4] hvmloader: make OVMF work with Xen Wei Liu
2013-11-15 15:59 ` [PATCH RFC 1/4] hvmloader/ovmf: increase blob size to 2MB Wei Liu
2013-11-19 17:49 ` Ian Campbell
2013-11-19 20:49 ` Wei Liu
2013-11-20 10:13 ` Ian Campbell
2013-11-15 15:59 ` [PATCH RFC 2/4] hvmloader/ovmf: show OVMF_BEGIN as bios address Wei Liu
2013-11-19 17:51 ` Ian Campbell
2013-11-15 15:59 ` [PATCH RFC 3/4] hvmloader/ovmf: setup ovmf_info Wei Liu
2013-11-19 17:54 ` Ian Campbell
2013-11-19 18:03 ` Wei Liu
2013-11-20 10:08 ` Ian Campbell
2013-11-15 15:59 ` [PATCH RFC 4/4] hvmloader:ovmf: setup E820 map Wei Liu
2013-11-19 17:56 ` Ian Campbell
2013-11-19 18:01 ` Wei Liu
2013-11-20 10:07 ` Ian Campbell
2013-11-20 11:49 ` Wei Liu
2013-11-20 11:51 ` Ian Campbell
2013-11-20 11:58 ` Wei Liu
2013-11-20 12:11 ` Ian Campbell
2013-11-20 12:19 ` Wei Liu
2013-11-19 19:56 ` Konrad Rzeszutek Wilk [this message]
2013-11-19 20:05 ` Wei Liu
2013-11-20 10:12 ` Ian Campbell
2013-11-20 14:04 ` Konrad Rzeszutek Wilk
2013-11-20 14:05 ` Ian Campbell
2013-11-19 17:47 ` [PATCH RFC 0/4] hvmloader: make OVMF work with Xen Ian Campbell
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=20131119195631.GA7921@phenom.dumpdata.com \
--to=konrad.wilk@oracle.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.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).