From: Chen Yu <yu.c.chen@intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>, Len Brown <len.brown@intel.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Michal Miroslaw" <mirq-linux@rere.qmqm.pl>,
Zhang Rui <rui.zhang@intel.com>,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
Chen Yu <yu.c.chen@intel.com>
Subject: [PATCH 0/2][RESEND v3] Extend trace point to cover all runtime usage count
Date: Wed, 15 Jul 2020 14:27:27 +0800 [thread overview]
Message-ID: <cover.1594790493.git.yu.c.chen@intel.com> (raw)
Currently some code flow of runtime usage count changes is not covered by
the rpm_runtime_usage tracepoints. Adjust corresponding tracepoints to monitor
all the runtime usage count changes.
Chen Yu (2):
PM-runtime: Move all runtime usage related function to runtime.c
PM-runtime: change the tracepoints to cover all usage_count
drivers/base/power/runtime.c | 50 ++++++++++++++++++++++++++----------
include/linux/pm_runtime.h | 12 ++-------
2 files changed, 38 insertions(+), 24 deletions(-)
--
2.17.1
next reply other threads:[~2020-07-15 6:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 6:27 Chen Yu [this message]
2020-07-15 6:27 ` [PATCH 1/2][RESEND v3] PM-runtime: Move all runtime usage related function to runtime.c Chen Yu
2020-07-15 15:35 ` Rafael J. Wysocki
2020-07-15 6:28 ` [PATCH 2/2][RESEND v3] PM-runtime: change the tracepoints to cover all usage_count Chen Yu
2020-07-15 7:06 ` Greg Kroah-Hartman
2020-07-15 7:27 ` Michal Miroslaw
2020-07-15 8:17 ` Greg Kroah-Hartman
2020-07-15 8:18 ` Chen Yu
2020-07-15 8:33 ` Greg Kroah-Hartman
2020-07-16 1:36 ` Chen Yu
2020-07-15 15:47 ` Rafael J. Wysocki
2020-07-16 1:49 ` Chen Yu
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=cover.1594790493.git.yu.c.chen@intel.com \
--to=yu.c.chen@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mirq-linux@rere.qmqm.pl \
--cc=rafael@kernel.org \
--cc=rui.zhang@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.