From: peterz@infradead.org
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: Rafael Wysocki <rjw@rjwysocki.net>,
linux-pm@vger.kernel.org,
Vincent Guittot <vincent.guittot@linaro.org>,
Lukasz Luba <lukasz.luba@arm.com>,
cristian.marussi@arm.com, sudeep.holla@arm.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/4] cpufreq: stats: Defer stats update to cpufreq_stats_record_transition()
Date: Fri, 11 Sep 2020 12:11:32 +0200 [thread overview]
Message-ID: <20200911101132.GC165568@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <973bd0536c4957d03f36447398498cfacb2393d9.1599031227.git.viresh.kumar@linaro.org>
On Wed, Sep 02, 2020 at 12:54:41PM +0530, Viresh Kumar wrote:
> + atomic_t reset_pending;
> + atomic_set(&stats->reset_pending, 0);
> + if (atomic_read(&stats->reset_pending))
> + bool pending = atomic_read(&stats->reset_pending);
> + atomic_set(&stats->reset_pending, 1);
> + bool pending = atomic_read(&stats->reset_pending);
> + if (atomic_read(&stats->reset_pending))
What do you think atomic_t is doing for you?
next prev parent reply other threads:[~2020-09-11 10:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 7:24 [PATCH 0/4] cpufreq: Record stats with fast-switching Viresh Kumar
2020-09-02 7:24 ` [PATCH 1/4] cpufreq: stats: Defer stats update to cpufreq_stats_record_transition() Viresh Kumar
2020-09-11 10:11 ` peterz [this message]
2020-09-11 11:35 ` Viresh Kumar
2020-09-11 12:16 ` Rafael J. Wysocki
2020-09-15 10:04 ` Lukasz Luba
2020-09-16 5:56 ` Viresh Kumar
2020-09-02 7:24 ` [PATCH 2/4] cpufreq: stats: Remove locking Viresh Kumar
2020-09-02 7:24 ` [PATCH 3/4] cpufreq: stats: Enable stats for fast-switch as well Viresh Kumar
2020-09-02 7:24 ` [PATCH 4/4] cpufreq: Move traces and update to policy->cur to cpufreq core Viresh Kumar
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=20200911101132.GC165568@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=cristian.marussi@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=vincent.guittot@linaro.org \
--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