From: Tri Vo <trong@android.com>
To: rjw@rjwysocki.net, viresh.kumar@linaro.org
Cc: Hridya Valsaraju <hridya@google.com>,
linux-pm@vger.kernel.org, kernel-team@android.com,
Sandeep Patil <sspatil@google.com>
Subject: Re: Alternatives to /sys/kernel/debug/wakeup_sources
Date: Tue, 11 Jun 2019 10:31:16 -0700 [thread overview]
Message-ID: <CANA+-vARQ9Ao=W1oEArrAQ0sqh757orq=-=kytdVPhstm-3E9w@mail.gmail.com> (raw)
In-Reply-To: <CANA+-vCThdRivg7nrMK5QoFu8SGUzEVSvSyp0H2CPyy9==Tqog@mail.gmail.com>
On Tue, Jun 4, 2019 at 5:23 PM Tri Vo <trong@android.com> wrote:
>
> Hello Rafael,
>
> Currently, Android reads wakeup sources statistics from
> /sys/kernel/debug/wakeup_sources in production environment. This
> information is used, for example, to report which wake lock prevents
> the device from suspending.
>
> Android userspace reading wakeup_sources is not ideal because:
> - Debugfs API is not stable, i.e. Android tools built on top of it are
> not guaranteed to be backward/forward compatible.
> - This file requires debugfs to be mounted, which itself is
> undesirable for security reasons.
>
> To address these problems, we want to contribute a way to expose these
> statistics that doesn't depend on debugfs.
>
> Some initial thoughts/questions: Should we expose the stats in sysfs?
> Or maybe implement eBPF-based solution? What do you think?
>
CC'ing some more folks.
> Thanks,
> Tri
next prev parent reply other threads:[~2019-06-11 17:31 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-05 0:23 Alternatives to /sys/kernel/debug/wakeup_sources Tri Vo
2019-06-11 17:31 ` Tri Vo [this message]
2019-06-18 20:17 ` Sandeep Patil
2019-06-18 21:23 ` Rafael J. Wysocki
2019-06-18 23:15 ` Tri Vo
2019-06-18 23:52 ` Joel Fernandes
2019-06-19 8:35 ` Rafael J. Wysocki
2019-06-19 10:33 ` Joel Fernandes
2019-06-19 16:51 ` Sandeep Patil
2019-06-19 16:53 ` Joel Fernandes
2019-06-19 17:07 ` Greg Kroah-Hartman
2019-06-19 18:01 ` Joel Fernandes
2019-06-19 18:31 ` Tri Vo
2019-06-19 18:35 ` Greg Kroah-Hartman
2019-06-19 18:55 ` Joel Fernandes
[not found] ` <CAGETcx-ZZRc_jtBws2cFTe1wjiWeBowdqfqOhcCJV_7AUyBEVw@mail.gmail.com>
2019-06-19 20:09 ` Joel Fernandes
2019-06-19 20:40 ` Saravana Kannan
2019-06-19 20:52 ` Joel Fernandes
2019-06-24 1:48 ` Tri Vo
2019-06-24 7:36 ` Greg Kroah-Hartman
2019-06-24 12:27 ` Joel Fernandes
2019-06-24 21:55 ` Rafael J. Wysocki
2019-06-24 22:14 ` Tri Vo
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='CANA+-vARQ9Ao=W1oEArrAQ0sqh757orq=-=kytdVPhstm-3E9w@mail.gmail.com' \
--to=trong@android.com \
--cc=hridya@google.com \
--cc=kernel-team@android.com \
--cc=linux-pm@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=sspatil@google.com \
--cc=viresh.kumar@linaro.org \
/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;
as well as URLs for NNTP newsgroup(s).