From: Mike Rapoport <rppt@kernel.org>
To: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Cc: jan.kiszka@siemens.com, kbingham@kernel.org,
akpm@linux-foundation.org, gregkh@linuxfoundation.org,
mingo@redhat.com, x86@kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, vbabka@suse.cz
Subject: Re: [PATCH] scripts/gdb: add mm introspection utils
Date: Sun, 1 Jan 2023 09:51:24 +0200 [thread overview]
Message-ID: <Y7E7fEBm6p0Q2djI@kernel.org> (raw)
In-Reply-To: <CANXV_XzMVGHy5SP-2=QyO6YvpZAzLU4ZwFL3b8KOucr9rwkzhg@mail.gmail.com>
On Sat, Dec 31, 2022 at 08:14:30PM +0300, Dmitrii Bundin wrote:
> On Fri, Dec 30, 2022 at 11:07 PM Mike Rapoport <rppt@kernel.org> wrote:
> >
> > The commit message does not mention it's x86-specific.
> > Not sure how gdb scripts handle per-arch functionality, but at the very
> > least this should be stated in the commit message.
> >
> Thanks for pointing this out. Will fix it. I put the command's code
> under the if utils.is_target_arch("x86") ... else
> gdb.GdbError("Virtual address translation is not supported for this
> arch") as it's done in other scripts and have plans to implement the
> same functionality for ARM in the foreseeable future.
>
> > Any particular reason to make it ALL CAPS?
> Actually, no. Do you propose to reformat the output with a lower case?
I like lower case more :)
I'd also put the bit number first and would align the columns, e.g
something like:
bit 0: entry present : true
bit 1: read/write access allowed : true
bit 2: user access allowed : true
bit 3: page level write through : false
bit 4: page level cache disabled : false
bit 5: entry has been accessed : true
bit 7: page size : false
bit 11: restart to ordinary : false
bit 63: execute disable : true
--
Sincerely yours,
Mike.
next prev parent reply other threads:[~2023-01-01 7:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 16:35 Dmitrii Bundin
2022-12-30 20:06 ` Mike Rapoport
2022-12-31 17:14 ` Dmitrii Bundin
2023-01-01 7:51 ` Mike Rapoport [this message]
2023-01-01 17:23 ` [PATCH v3] " Dmitrii Bundin
2023-01-02 8:59 ` Jan Kiszka
2023-01-02 17:10 ` [PATCH v4] " Dmitrii Bundin
2023-01-02 18:28 ` Mike Rapoport
2023-01-12 20:16 ` Greg KH
2023-01-13 17:51 ` [PATCH v5] " Dmitrii Bundin
2023-01-14 4:03 ` Andrew Morton
2022-12-30 21:37 ` [PATCH] " Andrew Morton
2022-12-31 17:26 ` Dmitrii Bundin
2022-12-31 17:12 ` [PATCH v2] " Dmitrii Bundin
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=Y7E7fEBm6p0Q2djI@kernel.org \
--to=rppt@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=dmitrii.bundin.a@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@redhat.com \
--cc=vbabka@suse.cz \
--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