From: Akio Takebe <takebe_akio@jp.fujitsu.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xensource.com>
Subject: Re: [Patch] Expand shadow memory area for using option ROM
Date: Mon, 05 Jan 2009 18:33:42 +0900 [thread overview]
Message-ID: <4961D3F6.20304@jp.fujitsu.com> (raw)
In-Reply-To: <C57E8EC0.1242%keir.fraser@eu.citrix.com>
Keir Fraser wrote
> On 26/12/2008 04:46, "Akio Takebe" <takebe_akio@jp.fujitsu.com> wrote:
>
>> This patch is:
>> - replace e820 table from 0xe0000 to 0xeb000.
>> - expand shadowr from 0xc0000-0xdffff to 0xc0000-0xe8fff.
>> - fix scan size of VGA BIOS.
>>
>> after this patch, BIOS map is below.
>> BIOS map:
>> c0000-c8fff: VGA BIOS
>> c9000-d57ff: Etherboot ROM
>> d5800-e0fff: PCI Option ROMs
>> e9000-e919c: SMBIOS tables
>> f0000-fffff: Main BIOS
>
> Comments:
>
> 1. Why does the VGA BIOS 'scan size' need to be fixed? What's wrong with
> scanning only up to 0xc8000 for it, and letting option ROMs continue to
> reside from 0xc8000? Indeed, won't the VGABIOS always be at 0xc0000, so we
> could actually only probe that address for it, and let option ROMs load as
> low as 0xc0800?
Because the current VGA BIOS uses 0xc0000-0xc8fff from the following log.
I want just to avoid the unnecessary scanning.
(XEN) HVM1: BIOS map:
(XEN) HVM1: c0000-c8fff: VGA BIOS
(XEN) HVM1: c9000-d57ff: Etherboot ROM
(XEN) HVM1: e9000-e919c: SMBIOS tables
(XEN) HVM1: f0000-fffff: Main BIOS
I think rombios works fine if we drop the part of the patch.
>
> 2. It'd be nice to give E820_PHYSICAL_ADDRESS a definition in config.h and
> then use that instead of hardcoding the address throughout rombios.c.
>
I'll try it.
Best Regards,
Akio Takebe
prev parent reply other threads:[~2009-01-05 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-26 4:46 [Patch] Expand shadow memory area for using option ROM Akio Takebe
2008-12-29 14:27 ` Keir Fraser
2009-01-05 9:33 ` Akio Takebe [this message]
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=4961D3F6.20304@jp.fujitsu.com \
--to=takebe_akio@jp.fujitsu.com \
--cc=keir.fraser@eu.citrix.com \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.