mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter Hilber <peter.hilber@opensynergy.com>
To: linux-kernel@vger.kernel.org
Cc: Peter Hilber <peter.hilber@opensynergy.com>,
	John Stultz <jstultz@google.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	Stephen Boyd <sboyd@kernel.org>,
	"Christopher S. Hall" <christopher.s.hall@intel.com>
Subject: [RFC PATCH 2/7] timekeeping: Fix cross-timestamp interpolation corner case decision
Date: Fri, 30 Jun 2023 19:10:45 +0200	[thread overview]
Message-ID: <20230630171052.985577-3-peter.hilber@opensynergy.com> (raw)
In-Reply-To: <20230630171052.985577-1-peter.hilber@opensynergy.com>

cycle_between() decides whether get_device_system_crosststamp() will
interpolate for older counter readings. So far, cycle_between() checks if
parameter test is in the open interval (before, after), when disregarding
the special case before > after.

The only cycle_between() user, get_device_system_crosststamp(), has the
following problem with this: If interval_start == cycles,
cycle_between(interval_start, cycles, now) returns false. If a
history_begin was supplied to get_device_system_crosststamp(), it will
later call cycle_between() again, with effective argument values
cycle_between(history_begin->cycles, cycles, cycles). Due to the test
against the open interval, cycle_between() returns false again, and
get_device_system_crosststamp() returns -EINVAL, when it could have
succeeded.

Fix this by testing against the closed interval in cycle_between(). This
disables interpolation if interval_start == cycles. For the special case
before > after, similar arguments hold. Fix this in a similar way.

At the second cycle_between() call site, add an extra condition in order to
effectively check a half-open interval, which keeps the condition
documented above the call site satisfied.

Fixes: 2c756feb18d9 ("time: Add history to cross timestamp interface supporting slower devices")
Signed-off-by: Peter Hilber <peter.hilber@opensynergy.com>
---
 kernel/time/timekeeping.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
index 8f35455b6250..7e86d5cd784d 100644
--- a/kernel/time/timekeeping.c
+++ b/kernel/time/timekeeping.c
@@ -1180,13 +1180,13 @@ static int adjust_historical_crosststamp(struct system_time_snapshot *history,
 }
 
 /*
- * cycle_between - true if test occurs chronologically between before and after
+ * cycle_between - true if test occurs chronologically in [before, after]
  */
 static bool cycle_between(u64 before, u64 test, u64 after)
 {
-	if (test > before && test < after)
+	if (test >= before && test <= after)
 		return true;
-	if (before > after && (test > before || test < after))
+	if (before > after && (test >= before || test <= after))
 		return true;
 	return false;
 }
@@ -1282,6 +1282,7 @@ int get_device_system_crosststamp(int (*get_time_fn)
 		 * clocksource change
 		 */
 		if (!history_begin ||
+		    history_begin->cycles == system_counterval.cycles ||
 		    !cycle_between(history_begin->cycles,
 				   system_counterval.cycles, cycles) ||
 		    history_begin->cs_was_changed_seq != cs_was_changed_seq)
-- 
2.39.2


  parent reply	other threads:[~2023-06-30 17:33 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-30 17:10 [RFC PATCH 0/7] Add virtio_rtc module and related changes Peter Hilber
2023-06-30 17:10 ` [RFC PATCH 1/7] timekeeping: Fix cross-timestamp interpolation on counter wrap Peter Hilber
2023-07-07 22:51   ` John Stultz
2023-07-27 10:21     ` Peter Hilber
2023-06-30 17:10 ` Peter Hilber [this message]
2023-07-07 23:02   ` [RFC PATCH 2/7] timekeeping: Fix cross-timestamp interpolation corner case decision John Stultz
2023-07-27 10:21     ` Peter Hilber
2023-06-30 17:10 ` [RFC PATCH 3/7] timekeeping: Fix cross-timestamp interpolation for non-x86 Peter Hilber
2023-07-07 23:31   ` John Stultz
2023-07-27 10:21     ` Peter Hilber
2023-06-30 17:10 ` [RFC PATCH 4/7] clocksource: arm_arch_timer: Export counter type, clocksource Peter Hilber
2023-07-03  8:13   ` Marc Zyngier
2023-07-27 10:22     ` Peter Hilber
2023-07-28  8:11       ` Marc Zyngier
2023-07-31 16:15         ` Peter Hilber
2023-06-30 17:10 ` [RFC PATCH 5/7] virtio_rtc: Add module and driver core Peter Hilber
2023-06-30 17:10 ` [RFC PATCH 6/7] virtio_rtc: Add PTP clocks Peter Hilber
2023-06-30 17:10 ` [RFC PATCH 7/7] virtio_rtc: Add Arm Generic Timer cross-timestamping Peter Hilber

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=20230630171052.985577-3-peter.hilber@opensynergy.com \
    --to=peter.hilber@opensynergy.com \
    --cc=christopher.s.hall@intel.com \
    --cc=jstultz@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sboyd@kernel.org \
    --cc=tglx@linutronix.de \
    /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®