mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ilya Leoshkevich <iii@linux.ibm.com>
To: Jan Kiszka <jan.kiszka@siemens.com>,
	Kieran Bingham <kbingham@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, Heiko Carstens <hca@linux.ibm.com>,
	Vasily Gorbik <gor@linux.ibm.com>,
	Alexander Gordeev <agordeev@linux.ibm.com>,
	Ilya Leoshkevich <iii@linux.ibm.com>
Subject: [PATCH 0/3] scripts/gdb/symbols: determine KASLR offset on s390 during early boot
Date: Thu, 15 May 2025 17:52:10 +0200	[thread overview]
Message-ID: <20250515155811.114392-1-iii@linux.ibm.com> (raw)

Hi,

I noticed that debugging s390 early boot using the support I introduced
in commit 28939c3e9925 ("scripts/gdb/symbols: determine KASLR offset on
s390") does not work.

The reason is that decompressor does not provide the vmcoreinfo note,
so KASLR offset needs to be extracted in a different way, which this
series implements. Patches 1-2 are trivial refactorings, and patch 3 is
the implementation.

Best regards,
Ilya

Ilya Leoshkevich (3):
  scripts/gdb/symbols: factor out get_vmlinux()
  scripts/gdb/symbols: factor out pagination_off()
  scripts/gdb/symbols: determine KASLR offset on s390 during early boot

 scripts/gdb/linux/symbols.py | 38 +++++++++++++++++++-----------------
 scripts/gdb/linux/utils.py   | 20 +++++++++++++++++++
 2 files changed, 40 insertions(+), 18 deletions(-)

-- 
2.49.0


             reply	other threads:[~2025-05-15 15:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-15 15:52 Ilya Leoshkevich [this message]
2025-05-15 15:52 ` [PATCH 1/3] scripts/gdb/symbols: factor out get_vmlinux() Ilya Leoshkevich
2025-05-15 15:52 ` [PATCH 2/3] scripts/gdb/symbols: factor out pagination_off() Ilya Leoshkevich
2025-05-15 15:52 ` [PATCH 3/3] scripts/gdb/symbols: determine KASLR offset on s390 during early boot Ilya Leoshkevich

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=20250515155811.114392-1-iii@linux.ibm.com \
    --to=iii@linux.ibm.com \
    --cc=agordeev@linux.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=gor@linux.ibm.com \
    --cc=hca@linux.ibm.com \
    --cc=jan.kiszka@siemens.com \
    --cc=kbingham@kernel.org \
    --cc=linux-kernel@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
all inboxes | Powered by JetHome®