All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
Cc: jan.kiszka@siemens.com, kbingham@kernel.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: Fri, 30 Dec 2022 13:37:26 -0800	[thread overview]
Message-ID: <20221230133726.4c2e7e148a8a6627cd621e0f@linux-foundation.org> (raw)
In-Reply-To: <20221230163512.23736-1-dmitrii.bundin.a@gmail.com>

On Fri, 30 Dec 2022 19:35:12 +0300 Dmitrii Bundin <dmitrii.bundin.a@gmail.com> wrote:

> This command provides a way to traverse the entire page hierarchy by a
> given virtual address. In addition to qemu's commands info tlb/info mem
> it provides the complete information about the paging structure for an
> arbitrary virtual address. It supports 4Kb/2MB/1GB and 5 level paging.

Seems neat.  Should it have a check that it's being run on the supported
architecture?  Or do we just rely on non-x86_64 users learning not to
do that.

  parent reply	other threads:[~2022-12-30 21:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30 16:35 [PATCH] scripts/gdb: add mm introspection utils Dmitrii Bundin
2022-12-30 20:06 ` Mike Rapoport
2022-12-31 17:14   ` Dmitrii Bundin
2023-01-01  7:51     ` Mike Rapoport
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 ` Andrew Morton [this message]
2022-12-31 17:26   ` [PATCH] " 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=20221230133726.4c2e7e148a8a6627cd621e0f@linux-foundation.org \
    --to=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 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.