Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Wed, 14 Aug 2019 09:47:39 -0700
User-Agent: K-9 Mail for Android
In-Reply-To: <342565604d704b6ebaf2e9ec28d3e109@AcuMS.aculab.com>
References: <CAK8P3a0VxM1BkjY1D2FfHi6L-ho_NH3v3+gBu45EfpjLF5NU5w@mail.gmail.com> <CAHk-=wiO2CWONDBud4nxoPgUJN1JEewFWhHa5wAqY8G5rrTXRQ@mail.gmail.com> <20190814000622.GB20365@mit.edu> <342565604d704b6ebaf2e9ec28d3e109@AcuMS.aculab.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
Subject: RE: New kernel interface for sys_tz and timewarp?
To:     David Laight <David.Laight@ACULAB.COM>,
        "'Theodore Y. Ts'o'" <tytso@mit.edu>,
        Linus Torvalds <torvalds@linux-foundation.org>
CC:     Arnd Bergmann <arnd@arndb.de>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Thomas Gleixner <tglx@linutronix.de>,
        John Stultz <john.stultz@linaro.org>,
        Alexandre Belloni <alexandre.belloni@bootlin.com>,
        Stephen Boyd <sboyd@kernel.org>,
        Florian Weimer <fweimer@redhat.com>,
        Palmer Dabbelt <palmer@dabbelt.com>,
        Alistair Francis <alistair.francis@wdc.com>,
        GNU C Library <libc-alpha@sourceware.org>,
        Karel Zak <kzak@redhat.com>,
        Lennart Poettering <lennart@poettering.net>,
        OGAWA Hirofumi <hirofumi@mail.parknet.co.jp>
From:   hpa@zytor.com
Message-ID: <0089C4CC-DD85-48A1-869B-A9D71852BEC7@zytor.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On August 14, 2019 9:26:36 AM PDT, David Laight <David=2ELaight@ACULAB=2ECO=
M> wrote:
>From: Theodore Y=2E Ts'o
>> Sent: 14 August 2019 01:06
>> On Tue, Aug 13, 2019 at 10:30:34AM -0700, Linus Torvalds wrote:
>> >
>> > I suspect the only actual _valid_ use in the kernel for a time zone
>> > setting is likely for RTC clock setting, but even that isn't really
>> > "global", as much as "per RTC"=2E
>>=20
>> As I recall (and I may or may not have been original for the original
>> sys_tz; it was many years ago, and my memories of 1992 are a bit
>> fuzzy) the only reason why we added it was because x86 systems that
>> were dual-booting with Windows had a RTC which ticked localtime, and
>> originally, the system time was fetched from the RTC in early boot,
>> and then when the timezone was set, the time would be warped so it
>> would be correct=2E
>
>x86 systems are very likely to have the RTC set by the bios config=2E
>In which case it will almost certainly get set to local time=2E
>It is certainly the default for windows installs - I don't even know
>if you have any other option=2E
>
>The 'real fun' (tm) happens when a dual boot system changes from
>winter to summer time=2E
>ISTR that it is quite easy to get both (or more) OS to change the
>RTC by an hour (I went home an hour early one year)=2E
>Although the x86 RTC chip has a bit defined for 'summertime', nothing
>sets it (at least when I looked)=2E
>
>	David
>
>-
>Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes,
>MK1 1PT, UK
>Registration No: 1397386 (Wales)

I believe Windows 10 changed the default RTC to UTC, although perhaps only=
 if running under UEFI=2E
--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E