[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160728103812.41e02ae5@gandalf.local.home>
Date: Thu, 28 Jul 2016 10:38:12 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Namhyung Kim <namhyung@...nel.org>
Cc: "Michael S. Tsirkin" <mst@...hat.com>, <kvm@...r.kernel.org>,
<qemu-devel@...gnu.org>,
<virtualization@...ts.linux-foundation.org>,
LKML <linux-kernel@...r.kernel.org>,
Paolo Bonzini <pbonzini@...hat.com>,
Radim Krčmář <rkrcmar@...hat.com>,
Anthony Liguori <aliguori@...zon.com>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Kees Cook <keescook@...omium.org>,
Tony Luck <tony.luck@...el.com>,
Ingo Molnar <mingo@...nel.org>,
Minchan Kim <minchan@...nel.org>
Subject: Re: [PATCH 6/7] qemu: Implement virtio-pstore device
On Thu, 28 Jul 2016 14:39:53 +0900
Namhyung Kim <namhyung@...nel.org> wrote:
> Well, I dont' know. As you know, the kernel oops dump is already sent
> to serial device but it's rather slow. As I wrote in the cover
> letter, enabling ftrace_dump_on_oops makes it even worse.. Also
> pstore saves the (compressed) binary data so I thought it'd be better
> to have a dedicated IO channel.
BTW, I agree with this. It is better to have a quick way to grab the
ftrace buffers when a crash happens, as serial is excruciatingly slow.
Although, currently I still use kexec/kdump, but as Namhyung said, it
depends on crash being up to date. I tend to be sending in updates
every time I have to use it.
-- Steve
Powered by blists - more mailing lists