From: alexandre.belloni@free-electrons.com (Alexandre Belloni)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 2/2] clocksource: don't suspend/resume when unused
Date: Fri, 16 Jan 2015 12:28:08 +0100 [thread overview]
Message-ID: <20150116112808.GM3843@piout.net> (raw)
In-Reply-To: <20150116112324.GG12302@n2100.arm.linux.org.uk>
On 16/01/2015 at 11:23:24 +0000, Russell King - ARM Linux wrote :
> On Fri, Jan 16, 2015 at 11:35:30AM +0100, Alexandre Belloni wrote:
> > On 16/01/2015 at 11:23:32 +0100, Thomas Gleixner wrote :
> > > On Fri, 16 Jan 2015, Alexandre Belloni wrote:
> > >
> > > > There is no point in calling suspend/resume for unused
> > > > clocksources.
> > > >
> > > > Signed-off-by: Alexandre Belloni <alexandre.belloni@free-electrons.com>
> > > > ---
> > > > kernel/time/clocksource.c | 4 ++--
> > > > 1 file changed, 2 insertions(+), 2 deletions(-)
> > > >
> > > > diff --git a/kernel/time/clocksource.c b/kernel/time/clocksource.c
> > > > index 920a4da58eb0..baea4e42ae90 100644
> > > > --- a/kernel/time/clocksource.c
> > > > +++ b/kernel/time/clocksource.c
> > > > @@ -493,7 +493,7 @@ void clocksource_suspend(void)
> > > > struct clocksource *cs;
> > > >
> > > > list_for_each_entry_reverse(cs, &clocksource_list, list)
> > > > - if (cs->suspend)
> > > > + if (cs->suspend && (cs->flags & CLOCK_SOURCE_USED))
> > > > cs->suspend(cs);
> > >
> > > This might be dangerous. If the clocksource has no enable/disable
> > > callbacks, but suspend/resume, then you might leave it enabled across
> > > suspend.
> > >
> >
> > Isn't that already the case?
> > Right now, if you call clocksource_suspend, it doesn't matter whether
> > the clocksource has an enable or not, it will be suspended. Maybe I'm
> > mistaken but my patch doesn't seem to change that behaviour.
>
> You change an "always suspend" problem to a "never suspend" problem
> since those clocksources which are used, but do not have an ->enable
> callback will not be marked with CLOCK_SOURCE_USED.
>
> Look at patch 1:
>
> - if (!new->enable || new->enable(new) == 0) {
> + if (!new->enable || clocksource_enable(new) == 0) {
>
> If new->enable is NULL, clocksource_enable() won't be called, which
> means there's nothing which sets CLOCK_SOURCE_USED, which in turn
> means that ->suspend() will never be called.
>
My mistake, I should have remove the check, this should be:
if (clocksource_enable(new) == 0)
And I'll do the change suggested by Boris which should solve that
issue.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-01-16 11:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 9:17 [RFC 0/2] clocksource: don't suspend/resume when unused Alexandre Belloni
2015-01-16 9:17 ` [RFC 1/2] clocksource: track usage Alexandre Belloni
2015-01-16 10:39 ` Boris Brezillon
2015-02-02 20:03 ` Kevin Hilman
2015-01-16 9:17 ` [RFC 2/2] clocksource: don't suspend/resume when unused Alexandre Belloni
2015-01-16 10:23 ` Thomas Gleixner
2015-01-16 10:35 ` Alexandre Belloni
2015-01-16 10:39 ` Daniel Lezcano
2015-01-16 10:48 ` Alexandre Belloni
2015-01-16 10:59 ` Daniel Lezcano
2015-01-16 11:07 ` Alexandre Belloni
2015-01-16 11:45 ` Alexandre Belloni
2015-01-16 11:23 ` Russell King - ARM Linux
2015-01-16 11:28 ` Alexandre Belloni [this message]
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=20150116112808.GM3843@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.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).