From: Matt Fleming <matt@console-pimps.org>
To: Jan Beulich <JBeulich@suse.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
mingo@kernel.org, x86@kernel.org, mjg@redhat.com,
linux-efi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] x86, mm: Include the entire kernel memory map in trampoline_pgd
Date: Fri, 05 Oct 2012 07:48:00 +0100 [thread overview]
Message-ID: <1349419680.15966.32.camel@mfleming-mobl1.ger.corp.intel.com> (raw)
In-Reply-To: <506E9CDC020000780009FD13@nat28.tlf.novell.com>
On Fri, 2012-10-05 at 07:39 +0100, Jan Beulich wrote:
> >>> On 04.10.12 at 23:08, "H. Peter Anvin" <hpa@zytor.com> wrote:
> > On 10/03/2012 06:31 AM, Jan Beulich wrote:
> >>>>> Matt Fleming <matt@console-pimps.org> 10/03/12 2:59 PM >>>
> >>> +static int insert_identity_mapping(resource_size_t paddr, unsigned long
> > vaddr,
> >>> + unsigned long size)
> >>> +{
> >>> + unsigned long end = vaddr + size;
> >>> + unsigned long next;
> >>> + pgd_t *vpgd, *ppgd;
> >>> +
> >>> +#ifdef CONFIG_X86_32
> >>> + ppgd = initial_page_table + pgd_index(paddr);
> >>> +
> >>> + if (paddr >= PAGE_OFFSET || paddr + size > PAGE_OFFSET)
> >>> + return 1;
> >>> +#else
> >>> + ppgd = __va(real_mode_header->trampoline_pgd) + pgd_index(paddr);
> >>
> >> Missing equivalent code (to the 32-bit one above) here - after all, you're
> > trying
> >> to potentially insert a 52-bit physical address into 48-bit virtual space.
> >>
> >
> > We should have the check, but at least for Linux support we require
> > P <= V-2.
>
> Not really imo - P <= V - 1 should be sufficient here, as all that is
> necessary is that the result represents a 1:1 mapping. Specifically,
> there's no constraint to the virtual space limitation of the direct
> mapping of RAM.
Just to be clear, I was going to add this check,
/* Don't map over the guard hole. */
if (paddr >= 0x7fffffffffff || paddr + size > 0x7fffffffffff)
return 1;
Since I'm guessing mapping over the guard hole would be bad.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2012-10-05 6:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-03 12:59 [PATCH 0/3] x86/efi: Identity mapping pagetable Matt Fleming
2012-10-03 12:59 ` [PATCH 1/3] x86, mm: Include the entire kernel memory map in trampoline_pgd Matt Fleming
2012-10-03 13:31 ` Jan Beulich
2012-10-03 14:03 ` Matt Fleming
2012-10-04 6:32 ` Jan Beulich
2012-10-04 9:18 ` Matt Fleming
2012-10-04 10:01 ` Jan Beulich
2012-10-10 10:45 ` Matt Fleming
2012-10-15 7:22 ` Jan Beulich
2012-10-04 21:08 ` H. Peter Anvin
2012-10-05 6:39 ` Jan Beulich
2012-10-05 6:48 ` Matt Fleming [this message]
2012-10-05 8:19 ` Jan Beulich
2012-10-05 16:28 ` H. Peter Anvin
2012-10-07 8:16 ` Jan Beulich
2012-10-07 10:26 ` H. Peter Anvin
2012-10-08 6:43 ` Jan Beulich
2012-10-03 12:59 ` [PATCH 2/3] x86, efi: 1:1 pagetable mapping for virtual EFI calls Matt Fleming
2012-10-03 12:59 ` [PATCH 3/3] x86/kernel: remove tboot 1:1 page table creation code Matt Fleming
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=1349419680.15966.32.camel@mfleming-mobl1.ger.corp.intel.com \
--to=matt@console-pimps.org \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=mjg@redhat.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®