From: Ingo Molnar <mingo@kernel.org>
To: Matt Fleming <matt@codeblueprint.co.uk>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H . Peter Anvin" <hpa@zytor.com>, Toshi Kani <toshi.kani@hp.com>,
linux-kernel@vger.kernel.org, linux-efi@vger.kernel.org,
Borislav Petkov <bp@alien8.de>,
Sai Praneeth Prakhya <sai.praneeth.prakhya@intel.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Dave Jones <davej@codemonkey.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
Stephen Smalley <sds@tycho.nsa.gov>
Subject: Re: [PATCH 6/6] Documentation/x86: Update EFI memory region description
Date: Fri, 13 Nov 2015 10:22:10 +0100 [thread overview]
Message-ID: <20151113092210.GB19922@gmail.com> (raw)
In-Reply-To: <1447342823-3612-7-git-send-email-matt@codeblueprint.co.uk>
* Matt Fleming <matt@codeblueprint.co.uk> wrote:
> +We map EFI runtime services in the efi_pgd PGD in the virtual range of
> +64Gb (arbitrarily set, can be raised if needed). The mappings are not
> +part of any other kernel PGD and are only available during EFI runtime
> +calls.
Is that virtual address range 0-64Gb, i.e.:
0x00000000.00000000 - 0x00000010.00000000
or is it somewhere else?
Thanks,
Ingo
WARNING: multiple messages have this Message-ID (diff)
From: Ingo Molnar <mingo-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>
To: Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
Cc: Thomas Gleixner <tglx-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>,
"H . Peter Anvin" <hpa-YMNOUZJC4hwAvxtiuMwx3w@public.gmane.org>,
Toshi Kani <toshi.kani-VXdhtT5mjnY@public.gmane.org>,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-efi-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Borislav Petkov <bp-Gina5bIWoIWzQB+pC5nmwQ@public.gmane.org>,
Sai Praneeth Prakhya
<sai.praneeth.prakhya-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Linus Torvalds
<torvalds-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Dave Jones
<davej-rdkfGonbjUTCLXcRTR1eJlpr/1R2p/CL@public.gmane.org>,
Andrew Morton
<akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>,
Andy Lutomirski <luto-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org>,
Denys Vlasenko <dvlasenk-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>,
Stephen Smalley <sds-+05T5uksL2qpZYMLLGbcSA@public.gmane.org>
Subject: Re: [PATCH 6/6] Documentation/x86: Update EFI memory region description
Date: Fri, 13 Nov 2015 10:22:10 +0100 [thread overview]
Message-ID: <20151113092210.GB19922@gmail.com> (raw)
In-Reply-To: <1447342823-3612-7-git-send-email-matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org>
* Matt Fleming <matt-mF/unelCI9GS6iBeEJttW/XRex20P6io@public.gmane.org> wrote:
> +We map EFI runtime services in the efi_pgd PGD in the virtual range of
> +64Gb (arbitrarily set, can be raised if needed). The mappings are not
> +part of any other kernel PGD and are only available during EFI runtime
> +calls.
Is that virtual address range 0-64Gb, i.e.:
0x00000000.00000000 - 0x00000010.00000000
or is it somewhere else?
Thanks,
Ingo
next prev parent reply other threads:[~2015-11-13 9:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-12 15:40 [GIT PULL 0/6] EFI page table isolation Matt Fleming
2015-11-12 15:40 ` [PATCH 1/6] x86/mm/pageattr: Ensure cpa->pfn only contains page frame numbers Matt Fleming
2015-11-12 18:47 ` Borislav Petkov
2015-11-12 15:40 ` [PATCH 2/6] x86/mm/pageattr: Do not strip pte flags from cpa->pfn Matt Fleming
2015-11-12 18:47 ` Borislav Petkov
2015-11-12 18:47 ` Borislav Petkov
2015-11-12 19:28 ` Matt Fleming
2015-11-12 15:40 ` [PATCH 3/6] x86/efi: Map RAM into the identity page table for mixed mode Matt Fleming
2015-11-12 18:01 ` Borislav Petkov
2015-11-12 19:45 ` Matt Fleming
2015-11-12 15:40 ` [PATCH 4/6] x86/efi: Hoist page table switching code into efi_call_virt() Matt Fleming
2015-11-12 18:44 ` Borislav Petkov
2015-11-12 18:44 ` Borislav Petkov
2015-11-12 20:01 ` Matt Fleming
2015-11-13 7:59 ` Borislav Petkov
2015-11-13 7:59 ` Borislav Petkov
2015-11-13 16:19 ` Matt Fleming
2015-11-13 16:19 ` Matt Fleming
2015-11-12 18:47 ` Borislav Petkov
2015-11-12 18:47 ` Borislav Petkov
2015-11-12 20:15 ` Matt Fleming
2015-11-12 15:40 ` [PATCH 5/6] x86/efi: Build our own page table structures Matt Fleming
2015-11-12 15:40 ` Matt Fleming
2015-11-12 18:38 ` Borislav Petkov
2015-11-12 18:38 ` Borislav Petkov
2015-11-12 21:38 ` Matt Fleming
2015-11-12 21:38 ` Matt Fleming
2015-11-12 15:40 ` [PATCH 6/6] Documentation/x86: Update EFI memory region description Matt Fleming
2015-11-12 18:37 ` Borislav Petkov
2015-11-13 9:22 ` Ingo Molnar [this message]
2015-11-13 9:22 ` Ingo Molnar
2015-11-13 9:29 ` Matt Fleming
2015-11-13 16:42 ` Linus Torvalds
2015-11-13 16:42 ` Linus Torvalds
2015-11-13 22:22 ` Matt Fleming
2015-11-13 22:22 ` Matt Fleming
2015-11-18 8:18 ` Ingo Molnar
2015-11-18 8:18 ` Ingo Molnar
2015-11-19 11:22 ` 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=20151113092210.GB19922@gmail.com \
--to=mingo@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=davej@codemonkey.org.uk \
--cc=dvlasenk@redhat.com \
--cc=hpa@zytor.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=matt@codeblueprint.co.uk \
--cc=sai.praneeth.prakhya@intel.com \
--cc=sds@tycho.nsa.gov \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hp.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.