From: Mukesh Ojha <mojha@codeaurora.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: john.stultz@linaro.org, linux-kernel@vger.kernel.org,
neeraju@codeaurora.org, gkohli@codeaurora.org,
cpandya@codeaurora.org
Subject: Re: [PATCH v2] time: Fix sleeptime injection for non-stop clocksource & persistent clock
Date: Fri, 6 Jul 2018 13:45:33 +0530 [thread overview]
Message-ID: <be7701cb-c0f0-a357-ba99-8f86a18060c2@codeaurora.org> (raw)
In-Reply-To: <alpine.DEB.2.21.1806251701410.1821@nanos.tec.linutronix.de>
Hi Thomas,
Could you raise a formal patch on this as you are the author now?
Thanks,
Mukesh
On 6/25/2018 8:34 PM, Thomas Gleixner wrote:
> On Mon, 25 Jun 2018, Mukesh Ojha wrote:
>> On 6/23/2018 2:57 AM, Thomas Gleixner wrote:
>>> @@ -1671,7 +1685,6 @@ void timekeeping_resume(void)
>>> struct timespec64 ts_new, ts_delta;
>>> u64 cycle_now;
>>> - sleeptime_injected = false;
>>> read_persistent_clock64(&ts_new);
>>> clockevents_resume();
>>> @@ -1743,6 +1756,8 @@ int timekeeping_suspend(void)
>>> if (timekeeping_suspend_time.tv_sec ||
>>> timekeeping_suspend_time.tv_nsec)
>>> persistent_clock_exists = true;
>>> + sleeptime_injected = false;
>> I did not get the exact valid point of moving it from `timekeeping_suspend` to
>> `timekeeping_resume`.
> It's the other way round. I move it from resume to suspend. Simply because
> it should only be set to 'false' when suspend is reached. It would work the
> other way round as well, but I felt it's inconsistent.
>
> Thanks,
>
> tglx
>
>
next prev parent reply other threads:[~2018-07-06 8:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-30 11:44 [PATCH v2] time: Fix sleeptime injection for non-stop clocksource & persistent clock Mukesh Ojha
2018-06-14 14:07 ` Mukesh Ojha
2018-06-22 21:27 ` Thomas Gleixner
2018-06-25 14:38 ` Mukesh Ojha
2018-06-25 15:04 ` Thomas Gleixner
2018-07-06 8:15 ` Mukesh Ojha [this message]
2018-07-06 8:58 ` Thomas Gleixner
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=be7701cb-c0f0-a357-ba99-8f86a18060c2@codeaurora.org \
--to=mojha@codeaurora.org \
--cc=cpandya@codeaurora.org \
--cc=gkohli@codeaurora.org \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraju@codeaurora.org \
--cc=tglx@linutronix.de \
/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).