From: Baoquan He <bhe@redhat.com>
To: mingo@kernel.org, tglx@linutronix.de, hpa@zytor.com
Cc: linux-kernel@vger.kernel.org, kirill.shutemov@linux.intel.com,
x86@kernel.org, thgarnie@google.com, corbet@lwn.net,
linux-doc@vger.kernel.org, peterz@infradead.org
Subject: Re: [PATCH 3/3] x86/doc/kaslr.txt: Create a separate part of document abourt KASLR at the end of file
Date: Fri, 21 Sep 2018 11:19:27 +0800 [thread overview]
Message-ID: <20180921031927.GS2555@MiWiFi-R3L-srv> (raw)
In-Reply-To: <20180921020550.13095-4-bhe@redhat.com>
On 09/21/18 at 10:05am, Baoquan He wrote:
> +Name Starting address Size Aligned
> +-----------------------------------------------------------------------------------------------
> +direct mapping page_offset_base [actual size of system RAM + 10 TB padding] 1 GB
> +*guard hole random random 1 GB
> +vmalloc vmalloc_base 32 TB 1 GB
> +*guard hole random random 1 GB
> +vmemmap vmemmap_base 1 TB 1 GB
> +*guard hole random random 1 GB
OK, seems tab is uncontrollable, I will use space instead.
next prev parent reply other threads:[~2018-09-21 3:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 2:05 [PATCH 0/3] x86/mm/doc: Clean up mm.txt Baoquan He
2018-09-21 2:05 ` [PATCH 1/3] x86/KASLR: Update document about KERNEL_IMAGE_SIZE Baoquan He
2018-09-21 2:05 ` [PATCH 2/3] x86/mm/doc: Clean up the memory region layout descriptions Baoquan He
2018-09-21 2:05 ` [PATCH 3/3] x86/doc/kaslr.txt: Create a separate part of document abourt KASLR at the end of file Baoquan He
2018-09-21 3:19 ` Baoquan He [this message]
2018-09-21 3:21 ` [PATCH v2 " Baoquan He
2018-09-21 5:23 ` Baoquan He
2018-09-21 5:29 ` [PATCH v3 " Baoquan He
2018-09-27 0:02 ` [PATCH 0/3] x86/mm/doc: Clean up mm.txt Baoquan He
-- strict thread matches above, loose matches on Subject: below --
2018-10-06 8:43 Baoquan He
2018-10-06 8:43 ` [PATCH 3/3] x86/doc/kaslr.txt: Create a separate part of document abourt KASLR at the end of file Baoquan He
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=20180921031927.GS2555@MiWiFi-R3L-srv \
--to=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=hpa@zytor.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thgarnie@google.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 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.