From: "Arnd Bergmann" <arnd@arndb.de>
To: "Alexandre Belloni" <alexandre.belloni@bootlin.com>
Cc: "Karl Mehltretter" <kmehltretter@gmail.com>,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtc: class: Make the time32 hctosys limit configurable
Date: Tue, 06 Oct 2026 14:33:36 +0200 [thread overview]
Message-ID: <d07b4229-a5f8-47fc-9b1c-c4a7096959b4@app.fastmail.com> (raw)
In-Reply-To: <202610051349454ed35b56@mail.local>
On Mon, Oct 5, 2026, at 15:49, Alexandre Belloni wrote:
> On 24/09/2026 17:07:30+0200, Arnd Bergmann wrote:
>> On Tue, Sep 22, 2026, at 23:37, Alexandre Belloni wrote:
>>
>> Not sure what exactly you are suggesting here. Do you mean we should
>> try again to address this in systemd in order to no longer need
>> the RTC_HCTOSYS hack?
>>
>
> Well I guess we'll get the same answer that this is too late in the boot
> process.
Right
> My proposed solution is to have a way to tell the kernel what size of
> time_t userspace actually supports as there is no way to automatically
> detect it. That's why I was thinking a kernel cmdline parameter would
> fit. This would allow us to be 100% correct.
>
> Else, I'm fine with your last proposal.
Ok, thanks!
A command line argument would work for me as well, if we can make it
have a working default for the COMPAT_32BIT_TIME=n case.
We could of course combine a compile-time and boot-time flag, but
there should not be any need for that.
> I guess this would leave us with
> two unhandled cases:
> - 64bit systems with 32 bit userspace that you said we don't want to
> support
Right, as far as I'm concerned this has always done what I want,
so no need to change it.
> - 32bit systems with 64bit time_t userspace that would not work
> properly with the default configuration.
At this point it's just part of the platform defconfig, and
users can pick the setting.
Arnd
prev parent reply other threads:[~2026-10-06 12:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-14 21:25 Karl Mehltretter
2026-09-15 5:48 ` Arnd Bergmann
2026-09-15 22:37 ` Karl Mehltretter
2026-09-16 6:56 ` Arnd Bergmann
2026-09-19 0:10 ` Karl Mehltretter
2026-09-19 9:16 ` Arnd Bergmann
2026-09-22 21:37 ` Alexandre Belloni
2026-09-24 15:07 ` Arnd Bergmann
2026-10-05 13:49 ` Alexandre Belloni
2026-10-06 12:33 ` Arnd Bergmann [this message]
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=d07b4229-a5f8-47fc-9b1c-c4a7096959b4@app.fastmail.com \
--to=arnd@arndb.de \
--cc=alexandre.belloni@bootlin.com \
--cc=kmehltretter@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.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
all inboxes | Powered by JetHome®