From: Jon Mason <jdmason@us.ibm.com>
To: xen-devel@lists.xensource.com
Subject: Re: [Xen-changelog] x86/64 e820-parse-and-map code should skip low 1GB now as that
Date: Thu, 20 Apr 2006 17:56:08 -0500 [thread overview]
Message-ID: <20060420225608.GG23538@us.ibm.com> (raw)
In-Reply-To: <E1FWdVv-0000AT-7L@xenbits.xensource.com>
On Thu, Apr 20, 2006 at 06:04:22PM +0000, Xen patchbot -3.0-testing wrote:
> # HG changeset patch
> # User kaf24@firebug.cl.cam.ac.uk
> # Node ID fc7a39016601e9dd3161b91b294df1e9674ab383
> # Parent d3db967d299a9193972a1e466e9a090358d1ec26
> x86/64 e820-parse-and-map code should skip low 1GB now as that
> is mapped by the boot code.
>
> Signed-off-by: Keir Fraser <keir@xensource.com>
>
> diff -r d3db967d299a -r fc7a39016601 xen/arch/x86/setup.c
> --- a/xen/arch/x86/setup.c Thu Apr 20 17:10:51 2006 +0100
> +++ b/xen/arch/x86/setup.c Thu Apr 20 17:11:12 2006 +0100
> @@ -321,7 +321,7 @@ void __init __start_xen(multiboot_info_t
> #if defined (CONFIG_X86_64)
> /*
> * x86/64 maps all registered RAM. Points to note:
> - * 1. The initial pagetable already maps low 64MB, so skip that.
> + * 1. The initial pagetable already maps low 1GB, so skip that.
> * 2. We must map *only* RAM areas, taking care to avoid I/O holes.
> * Failure to do this can cause coherency problems and deadlocks
> * due to cache-attribute mismatches (e.g., AMD/AGP Linux bug).
> @@ -329,13 +329,14 @@ void __init __start_xen(multiboot_info_t
> {
> /* Calculate page-frame range, discarding partial frames. */
> unsigned long start, end;
> + unsigned long init_mapped = 1UL << (30 - PAGE_SHIFT); /* 1GB */
> start = PFN_UP(e820.map[i].addr);
> end = PFN_DOWN(e820.map[i].addr + e820.map[i].size);
> /* Clip the range to above 64MB. */
The aboove comment should be killed too.
Thanks,
Jon
> - if ( end < (64UL << (20-PAGE_SHIFT)) )
> + if ( end < init_mapped )
> continue;
> - if ( start < (64UL << (20-PAGE_SHIFT)) )
> - start = 64UL << (20-PAGE_SHIFT);
> + if ( start < init_mapped )
> + start = init_mapped;
> /* Request the mapping. */
> map_pages_to_xen(
> PAGE_OFFSET + (start << PAGE_SHIFT),
>
> _______________________________________________
> Xen-changelog mailing list
> Xen-changelog@lists.xensource.com
> http://lists.xensource.com/xen-changelog
parent reply other threads:[~2006-04-20 22:56 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <E1FWdVv-0000AT-7L@xenbits.xensource.com>]
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=20060420225608.GG23538@us.ibm.com \
--to=jdmason@us.ibm.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.