[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAEXW_YQk44VdSrZFtpfyCPHcrDxEFaEe2Wu900CZcWWodw3+xg@mail.gmail.com>
Date: Fri, 1 Jul 2022 12:53:17 -0400
From: Joel Fernandes <joel@...lfernandes.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Rob Herring <robh+dt@...nel.org>,
Nachammai Karuppiah <nachukannan@...il.com>,
Ingo Molnar <mingo@...hat.com>,
Frank Rowand <frowand.list@...il.com>,
Kees Cook <keescook@...omium.org>,
Anton Vorontsov <anton@...msg.org>,
Colin Cross <ccross@...roid.com>,
Tony Luck <tony.luck@...el.com>,
LKML <linux-kernel@...r.kernel.org>,
Sai Prakash Ranjan <saiprakash.ranjan@...eaurora.org>,
Brian Norris <computersforpeace@...il.com>
Subject: Re: [RFC PATCH 0/7] Trace events to pstore
On Fri, Jul 1, 2022 at 12:46 PM Steven Rostedt <rostedt@...dmis.org> wrote:
>
> On Fri, 1 Jul 2022 12:37:35 -0400
> Joel Fernandes <joel@...lfernandes.org> wrote:
>
> > I am curious how this came on your radar after 2 years, did someone
> > tell you to prioritize improving performance of ftrace on pstore? I
> > could probably make time to work on it more if someone has a usecase
> > for this or something.
>
> I'm looking into ways to extract the ftrace ring buffer from crashes, and
> it was brought up that pstore was used before.
Interesting. In the case of pstore, you know exactly where the pages
are for ftrace. How would you know that for the buddy system where
pages are in the wild wild west? I guess you would need to track where
ftrace pages where allocated, within the crash dump/report.
- Joel
Powered by blists - more mailing lists