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>
Subject: Re: [PATCH 2/2] scripts/gdb/symbols: make lx-symbols skip the s390 decompressor
Date: Wed, 09 Jul 2025 16:37:40 +0200 [thread overview]
Message-ID: <6a2524c66c6462c94237058c8ab8aa43f2192c87.camel@linux.ibm.com> (raw)
In-Reply-To: <3a87aa8d-ce40-4909-be36-24c8ea75af8b@siemens.com>
On Wed, 2025-07-09 at 13:40 +0200, Jan Kiszka wrote:
> On 25.06.25 17:36, Ilya Leoshkevich wrote:
> > When one starts QEMU with the -S flag and attaches GDB, the kernel
> > is
> > not yet loaded, and the current instruction is an entry point to
> > the
> > decompressor. In case the intention is to debug the early kernel
> > boot,
> > and not the decompressor, e.g., put a breakpoint on some kernel
> > function and see all the invocations, one has to skip the
> > decompressor.
> >
> > There are many ways to do this, and so far people wrote private
> > scripts
> > or memorized certain command sequences.
> >
> > Make it work out of the box like this:
> >
> > $ gdb -ex 'target remote :6812' -ex 'source vmlinux-gdb.py'
> > vmlinux
> > Remote debugging using :6812
> > 0x0000000000010000 in ?? ()
> > (gdb) lx-symbols
> > loading vmlinux
> > (gdb) x/i $pc
> > => 0x3ffe0100000 <startup_continue>: lghi %r2,0
> >
> > Implement this by reading the address of the jump_to_kernel()
> > function
> > from the lowcore, and step until DAT is turned on.
>
> Why do you need to stepi until there? SW breakpoint will likely need
> to
> output of the decompressor first. No HW breakpoint available? Or
> missing
> <end-of-decompressor> address?
jump_to_kernel is <end-of-decompressor>; the code from this patch puts
an SW breakpoint there, and this works fine.
However, the problem is that once jump_to_kernel is reached, even
though the kernel is already in place, paging is still off.
jump_to_kernel contains a single "lpswe" instruction, which both jumps
to kernel and enables paging, therefore, we must "stepi" over it. The
loop is there just for future-proofing. Everything happens very
quickly, there are no thousands of "stepi"s.
> > Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> > ---
> > scripts/gdb/linux/symbols.py | 26 ++++++++++++++++++++++++++
> > 1 file changed, 26 insertions(+)
> >
> > diff --git a/scripts/gdb/linux/symbols.py
> > b/scripts/gdb/linux/symbols.py
> > index 2332bd8eddf1..6edb99221675 100644
> > --- a/scripts/gdb/linux/symbols.py
> > +++ b/scripts/gdb/linux/symbols.py
> > @@ -84,6 +84,30 @@ def get_kerneloffset():
> > return None
> >
> >
> > +def is_in_s390_decompressor():
> > + # DAT is always off in decompressor. Use this as an indicator.
> > + # Note that in the kernel, DAT can be off during kexec() or
> > restart.
> > + # Accept this imprecision in order to avoid complicating
> > things.
> > + # It is unlikely that someone will run lx-symbols at these
> > points.
> > + pswm = int(gdb.parse_and_eval("$pswm"))
> > + return (pswm & 0x0400000000000000) == 0
> > +
> > +
> > +def skip_decompressor():
> > + if utils.is_target_arch("s390"):
> > + if is_in_s390_decompressor():
> > + # The address of the jump_to_kernel function is
> > statically placed
> > + # into svc_old_psw.addr (see ipl_data.c); read it from
> > there. DAT
> > + # is off, so we do not need to care about lowcore
> > relocation.
> > + svc_old_pswa = 0x148
> > + jump_to_kernel = int(gdb.parse_and_eval("*(unsigned
> > long long *)" +
> > +
> > hex(svc_old_pswa)))
> > + gdb.execute("tbreak *" + hex(jump_to_kernel))
> > + gdb.execute("continue")
> > + while is_in_s390_decompressor():
> > + gdb.execute("stepi")
> > +
> > +
> > class LxSymbols(gdb.Command):
> > """(Re-)load symbols of Linux kernel and currently loaded
> > modules.
> >
> > @@ -204,6 +228,8 @@ lx-symbols command."""
> > saved_state['breakpoint'].enabled =
> > saved_state['enabled']
> >
> > def invoke(self, arg, from_tty):
> > + skip_decompressor()
> > +
> > self.module_paths =
> > [os.path.abspath(os.path.expanduser(p))
> > for p in arg.split()]
> > self.module_paths.append(os.getcwd())
>
> Otherwise, this series looks good to me and could be picked up if
> there
> is no better way to reach the end of the decompressor.
Could you please ack this patch if the explanation above is
satisfactory? We would like to take this series via the s390 tree,
if possible.
> Jan
next prev parent reply other threads:[~2025-07-09 14:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-25 15:36 [PATCH 0/2] scripts/gdb/symbols: make lx-symbols skip the s390 decompressor Ilya Leoshkevich
2025-06-25 15:36 ` [PATCH 1/2] s390/boot: Introduce jump_to_kernel() function Ilya Leoshkevich
2025-06-25 15:36 ` [PATCH 2/2] scripts/gdb/symbols: make lx-symbols skip the s390 decompressor Ilya Leoshkevich
2025-07-09 11:40 ` Jan Kiszka
2025-07-09 14:37 ` Ilya Leoshkevich [this message]
2025-07-09 15:45 ` Jan Kiszka
2025-06-30 15:32 ` [PATCH 0/2] " Alexander Gordeev
2025-07-09 9:27 ` [PATCH PING " Ilya Leoshkevich
2025-07-10 5:46 ` [PATCH " Alexander Gordeev
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=6a2524c66c6462c94237058c8ab8aa43f2192c87.camel@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;
as well as URLs for NNTP newsgroup(s).