From: "H. Peter Anvin" <hpa@zytor.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: matt@console-pimps.org, matt.fleming@intel.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: Sun, 07 Oct 2012 19:26:57 +0900 [thread overview]
Message-ID: <e0004a11-4caa-4100-8876-1e7346f50673@email.android.com> (raw)
In-Reply-To: <50714881020000780008D43E@nat28.tlf.novell.com>
Actually, no, because we may need to double-map in the low address space per discussion at LPC.
Jan Beulich <jbeulich@suse.com> wrote:
>>>> "H. Peter Anvin" <hpa@zytor.com> 10/05/12 6:28 PM >>>
>>On 10/04/2012 11:39 PM, Jan Beulich wrote:
>>>>
>>>> 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.
>>>
>>
>>The P <= V-2 limitation doesn't come from this, it comes from the fact
>
>>that we need to have the regular kernel 1:1 map and still have space
>for
>>the kernel, vmalloc, ioremap and so on in the kernel part of the
>address
>>space; in theory it *could* be some fraction between 1 and 2, but
>since
>>hardware doesn't do fractional bits very well the above is what we
>have
>>been telling the hardware folks. :)
>
>I understand all that, but here we're talking about a true 1:1 mapping
>(i.e. in the lower half of the virtual address space), as opposed to
>the
>direct mapping (in the upper half). We can obviously use all of the
>lower
>half for this purpose.
>
>Jan
--
Sent from my mobile phone. Please excuse brevity and lack of formatting.
next prev parent reply other threads:[~2012-10-07 10:27 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
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 [this message]
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=e0004a11-4caa-4100-8876-1e7346f50673@email.android.com \
--to=hpa@zytor.com \
--cc=jbeulich@suse.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=matt@console-pimps.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®