linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Stultz <john.stultz@linaro.org>
To: Dong Zhu <bluezhudong@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] timekeeping: avoid adjust kernel time once hwclock kept in UTC time
Date: Tue, 18 Dec 2012 22:37:08 -0800	[thread overview]
Message-ID: <50D16094.1030101@linaro.org> (raw)
In-Reply-To: <20121219051518.GA8584@zhudong.nay.redhat.com>

On 12/18/2012 09:15 PM, Dong Zhu wrote:
> On Thu, Dec 06, 2012 at 10:03:34PM +0800, Dong Zhu wrote:
>>  From c126376cf1837b0956e0268056db61870fbbc1d4 Mon Sep 17 00:00:00 2001
>> From: Dong Zhu <bluezhudong@gmail.com>
>> Date: Thu, 6 Dec 2012 21:45:00 +0800
>> Subject: [PATCH] timekeeping: avoid adjust kernel time once hwclock kept in
>>   UTC time
>>
>> If the Hardware Clock kept in local time,kernel will adjust the time
>> to be UTC time.But if Hardware Clock kept in UTC time,system will make
>> a dummy settimeofday call first (sys_tz.tz_minuteswest = 0) to make sure
>> the time is not shifted,so at this point I think maybe it is not necessary
>> to set the kernel time once the sys_tz.tz_minuteswest is zero.
>>
>> Signed-off-by: Dong Zhu <bluezhudong@gmail.com>
>> ---
>>   kernel/time.c | 8 +++++---
>>   1 file changed, 5 insertions(+), 3 deletions(-)
>>
>> diff --git a/kernel/time.c b/kernel/time.c
>> index d226c6a..0b592ce 100644
>> --- a/kernel/time.c
>> +++ b/kernel/time.c
>> @@ -134,9 +134,11 @@ static inline void warp_clock(void)
>>   {
>>   	struct timespec adjust;
>>   
>> -	adjust = current_kernel_time();
>> -	adjust.tv_sec += sys_tz.tz_minuteswest * 60;
>> -	do_settimeofday(&adjust);
>> +	if (sys_tz.tz_minuteswest) {
>> +		adjust = current_kernel_time();
>> +		adjust.tv_sec += sys_tz.tz_minuteswest * 60;
>> +		do_settimeofday(&adjust);
>> +	}
>>   }
>>   
>>   /*
>> -- 
>> 1.7.11.7
>>
> Hi,
>
> Any comments ?
Sorry for the slow response, been a little busy.   Honestly the 
warp_clock() code path is always been a bit odd to me, so I've not 
really been able to get my head around the implications of this change.

Really, I'm not sure if I'll get to this before the new year.
Its on my list, but don't be afraid to ping me early Jan if I haven't 
queued it for 3.9 by then.

thanks
-john


  reply	other threads:[~2012-12-19  6:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-06 14:03 [PATCH] timekeeping: avoid adjust kernel time once hwclock kept in UTC time Dong Zhu
2012-12-19  5:15 ` Dong Zhu
2012-12-19  6:37   ` John Stultz [this message]
2013-02-20  8:13     ` Dong Zhu
2013-02-22 20:37 ` John Stultz

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=50D16094.1030101@linaro.org \
    --to=john.stultz@linaro.org \
    --cc=bluezhudong@gmail.com \
    --cc=linux-kernel@vger.kernel.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).