From: Stephen Brennan <stephen.s.brennan@oracle.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Baoquan He <bhe@redhat.com>,
linux-kernel@vger.kernel.org, kexec@lists.infradead.org,
Nick Desaulniers <ndesaulniers@google.com>,
Dave Young <dyoung@redhat.com>, Kees Cook <keescook@chromium.org>,
Jiri Olsa <jolsa@kernel.org>, Stephen Boyd <swboyd@chromium.org>,
Bixuan Cui <cuibixuan@huawei.com>,
David Vernet <void@manifault.com>,
Vivek Goyal <vgoyal@redhat.com>,
Sami Tolvanen <samitolvanen@google.com>
Subject: Re: [PATCH 0/2] Expose kallsyms data in vmcoreinfo note
Date: Mon, 13 Jun 2022 15:33:19 -0700 [thread overview]
Message-ID: <87bkuwry6o.fsf@oracle.com> (raw)
In-Reply-To: <20220613151422.e2173f14909b9149fec8e0a6@linux-foundation.org>
Andrew Morton <akpm@linux-foundation.org> writes:
> On Mon, 13 Jun 2022 14:59:44 -0700 Stephen Brennan <stephen.s.brennan@oracle.com> wrote:
>> >> Related discussion around the BTF side of this:
>> >> https://lore.kernel.org/bpf/586a6288-704a-f7a7-b256-e18a675927df@oracle.com/T/#u
>> >>
>> >> Some work-in-progress branches using this feature:
>> >> https://github.com/brenns10/dwarves/tree/remove_percpu_restriction_1
>> >> https://github.com/brenns10/drgn/tree/kallsyms_plus_btf
>> >
>> > What's the story on using gdb with this?
>>
>> There is no story with GDB as of yet. I was already familiar with the
>> code of drgn when I started down this path, so that's what I used. Drgn
>> happens to have a very extensible type system which made it quite simple
>> to do. I'd love to see support for doing this with GDB, and might look
>> into the feasibility of it, but it's not on my roadmap right now.
>
> Naive question - could some standalone tool take this kallsyms-based
> info, combine it with a core image and create a minimally-dwarfified
> file which any debugger can munch on?
I'm not too familiar with the guts of DWARF, so honestly my guess may
not be any better than yours.
One thing that strikes me is that DWARF is typically included in an ELF
section, whereas x86_64 kernels are typically a bzImage, so I'm not
entirely sure how you'd get back an ELF file suitable to stick the DWARF
into. And from there, I really have no guess about the DWARF.
I will say that Compact Type Format (CTF) [1] is rather similar to BTF
in scope, and it already has support in the GNU Binutils. I'd imagine
that there's much more of a fighting chance of converting BTF to CTF and
getting GDB to use that instead.
[1] https://lwn.net/Articles/795384/
Stephen
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
prev parent reply other threads:[~2022-06-13 22:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 0:05 [PATCH 0/2] Expose kallsyms data in vmcoreinfo note Stephen Brennan
2022-05-17 0:05 ` [PATCH 1/2] kallsyms: Move declarations to internal header Stephen Brennan
2022-05-17 0:05 ` [PATCH 2/2] vmcoreinfo: Include kallsyms symbols Stephen Brennan
2022-05-18 10:19 ` [PATCH 0/2] Expose kallsyms data in vmcoreinfo note Baoquan He
2022-05-23 18:00 ` Stephen Brennan
2022-05-25 2:39 ` Baoquan He
2022-06-13 20:39 ` Stephen Brennan
2022-06-13 21:26 ` Andrew Morton
2022-06-13 21:59 ` Stephen Brennan
2022-06-13 22:14 ` Andrew Morton
2022-06-13 22:33 ` Stephen Brennan [this message]
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=87bkuwry6o.fsf@oracle.com \
--to=stephen.s.brennan@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=cuibixuan@huawei.com \
--cc=dyoung@redhat.com \
--cc=jolsa@kernel.org \
--cc=keescook@chromium.org \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=samitolvanen@google.com \
--cc=swboyd@chromium.org \
--cc=vgoyal@redhat.com \
--cc=void@manifault.com \
/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).