From: Greg KH <gregkh@linuxfoundation.org>
To: Hongyu Xie <xiehongyu1@kylinos.cn>
Cc: linux@armlinux.org.uk, jirislaby@kernel.org,
rdunlap@infradead.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org, xy521521@gmail.com
Subject: Re: [RESEND RFC PATCH v3 -next] tty: serial: add panic serial helper
Date: Wed, 31 May 2023 09:05:53 +0100 [thread overview]
Message-ID: <2023053113-surviving-ride-2dd6@gregkh> (raw)
In-Reply-To: <20230531071802.414383-1-xiehongyu1@kylinos.cn>
On Wed, May 31, 2023 at 03:18:02PM +0800, Hongyu Xie wrote:
> It was inspired by kgdboc.
>
> This is a debug module that allows you to get all kernel logs
> after panic.
>
> Normally you need to attach a USB-to-UART tool or enable kdump
> before panic happens to get log from kernel after panic. If you
> didn't do that and kdump is not working, you can't get any log to
> know what happened before panic. If you have a USB-to-UART tool
> and the uart port on your computer is working. This module helps
> you to get all kernel log after panic() is called.
>
> To use this, see Documentation/dev-tools/panic_serial_helper.rst.
>
> Tested on arm64 device.
>
> Signed-off-by: Hongyu Xie <xiehongyu1@kylinos.cn>
> ---
>
> v3:
> 1. modify the document about this module.
> 2. provide case-ignored filter matching.
Why is this a RESEND?
It's a RFC, I can't apply it, as obviously you do not feel like it is
completed. What needs to be done to make you feel comfortable with it?
thanks,
greg k-h
prev parent reply other threads:[~2023-05-31 8:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-31 7:18 [RESEND RFC PATCH v3 -next] tty: serial: add panic serial helper Hongyu Xie
2023-05-31 8:05 ` Greg KH [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=2023053113-surviving-ride-2dd6@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=rdunlap@infradead.org \
--cc=xiehongyu1@kylinos.cn \
--cc=xy521521@gmail.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