linux-kernel - Re: [RFC][PATCH] ACPI: tracing: Have ACPI debug go to tracing ring buffer

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20221215151333.49af5442@gandalf.local.home>
Date:   Thu, 15 Dec 2022 15:13:33 -0500
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Joel Fernandes <joel@...lfernandes.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linux Trace Kernel <linux-trace-kernel@...r.kernel.org>,
        linux-acpi@...r.kernel.org,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Len Brown <lenb@...nel.org>,
        Masami Hiramatsu <mhiramat@...nel.org>,
        Brian Norris <briannorris@...omium.org>,
        Ross Zwisler <zwisler@...gle.com>,
        Ching-lin Yu <chinglinyu@...gle.com>
Subject: Re: [RFC][PATCH] ACPI: tracing: Have ACPI debug go to tracing ring
 buffer

On Thu, 15 Dec 2022 14:52:48 -0500
Joel Fernandes <joel@...lfernandes.org> wrote:

> Another approach could be to always enable the trace event by default,
> if the CONFIG is turned on. Or do a printk() telling the user about
> the event to enable, so they know why their trace buffer is empty.

Yeah, that is another option.

And, yes I need to document it better. I started to, but then decided to
hold off until I get some feedback in case this is rejected.

> 
> Up to you and the ACPI maintainers. ;-)

I'm going to guess I may not hear back until the new year. I'm fine with
that :-) I'll send a reminder then too as I Cc'd the linux-trace-kernel
list, which will keep it active in patchwork.

Cheers!

-- Steve