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,
Baoquan He <bhe@redhat.com>
Subject: [PATCH 0/3] x86/mm/doc: Clean up mm.txt
Date: Fri, 21 Sep 2018 10:05:47 +0800 [thread overview]
Message-ID: <20180921020550.13095-1-bhe@redhat.com> (raw)
This clean up is suggested by Ingo.
It firstly fix the confusions in mm layout tables by unifying
each memory region description in the consistent style.
Secondly take the KASLR words out of the mm layout tables to make
it as a separate section to only list mm layout in non-KASLR case.
Then add KASLR document at the end of mm.txt.
Meanwhile update document about KERNEL_IMAGE_SIZE in
arch/x86/include/asm/page_64_types.h .
Baoquan He (3):
x86/KASLR: Update document about KERNEL_IMAGE_SIZE
x86/mm/doc: Clean up the memory region layout descriptions
x86/doc/kaslr.txt: Create a separate part of document abourt KASLR at
the end of file
Documentation/x86/x86_64/mm.txt | 138 +++++++++++++++++++++++------------
arch/x86/include/asm/page_64_types.h | 7 +-
2 files changed, 96 insertions(+), 49 deletions(-)
--
2.13.6
next reply other threads:[~2018-09-21 2:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 2:05 Baoquan He [this message]
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
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
2018-10-06 8:43 Baoquan He
2018-10-06 11:28 ` Baoquan He
2018-10-06 12:21 ` Ingo Molnar
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=20180921020550.13095-1-bhe@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).