From: Kieran Bingham <kbingham@kernel.org>
To: Jan Kiszka <jan.kiszka@siemens.com>,
Petr Mladek <pmladek@suse.com>,
John Ogness <john.ogness@linutronix.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Baoquan He <bhe@redhat.com>, Dave Young <dyoung@redhat.com>,
Vivek Goyal <vgoyal@redhat.com>, Jonathan Corbet <corbet@lwn.net>,
Sergey Senozhatsky <sergey.senozhatsky.work@gmail.com>,
Sergey Senozhatsky <sergey.senozhatsky@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Nick Desaulniers <ndesaulniers@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2][next] update gdb scripts for lockless printk ringbuffer
Date: Mon, 24 Aug 2020 10:20:53 +0100 [thread overview]
Message-ID: <a5f4c178-9b3c-6ccd-9ea1-24d8fdc13273@kernel.org> (raw)
In-Reply-To: <d81e8b0d-fa7f-1da1-671f-0541b94ad349@siemens.com>
Hi Petr,
On 21/08/2020 09:55, Jan Kiszka wrote:
> On 21.08.20 10:08, Petr Mladek wrote:
>> On Fri 2020-08-14 23:31:23, John Ogness wrote:
>>> Hi,
>>>
>>> When we brought in the new lockless printk ringbuffer, we overlooked the gdb
>>> scripts. Here are a set of patches to implement gdb support for the new
>>> ringbuffer.
>>>
>>> John Ogness (2):
>>> scripts/gdb: add utils.read_ulong()
>>> scripts/gdb: update for lockless printk ringbuffer
>>
>> I am not fluent in the gdb macros and python so I did not try any
>> deep review. But both patches work for me:
>>
>> Tested-by: Petr Mladek <pmladek@suse.com>
>>
>> I am going to give it few more days before pushing just in case there is
>> another feedback.
Before 'pushing' ?
What context do you mean here? These patches go through AKPM don't they?
Did I miss some update to procedures?
>>
>
> Thanks, perfect!
>
>> Best Regards,
>> Petr
>>
>> BTW: Are you aware of https://github.com/crash-python/crash-python project?
>> The ambition is to implement "crash" features and even more into
>> gdb using python extensions. It similar approach like
>> scripts/gdb/
>>
>> crash-python is being developed sporadically in waves. It is
>> mostly during a week that is dedicated for such projects
>> at SUSE. It would be great to get more contributors.
>>
>
> The problem with all those out-of-tree kernel debugging projects is that
> they are even further away from the changes in upstream they need to
> adjust to over and over again. It's already hard for scripts/gdb to keep
> up as only few people are aware of the dependencies, and it's always
> easy to forget. But it's getting better and better here IMHO. And that
> was my idea behind pushing things into upstream.
Seconding that, and having also investigated the crash projects in
previous work. I really wish there was more alignment to the kernel ;-)
/me ponders what happened to the kernel awareness integrations on GDB...
I know others have been investigating too, If only I had time ...
> Jan
>
--
--
Kieran
next prev parent reply other threads:[~2020-08-24 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-14 21:25 John Ogness
2020-08-14 21:25 ` [PATCH 1/2][next] scripts/gdb: add utils.read_ulong() John Ogness
2020-08-14 22:29 ` Nick Desaulniers
2020-08-14 21:25 ` [PATCH 2/2][next] scripts/gdb: update for lockless printk ringbuffer John Ogness
2020-08-14 22:24 ` [PATCH 0/2][next] update gdb scripts " Nick Desaulniers
2020-08-21 8:08 ` Petr Mladek
2020-08-21 8:55 ` Jan Kiszka
2020-08-24 9:20 ` Kieran Bingham [this message]
2020-08-25 12:35 ` Petr Mladek
2020-08-25 13:53 ` Jan Kiszka
2020-08-26 0:17 ` Andrew Morton
2020-09-01 12:31 ` Petr Mladek
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=a5f4c178-9b3c-6ccd-9ea1-24d8fdc13273@kernel.org \
--to=kbingham@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=corbet@lwn.net \
--cc=dyoung@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jan.kiszka@siemens.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ndesaulniers@google.com \
--cc=pmladek@suse.com \
--cc=rostedt@goodmis.org \
--cc=sergey.senozhatsky.work@gmail.com \
--cc=sergey.senozhatsky@gmail.com \
--cc=torvalds@linux-foundation.org \
--cc=vgoyal@redhat.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
all inboxes | Powered by JetHome®