[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87pn41j7jx.fsf@nanos.tec.linutronix.de>
Date: Thu, 26 Nov 2020 01:17:06 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Carlos O'Donell <carlos@...hat.com>,
Zack Weinberg <zackw@...ix.com>, Cyril Hrubis <chrubis@...e.cz>
Cc: Dmitry Safonov <dima@...sta.com>, Andrei Vagin <avagin@...il.com>,
GNU C Library <libc-alpha@...rceware.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Petr Špaček <petr.spacek@....cz>
Subject: Re: [Y2038][time namespaces] Question regarding CLOCK_REALTIME support plans in Linux time namespaces
Carlos, Petr,
On Wed, Nov 25 2020 at 15:37, Carlos O'Donell wrote:
> On 11/19/20 7:14 PM, Thomas Gleixner wrote:
>> So from my point of view asking for distorted time still _is_ a request
>> for ponies.
>
> I'm happy if you say it's more work than the value it provides.
Thinking more about it. Would a facility which provides:
CLOCK_FAKE_MONOTONIC|BOOTTIME|REALTIME
where you can go wild on setting time to whatever you want solve
your problem?
Thanks,
tglx
Powered by blists - more mailing lists