From: Dmitrii Bundin <dmitrii.bundin.a@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
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,
Mike Rapoport <rppt@kernel.org>
Subject: Re: [PATCH] scripts/gdb: add mm introspection utils
Date: Sat, 31 Dec 2022 20:26:17 +0300 [thread overview]
Message-ID: <CANXV_XwqgEZ5qhP-A1YNOuP7wri5Ax=1yj1CV2BwOFQMyr+hBQ@mail.gmail.com> (raw)
In-Reply-To: <20221230133726.4c2e7e148a8a6627cd621e0f@linux-foundation.org>
On Sat, Dec 31, 2022 at 12:37 AM Andrew Morton
<akpm@linux-foundation.org> wrote:
> Should it have a check that it's being run on the supported
> architecture?
The x86 code is under the if utils.is_target_arch("x86") ... else
gdb.GdbError("Virtual address translation is not supported for this
arch") check so for now it will be an error to use this command for
other archs. In the patch v2 I mentioned x86 explicitly in the commit
message and also addressed issues Mike pointed out. Could you please
apply https://lore.kernel.org/all/20221231171258.7907-1-dmitrii.bundin.a@gmail.com/
in place of v1?
next prev parent reply other threads:[~2022-12-31 17:26 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 ` [PATCH] " Andrew Morton
2022-12-31 17:26 ` Dmitrii Bundin [this message]
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='CANXV_XwqgEZ5qhP-A1YNOuP7wri5Ax=1yj1CV2BwOFQMyr+hBQ@mail.gmail.com' \
--to=dmitrii.bundin.a@gmail.com \
--cc=akpm@linux-foundation.org \
--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=rppt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).