From: Thomas Gleixner <tglx@linutronix.de>
To: "Mahesh Bandewar (महेश बंडेवार)" <maheshb@google.com>
Cc: Sagi Maimon <maimon.sagi@gmail.com>,
richardcochran@gmail.com, luto@kernel.org, mingo@redhat.com,
bp@alien8.de, dave.hansen@linux.intel.com, x86@kernel.org,
hpa@zytor.com, arnd@arndb.de, geert@linux-m68k.org,
peterz@infradead.org, hannes@cmpxchg.org, sohil.mehta@intel.com,
rick.p.edgecombe@intel.com, nphamcs@gmail.com, palmer@sifive.com,
keescook@chromium.org, legion@kernel.org, mark.rutland@arm.com,
mszeredi@redhat.com, casey@schaufler-ca.com, reibax@gmail.com,
davem@davemloft.net, brauner@kernel.org,
linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
linux-arch@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: [PATCH v7] posix-timers: add clock_compare system call
Date: Wed, 03 Apr 2024 17:42:07 +0200 [thread overview]
Message-ID: <87v84ybghc.ffs@tglx> (raw)
In-Reply-To: <871q7md0ak.ffs@tglx>
On Wed, Apr 03 2024 at 15:48, Thomas Gleixner wrote:
> On Tue, Apr 02 2024 at 16:37, Mahesh Bandewar (महेश बंडेवार) wrote:
> It is just an implementation detail whether you use a flag or a
> clockid. You can carry the clockid for the clocks which actually can be
> read in that context in a reserved field of PTP_SYS_OFFSET_EXTENDED:
>
> struct ptp_sys_offset_extended {
> unsigned int n_samples; /* Desired number of measurements. */
> clockid_t clockid;
> unsigned int rsv[2]; /* Reserved for future use. */
> };
>
> and in the IOCTL:
>
> if (extoff->clockid != CLOCK_MONOTONIC_RAW)
> return -EINVAL;
That should obviously be:
switch (extoff->clockid) {
case CLOCK_REALTIME:
case CLOCK_MONOTONIC_RAW:
break;
default:
return -EINVAL;
}
...
> sts.clockid = extoff->clockid;
>
> and it all just works, no?
>
> I have no problem to decide that PTP_SYS_OFFSET will not get this
> treatment and the drivers have to be converted over to
> PTP_SYS_OFFSET_EXTENDED.
>
> But adding yet another callback just to carry a clockid as argument is a
> more than pointless exercise as I demonstrated.
>
> Thanks,
>
> tglx
next prev parent reply other threads:[~2024-04-03 15:42 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-14 9:05 [PATCH v7] posix-timers: add clock_compare system call Sagi Maimon
2024-03-14 11:12 ` Thomas Gleixner
2024-03-14 12:19 ` Sagi Maimon
2024-03-14 15:59 ` Mark Rutland
2024-03-14 18:08 ` Thomas Gleixner
2024-03-20 14:42 ` Sagi Maimon
2024-03-23 0:38 ` Thomas Gleixner
2024-03-23 0:42 ` Thomas Gleixner
2024-03-24 11:04 ` Kurt Kanzenbach
2024-03-28 15:40 ` Sagi Maimon
2024-04-01 20:46 ` Thomas Gleixner
2024-04-02 5:42 ` Mahesh Bandewar (महेश बंडेवार)
2024-04-02 9:24 ` Thomas Gleixner
2024-04-02 21:16 ` Mahesh Bandewar (महेश बंडेवार)
2024-04-02 22:37 ` Thomas Gleixner
2024-04-02 23:37 ` Mahesh Bandewar (महेश बंडेवार)
2024-04-03 13:48 ` Thomas Gleixner
2024-04-03 15:42 ` Thomas Gleixner [this message]
2024-04-11 2:55 ` Mahesh Bandewar (महेश बंडेवार)
2024-04-11 7:11 ` Sagi Maimon
2024-04-11 16:33 ` Mahesh Bandewar (महेश बंडेवार)
2024-04-14 12:22 ` Sagi Maimon
2024-04-15 17:23 ` Mahesh Bandewar (महेश बंडेवार)
2024-04-16 8:39 ` Sagi Maimon
2024-03-14 15:46 ` Sagi Maimon
2024-03-14 18:42 ` Thomas Gleixner
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=87v84ybghc.ffs@tglx \
--to=tglx@linutronix.de \
--cc=arnd@arndb.de \
--cc=bp@alien8.de \
--cc=brauner@kernel.org \
--cc=casey@schaufler-ca.com \
--cc=dave.hansen@linux.intel.com \
--cc=davem@davemloft.net \
--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=maheshb@google.com \
--cc=maimon.sagi@gmail.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=mszeredi@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=nphamcs@gmail.com \
--cc=palmer@sifive.com \
--cc=peterz@infradead.org \
--cc=reibax@gmail.com \
--cc=richardcochran@gmail.com \
--cc=rick.p.edgecombe@intel.com \
--cc=sohil.mehta@intel.com \
--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 NNTP newsgroup(s).