[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <alpine.DEB.2.20.1609022119160.5647@nanos>
Date: Fri, 2 Sep 2016 21:26:51 +0200 (CEST)
From: Thomas Gleixner <tglx@...utronix.de>
To: "Rafael J. Wysocki" <rjw@...ysocki.net>
cc: Chen Yu <yu.c.chen@...el.com>, x86@...nel.org,
John Stultz <john.stultz@...aro.org>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, linux-kernel@...r.kernel.org,
Xunlei Pang <xlpang@...hat.com>,
"3.17+" <stable@...r.kernel.org>, Zhang Rui <rui.zhang@...el.com>,
linux-pm@...r.kernel.org
Subject: Re: [PATCH][RFC v5] timekeeping: Ignore the bogus sleep time if
pm_trace is enabled
On Wed, 31 Aug 2016, Rafael J. Wysocki wrote:
> On Monday, August 29, 2016 12:40:39 AM Chen Yu wrote:
> > +
> > + /*
> > + * Make rtc-based persistent clock unusable
> > + * if pm_trace is enabled, only take effect
> > + * for timekeeping_suspend/resume.
> > + */
> > + if (pm_trace_is_enabled() &&
> > + x86_platform.get_wallclock == mach_get_cmos_time) {
> > + ts->tv_sec = 0;
> > + ts->tv_nsec = 0;
> > + }
>
> I'm not sure about this. Looks hackish.
Indeed. Can't you just keep track that pm_trace fiddled with the cmos clock
and then discard the value either in the core or in mach_get_cmos_time()
Thanks,
tglx
Powered by blists - more mailing lists