From: Randy Dunlap <rdunlap@infradead.org>
To: Hailong Liu <liuhailongg6@163.com>,
Catalin Marinas <catalin.marinas@arm.com>
Cc: Will Deacon <will@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Steven Price <steven.price@arm.com>,
Vincenzo Frascino <vincenzo.frascino@arm.com>,
Andrey Konovalov <andreyknvl@google.com>,
Mark Brown <broonie@kernel.org>,
Anshuman Khandual <anshuman.khandual@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Hailong Liu <liu.hailong6@zte.com.cn>
Subject: Re: [PATCH] arm64/ptdump:display the Linear Mapping start marker
Date: Tue, 2 Feb 2021 11:39:45 -0800 [thread overview]
Message-ID: <c032e6aa-7101-fb3c-09be-425d77877efe@infradead.org> (raw)
In-Reply-To: <20210202150749.10104-1-liuhailongg6@163.com>
On 2/2/21 7:07 AM, Hailong Liu wrote:
> From: Hailong Liu <liu.hailong6@zte.com.cn>
>
> The current /sys/kernel/debug/kernel_page_tables does not display the
> *Linear Mapping start* marker on arm64, which I think should be paired
> with the *Linear Mapping start* marker.
paired with itself? just asking...
>
> Since *Linear Mapping start* is the first marker, use level=-1 to display it.
>
> Signed-off-by: Hailong Liu <liu.hailong6@zte.com.cn>
> ---
> arch/arm64/mm/ptdump.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/arm64/mm/ptdump.c b/arch/arm64/mm/ptdump.c
> index 04137a8f3d2d..0e050d76b83a 100644
> --- a/arch/arm64/mm/ptdump.c
> +++ b/arch/arm64/mm/ptdump.c
> @@ -324,6 +324,7 @@ void ptdump_walk(struct seq_file *s, struct ptdump_info *info)
> st = (struct pg_state){
> .seq = s,
> .marker = info->markers,
> + .level = -1,
> .ptdump = {
> .note_page = note_page,
> .range = (struct ptdump_range[]){
>
--
~Randy
next prev parent reply other threads:[~2021-02-02 19:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-02 15:07 Hailong Liu
2021-02-02 19:39 ` Randy Dunlap [this message]
2021-02-03 14:13 ` Hailong Liu
2021-02-02 21:25 ` Will Deacon
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=c032e6aa-7101-fb3c-09be-425d77877efe@infradead.org \
--to=rdunlap@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=andreyknvl@google.com \
--cc=anshuman.khandual@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liu.hailong6@zte.com.cn \
--cc=liuhailongg6@163.com \
--cc=steven.price@arm.com \
--cc=vincenzo.frascino@arm.com \
--cc=will@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®