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:   Thu, 15 Aug 2019 08:24:09 -0700
User-Agent: K-9 Mail for Android
In-Reply-To: <20190815150530.GA18727@mit.edu>
References: <CAK8P3a0VxM1BkjY1D2FfHi6L-ho_NH3v3+gBu45EfpjLF5NU5w@mail.gmail.com> <CAHk-=wiO2CWONDBud4nxoPgUJN1JEewFWhHa5wAqY8G5rrTXRQ@mail.gmail.com> <20190814000622.GB20365@mit.edu> <342565604d704b6ebaf2e9ec28d3e109@AcuMS.aculab.com> <0089C4CC-DD85-48A1-869B-A9D71852BEC7@zytor.com> <CAK8P3a0VQ1F5xnRNmfeg-rAWbKb64u_8xfQjFNahNRoAHTMJ3g@mail.gmail.com> <20190815150530.GA18727@mit.edu>
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:     "Theodore Y. Ts'o" <tytso@mit.edu>, Arnd Bergmann <arnd@arndb.de>
CC:     David Laight <David.Laight@aculab.com>,
        Linus Torvalds <torvalds@linux-foundation.org>,
        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: <EA707642-4509-4B88-B4FF-453B1F473608@zytor.com>
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On August 15, 2019 8:05:30 AM PDT, "Theodore Y=2E Ts'o" <tytso@mit=2Eedu> w=
rote:
>On Thu, Aug 15, 2019 at 03:22:45PM +0200, Arnd Bergmann wrote:
>> If 64-bit Windows relies on a working EFI RTC implementation, we
>could
>> decide to leave the driver enabled on 64-bit and only disable it for
>> 32-bit EFI=2E That way, future distros would no longer have to worry
>about
>> the localtime hack, at least the ones that have dropped support for
>> 32-bit x86 kernels=2E
>
>=2E=2E=2E and who have also dropped support for legacy (non-UEFI) 64-bit
>boot=2E  Keep in mind that even for distributions which may install with
>UEFI by default, if people have been upgrading from (for example)
>Debian Jessie to Stretch to Buster, they may still be using non-UEFI
>boot=2E  This might be especially true on small Linode servers (such as,
>for example, the one which is currently running my mail smarthost=2E=2E=
=2E=2E)
>
>    	     	     	      			   - Ted

There is also the ACPI TAD device, which can be used to expose this throug=
h ACPI=2E We might also be able to request that the ACPI information for th=
e RTC be augmented with a CMOS timezone location=2E
--=20
Sent from my Android device with K-9 Mail=2E Please excuse my brevity=2E