From: Illia Ostapyshyn <illia@yshyn.com>
To: linux-kernel@vger.kernel.org, workflows@vger.kernel.org,
linux-doc@vger.kernel.org
Cc: Jan Kiszka <jan.kiszka@siemens.com>,
Kieran Bingham <kbingham@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Florian Rommel <mail@florommel.de>,
Jonathan Corbet <corbet@lwn.net>, Alex Shi <alexs@kernel.org>,
Yanteng Si <si.yanteng@linux.dev>,
Dongliang Mu <dzm91@hust.edu.cn>,
Hu Haowen <2023002089@link.tyut.edu.cn>,
Brendan Jackman <jackmanb@google.com>,
Illia Ostapyshyn <illia@yshyn.com>
Subject: [PATCH 0/2] scripts/gdb: Fixes related to lx_per_cpu()
Date: Sat, 3 May 2025 14:32:30 +0200 [thread overview]
Message-ID: <20250503123234.2407184-1-illia@yshyn.com> (raw)
Hi all,
these patches (1) fix kgdb detection on systems featuring a single CPU and
(2) update the documentation to reflect the current usage of lx_per_cpu()
and update an outdated example of its usage.
Illia Ostapyshyn (2):
scripts/gdb: Fix kgdb probing on single-core systems
scripts/gdb: Update documentation for lx_per_cpu
.../debugging/gdb-kernel-debugging.rst | 34 ++++++++-----------
.../zh_CN/dev-tools/gdb-kernel-debugging.rst | 34 ++++++++-----------
.../zh_TW/dev-tools/gdb-kernel-debugging.rst | 34 ++++++++-----------
scripts/gdb/linux/cpus.py | 4 +--
scripts/gdb/linux/utils.py | 2 +-
5 files changed, 48 insertions(+), 60 deletions(-)
base-commit: 95d3481af6dc90fd7175a7643fd108cdcb808ce5
--
2.47.2
next reply other threads:[~2025-05-03 12:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-03 12:32 Illia Ostapyshyn [this message]
2025-05-03 12:32 ` [PATCH 1/2] scripts/gdb: Fix kgdb probing on single-core systems Illia Ostapyshyn
2025-05-03 12:32 ` [PATCH 2/2] scripts/gdb: Update documentation for lx_per_cpu Illia Ostapyshyn
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=20250503123234.2407184-1-illia@yshyn.com \
--to=illia@yshyn.com \
--cc=2023002089@link.tyut.edu.cn \
--cc=akpm@linux-foundation.org \
--cc=alexs@kernel.org \
--cc=corbet@lwn.net \
--cc=dzm91@hust.edu.cn \
--cc=jackmanb@google.com \
--cc=jan.kiszka@siemens.com \
--cc=kbingham@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mail@florommel.de \
--cc=si.yanteng@linux.dev \
--cc=workflows@vger.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