From: Richard Cochran <richardcochran@gmail.com>
To: Sagi Maimon <maimon.sagi@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Andy Lutomirski <luto@kernel.org>,
tglx@linutronix.de, Ingo Molnar <mingo@redhat.com>,
Borislav Petkov <bp@alien8.de>,
Dave Hansen <dave.hansen@linux.intel.com>,
x86@kernel.org, "H. Peter Anvin" <hpa@zytor.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Peter Zijlstra <peterz@infradead.org>,
Johannes Weiner <hannes@cmpxchg.org>,
Sohil Mehta <sohil.mehta@intel.com>,
Rick Edgecombe <rick.p.edgecombe@intel.com>,
Nhat Pham <nphamcs@gmail.com>, Palmer Dabbelt <palmer@sifive.com>,
Kees Cook <keescook@chromium.org>,
Alexey Gladkov <legion@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
Linux-Arch <linux-arch@vger.kernel.org>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH v3] posix-timers: add multi_clock_gettime system call
Date: Mon, 15 Jan 2024 15:41:45 -0800 [thread overview]
Message-ID: <ZaXCuV1Dy0e_E-h0@hoboy.vegasvil.org> (raw)
In-Reply-To: <CAMuE1bF4sSeiDr-jyebF6F8oRxGs1b2gtT39fTJ2JeaFabr6Ng@mail.gmail.com>
On Mon, Jan 15, 2024 at 05:49:32PM +0200, Sagi Maimon wrote:
> Thanks for your notes, all of them will be done on the next patch (it
> will take some time due to work overload).
No hurry, glad you are keeping this going...
> The only question that I have is: why not implement it as an IOCTL?
> It makes more sense to me since it is close to another IOCTL, the
> "PTP_SYS_OFFSET" family.
I've often needed other clock offsets, like CLOCK_REALTIME - CLOCK_MONOTONIC.
Those don't have a character device, and so there is no way to call
ioctl() on them. That is why I'd like to have a system call that
handles any two clock_t instances, using the most accurate back end
based on the kinds of the two clocks.
Thanks,
Richard
prev parent reply other threads:[~2024-01-15 23:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-28 12:24 [PATCH v3] posix-timers: add multi_clock_gettime system call Sagi Maimon
2023-12-29 3:21 ` kernel test robot
2023-12-29 4:03 ` kernel test robot
2023-12-29 15:26 ` Arnd Bergmann
2023-12-31 16:00 ` Sagi Maimon
2024-01-02 11:29 ` Arnd Bergmann
2024-01-07 14:05 ` Sagi Maimon
2024-01-11 7:31 ` Richard Cochran
2024-01-15 15:49 ` Sagi Maimon
2024-01-15 23:41 ` Richard Cochran [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=ZaXCuV1Dy0e_E-h0@hoboy.vegasvil.org \
--to=richardcochran@gmail.com \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=geert@linux-m68k.org \
--cc=hannes@cmpxchg.org \
--cc=hpa@zytor.com \
--cc=keescook@chromium.org \
--cc=legion@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=maimon.sagi@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nphamcs@gmail.com \
--cc=palmer@sifive.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=sohil.mehta@intel.com \
--cc=tglx@linutronix.de \
--cc=x86@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).