From: "Lendacky, Thomas" <Thomas.Lendacky@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"x86@kernel.org" <x86@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>,
Dave Hansen <dave.hansen@linux.intel.com>,
Andy Lutomirski <luto@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Baoquan He <bhe@redhat.com>, Lianbo Jiang <lijiang@redhat.com>
Subject: Re: [PATCH v2 1/2] x86/mm: Identify the end of the kernel area to be reserved
Date: Tue, 18 Jun 2019 01:43:00 +0000 [thread overview]
Message-ID: <7a35c79d-370e-5595-234e-0aafc527331b@amd.com> (raw)
In-Reply-To: <20190617104740.GG27127@zn.tnic>
On 6/17/19 5:47 AM, Borislav Petkov wrote:
> On Fri, Jun 14, 2019 at 09:15:18PM +0000, Lendacky, Thomas wrote:
>> The memory occupied by the kernel is reserved using memblock_reserve()
>> in setup_arch(). Currently, the area is from symbols _text to __bss_stop.
>> Everything after __bss_stop must be specifically reserved otherwise it
>> is discarded. This is not clearly documented.
>
> Hmm, so I see this in arch/x86/kernel/vmlinux.lds.S after _end:
>
> _end = .;
>
> STABS_DEBUG
> DWARF_DEBUG
>
> /* Sections to be discarded */
> DISCARDS
> /DISCARD/ : {
> *(.eh_frame)
> }
>
> and over DISCARDS:
>
> /*
> * Default discarded sections.
> *
> * Some archs want to discard exit text/data at runtime rather than
> * link time due to cross-section references such as alt instructions,
> * bug table, eh_frame, etc. DISCARDS must be the last of output
> * section definitions so that such archs put those in earlier section
> * definitions.
> */
> #define DISCARDS
>
> That sounds like it is documented to me, or do you mean something else?
Yes and no... it doesn't say how it is done, namely through the use of
memblock_reserve() calls and when and where those occur.
>
>> Add a new symbol, __end_of_kernel_reserve, that more readily identifies
>> what is reserved, along with comments that indicate what is reserved,
>> what is discarded and what needs to be done to prevent a section from
>> being discarded.
>>
>> Cc: Baoquan He <bhe@redhat.com>
>> Cc: Lianbo Jiang <lijiang@redhat.com>
>> Signed-off-by: Tom Lendacky <thomas.lendacky@amd.com>
>> ---
>> arch/x86/include/asm/sections.h | 2 ++
>> arch/x86/kernel/setup.c | 8 +++++++-
>> arch/x86/kernel/vmlinux.lds.S | 9 ++++++++-
>> 3 files changed, 17 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/include/asm/sections.h b/arch/x86/include/asm/sections.h
>> index 8ea1cfdbeabc..71b32f2570ab 100644
>> --- a/arch/x86/include/asm/sections.h
>> +++ b/arch/x86/include/asm/sections.h
>> @@ -13,4 +13,6 @@ extern char __end_rodata_aligned[];
>> extern char __end_rodata_hpage_align[];
>> #endif
>>
>> +extern char __end_of_kernel_reserve[];
>> +
>> #endif /* _ASM_X86_SECTIONS_H */
>> diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
>> index 08a5f4a131f5..32eb70625b3b 100644
>> --- a/arch/x86/kernel/setup.c
>> +++ b/arch/x86/kernel/setup.c
>> @@ -827,8 +827,14 @@ dump_kernel_offset(struct notifier_block *self, unsigned long v, void *p)
>>
>> void __init setup_arch(char **cmdline_p)
>> {
>> + /*
>> + * Reserve the memory occupied by the kernel between _text and
>> + * __end_of_kernel_reserve symbols. Any kernel sections after the
>> + * __end_of_kernel_reserve symbol must be explicity reserved with a
>> + * separate memblock_reserve() or it will be discarded.
>
> s/it/they/
>
>> + */
>> memblock_reserve(__pa_symbol(_text),
>> - (unsigned long)__bss_stop - (unsigned long)_text);
>> + (unsigned long)__end_of_kernel_reserve - (unsigned long)_text);
>>
>> /*
>> * Make sure page 0 is always reserved because on systems with
>> diff --git a/arch/x86/kernel/vmlinux.lds.S b/arch/x86/kernel/vmlinux.lds.S
>> index 0850b5149345..ca2252ca6ad7 100644
>> --- a/arch/x86/kernel/vmlinux.lds.S
>> +++ b/arch/x86/kernel/vmlinux.lds.S
>> @@ -368,6 +368,14 @@ SECTIONS
>> __bss_stop = .;
>> }
>>
>> + /*
>> + * The memory occupied from _text to here, __end_of_kernel_reserve, is
>> + * automatically reserved in setup_arch(). Anything after here must be
>> + * explicitly reserved using memblock_reserve() or it will be discarded
>> + * and treated as available memory.
>> + */
>> + __end_of_kernel_reserve = .;
>> +
>> . = ALIGN(PAGE_SIZE);
>> .brk : AT(ADDR(.brk) - LOAD_OFFSET) {
>> __brk_base = .;
>> @@ -382,7 +390,6 @@ SECTIONS
>> STABS_DEBUG
>> DWARF_DEBUG
>>
>> - /* Sections to be discarded */
>
> Huh?
>
> They're called DISCARD* ...
The comment above is more explicit about what will be discarded and
how not to have it discarded, so I removed this comment.
Thanks,
Tom
>
>> DISCARDS
>> /DISCARD/ : {
>> *(.eh_frame)
>
next prev parent reply other threads:[~2019-06-18 1:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-14 21:15 [PATCH 0/2] x86: SME: Kexec/kdump memory loading fix Lendacky, Thomas
2019-06-14 21:15 ` [PATCH v2 1/2] x86/mm: Identify the end of the kernel area to be reserved Lendacky, Thomas
2019-06-14 22:06 ` Dave Hansen
2019-06-16 12:03 ` lijiang
2019-06-17 1:54 ` Baoquan He
2019-06-17 10:47 ` Borislav Petkov
2019-06-18 1:43 ` Lendacky, Thomas [this message]
2019-06-18 9:37 ` Borislav Petkov
2019-06-14 21:15 ` [PATCH v2 2/2] x86/mm: Create an SME workarea in the kernel for early encryption Lendacky, Thomas
2019-06-17 11:02 ` Borislav Petkov
2019-06-18 1:49 ` Lendacky, Thomas
2019-06-18 10:11 ` Borislav Petkov
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=7a35c79d-370e-5595-234e-0aafc527331b@amd.com \
--to=thomas.lendacky@amd.com \
--cc=bhe@redhat.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=lijiang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--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®