From: Peter Hilber <peter.hilber@opensynergy.com>
To: John Stultz <jstultz@google.com>
Cc: linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
"Christopher S. Hall" <christopher.s.hall@intel.com>
Subject: Re: [RFC PATCH 1/7] timekeeping: Fix cross-timestamp interpolation on counter wrap
Date: Thu, 27 Jul 2023 12:21:38 +0200 [thread overview]
Message-ID: <acab57a7-3aab-11bc-6102-bc2e93cf9ecd@opensynergy.com> (raw)
In-Reply-To: <CANDhNCpaoRRKGz0XxV3zjA-ux66gU-dT_bGQ_OqDh4ty=VdXLQ@mail.gmail.com>
On 08.07.23 00:51, John Stultz wrote:
> On Fri, Jun 30, 2023 at 10:12 AM Peter Hilber
> <peter.hilber@opensynergy.com> wrote:
>>
>> cycle_between() decides whether get_device_system_crosststamp() will
>> interpolate for older counter readings.
>>
>> cycle_between() yields wrong results for a counter wrap-around where after
>> < before < test, and for the case after < test < before.
>>
>> Fix the comparison logic.
>>
>> 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 | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/kernel/time/timekeeping.c b/kernel/time/timekeeping.c
>> index 266d02809dbb..8f35455b6250 100644
>> --- a/kernel/time/timekeeping.c
>> +++ b/kernel/time/timekeeping.c
>> @@ -1186,7 +1186,7 @@ static bool cycle_between(u64 before, u64 test, u64 after)
>> {
>> if (test > before && test < after)
>> return true;
>> - if (test < before && before > after)
>> + if (before > after && (test > before || test < after))
>> return true;
>> return false;
>> }
>
> Thanks for catching this and sending it in.
> Looks good to me. Curious: Did you actually hit such a wrap around with u64s?
No, I just saw this when fixing the bug in the next patch.
Thanks,
Peter
next prev parent reply other threads:[~2023-07-27 10:21 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 [this message]
2023-06-30 17:10 ` [RFC PATCH 2/7] timekeeping: Fix cross-timestamp interpolation corner case decision Peter Hilber
2023-07-07 23:02 ` 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=acab57a7-3aab-11bc-6102-bc2e93cf9ecd@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®