From: "Theodore Y. Ts'o" <tytso@mit.edu>
To: 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>,
"H. Peter Anvin" <hpa@zytor.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>
Subject: Re: New kernel interface for sys_tz and timewarp?
Date: Tue, 13 Aug 2019 20:06:23 -0400 [thread overview]
Message-ID: <20190814000622.GB20365@mit.edu> (raw)
In-Reply-To: <CAHk-=wiO2CWONDBud4nxoPgUJN1JEewFWhHa5wAqY8G5rrTXRQ@mail.gmail.com>
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".
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.
Trying to use this for anything else is probably a bad idea, and in a
world where we can have initrd's and reading the RTC gets done by
userspace as opposed to kernel, it probably doesn't make any sence to
keep it.
Cheers,
- Ted
next prev parent reply other threads:[~2019-08-14 0:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 9:05 New kernel interface for sys_tz and timewarp? Arnd Bergmann
2019-08-13 17:10 ` John Stultz
2019-08-13 21:45 ` Alexandre Belloni
2019-08-13 17:30 ` Linus Torvalds
2019-08-13 17:49 ` Paul Eggert
2019-08-13 19:31 ` Florian Weimer
2019-08-13 20:04 ` Arnd Bergmann
2019-08-13 21:56 ` Alexandre Belloni
2019-08-14 0:06 ` Theodore Y. Ts'o [this message]
2019-08-14 8:31 ` Arnd Bergmann
2019-08-14 9:09 ` Lennart Poettering
2019-08-14 9:32 ` Alexandre Belloni
2019-08-14 12:15 ` Lennart Poettering
2019-08-19 11:09 ` Karel Zak
2019-08-19 13:43 ` Thomas Gleixner
2019-08-19 13:49 ` Thomas Gleixner
2019-08-20 18:45 ` Alexandre Belloni
2019-08-20 18:47 ` Alexandre Belloni
2019-08-20 18:58 ` Alexandre Belloni
2019-08-27 16:27 ` Arnd Bergmann
2019-08-27 16:31 ` Alexandre Belloni
2019-08-14 16:26 ` David Laight
2019-08-14 16:47 ` hpa
2019-08-15 13:22 ` Arnd Bergmann
2019-08-15 15:05 ` Theodore Y. Ts'o
2019-08-15 15:24 ` hpa
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=20190814000622.GB20365@mit.edu \
--to=tytso@mit.edu \
--cc=alexandre.belloni@bootlin.com \
--cc=alistair.francis@wdc.com \
--cc=arnd@arndb.de \
--cc=fweimer@redhat.com \
--cc=hirofumi@mail.parknet.co.jp \
--cc=hpa@zytor.com \
--cc=john.stultz@linaro.org \
--cc=kzak@redhat.com \
--cc=lennart@poettering.net \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=palmer@dabbelt.com \
--cc=sboyd@kernel.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
/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).