From: Thomas Gleixner <tglx@linutronix.de>
To: Carlos O'Donell <carlos@redhat.com>,
Zack Weinberg <zackw@panix.com>, Cyril Hrubis <chrubis@suse.cz>
Cc: "Dmitry Safonov" <dima@arista.com>,
"Andrei Vagin" <avagin@gmail.com>,
"GNU C Library" <libc-alpha@sourceware.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Petr Špaček" <petr.spacek@nic.cz>
Subject: Re: [Y2038][time namespaces] Question regarding CLOCK_REALTIME support plans in Linux time namespaces
Date: Thu, 26 Nov 2020 01:17:06 +0100 [thread overview]
Message-ID: <87pn41j7jx.fsf@nanos.tec.linutronix.de> (raw)
In-Reply-To: <5c382ef4-c505-5629-a85c-abae67c05c7c@redhat.com>
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
next prev parent reply other threads:[~2020-11-26 0:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-30 10:02 Lukasz Majewski
2020-10-30 13:08 ` Thomas Gleixner
2020-10-30 15:43 ` Lukasz Majewski
2020-10-30 13:58 ` Cyril Hrubis
2020-10-30 14:02 ` Zack Weinberg
2020-10-30 15:10 ` Thomas Gleixner
2020-10-30 16:58 ` Carlos O'Donell
2020-10-30 20:06 ` Thomas Gleixner
2020-10-30 22:19 ` Carlos O'Donell
2020-10-31 1:38 ` Thomas Gleixner
2020-11-03 12:43 ` Cyril Hrubis
2020-11-05 17:25 ` Carlos O'Donell
2020-11-07 0:47 ` Thomas Gleixner
2020-11-19 18:37 ` Carlos O'Donell
2020-11-20 0:14 ` Thomas Gleixner
2020-11-25 17:06 ` Petr Špaček
2020-11-25 20:37 ` Carlos O'Donell
2020-11-26 0:17 ` Thomas Gleixner [this message]
2020-11-26 3:05 ` Carlos O'Donell
2020-11-26 8:21 ` Andreas Schwab
2020-11-19 12:08 ` Petr Špaček
2020-11-14 10:25 ` Pavel Machek
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=87pn41j7jx.fsf@nanos.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=avagin@gmail.com \
--cc=carlos@redhat.com \
--cc=chrubis@suse.cz \
--cc=dima@arista.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=petr.spacek@nic.cz \
--cc=zackw@panix.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).