[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0733578f-1f9d-bbd4-0c30-a8a124f5ffa8@redhat.com>
Date: Wed, 8 Jul 2020 13:50:51 +0800
From: lijiang <lijiang@...hat.com>
To: John Ogness <john.ogness@...utronix.de>,
Petr Mladek <pmladek@...e.com>
Cc: Peter Zijlstra <peterz@...radead.org>,
Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>,
Sergey Senozhatsky <sergey.senozhatsky@...il.com>,
Steven Rostedt <rostedt@...dmis.org>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Andrea Parri <parri.andrea@...il.com>,
Thomas Gleixner <tglx@...utronix.de>,
Paul McKenney <paulmck@...nel.org>, kexec@...ts.infradead.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v3 3/3] printk: use the lockless ringbuffer
在 2020年07月03日 19:54, John Ogness 写道:
> On 2020-07-02, lijiang <lijiang@...hat.com> wrote:
>> About the VMCOREINFO part, I made some tests based on the kernel patch
>> v3, the makedumpfile and crash-utility can work as expected with your
>> patch(userspace patch), but, unfortunately, the
>> vmcore-dmesg(kexec-tools) can't correctly read the printk ring buffer
>> information, and get the following error:
>>
>> "Missing the log_buf symbol"
>>
>> The kexec-tools(vmcore-dmesg) should also have a similar patch, just like
>> in the makedumpfile and crash-utility.
>
> A patched kexec-tools is available here [0].
>
> I did not test using 32-bit dumps on 64-bit machines and vice versa. But
> it should work.
>
> John Ogness
>
> [0] https://github.com/Linutronix/kexec-tools.git (printk branch)
>
After applying this patch, the vmcore-dmesg can work.
Thank you, John Ogness.
Powered by blists - more mailing lists