From: Barry Song <song.bao.hua@hisilicon.com>
To: <akpm@linux-foundation.org>, <jan.kiszka@siemens.com>,
<kbingham@kernel.org>
Cc: <corbet@lwn.net>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <linuxarm@openeuler.org>,
Barry Song <song.bao.hua@hisilicon.com>
Subject: [RESEND PATCH v2 0/2] scripts/gdb: clarify the platforms supporting lx_current and add arm64 support
Date: Mon, 15 Mar 2021 09:34:42 +1300 [thread overview]
Message-ID: <20210314203444.15188-1-song.bao.hua@hisilicon.com> (raw)
lx_current depends on per_cpu current_task variable which exists on x86 only.
so it actually works on x86 only. the 1st patch documents this clearly; the
2nd patch adds support for arm64.
-resend
resending to Andrew as Kieran Bingham explained patches of scripts/gdb
usually go through the tree of Andrew Morton;
Barry Song (2):
scripts/gdb: document lx_current is only supported by x86
scripts/gdb: add lx_current support for arm64
.../dev-tools/gdb-kernel-debugging.rst | 2 +-
scripts/gdb/linux/cpus.py | 23 +++++++++++++++++--
2 files changed, 22 insertions(+), 3 deletions(-)
--
2.25.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-03-14 20:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-14 20:34 Barry Song [this message]
2021-03-14 20:34 ` [RESEND PATCH v2 1/2] scripts/gdb: document lx_current is only supported by x86 Barry Song
2021-03-14 20:34 ` [RESEND PATCH v2 2/2] scripts/gdb: add lx_current support for arm64 Barry Song
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=20210314203444.15188-1-song.bao.hua@hisilicon.com \
--to=song.bao.hua@hisilicon.com \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@openeuler.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).