From: Thomas Gleixner <tglx@kernel.org>
To: Mani Tofigh <mt4022@columbia.edu>,
Mani Tofigh via B4 Relay <devnull+mt4022.columbia.edu@kernel.org>,
John Stultz <jstultz@google.com>
Cc: Stephen Boyd <sboyd@kernel.org>,
Miroslav Lichvar <mlichvar@redhat.com>,
Srikanth Aithal <Srikanth.Aithal@amd.com>,
Borislav Petkov <bp@alien8.de>,
K Prateek Nayak <kprateek.nayak@amd.com>,
linux-kernel@vger.kernel.org, tz2294@columbia.edu,
stable@vger.kernel.org
Subject: Re: [PATCH] clocksource: Use the clocksource under test for the skew check timeout
Date: Fri, 06 Nov 2026 21:35:36 +0100 [thread overview]
Message-ID: <87zevlwvdz.ffs@fw13> (raw)
In-Reply-To: <d16c6038-f03a-4e1b-9691-1ae36650f39c@columbia.edu>
On Thu, Nov 05 2026 at 15:22, Mani Tofigh wrote:
> On 11/3/26 3:20 PM, Thomas Gleixner wrote:
>> So your reproducer does:
>>
>> while true; do echo 0 >/sys/devices/system/cpu/cpu1/online; echo 1 >/sys/devices/system/cpu/cpu1/online; done
>>
>> right?
>>
> Yes, but on a kernel booted with clocksource=jiffies.
I did so too and it did not happen within a couple of hours :(
>> Can you and Srikanth please run that on top to validate that we don't
>> end up with that?
> I ran my patch with your delta in the same guest and it holds up well.
> No hang and no "stalled" warning (even though the remote read timed out
> a lot during the loop).
>
> Do you want the delta in v2? I can carry it as a separate patch from you
> or fold it into mine, whatever you prefer.
Just fold it in. It makes sense in that context.
Thanks,
tglx
prev parent reply other threads:[~2026-11-06 20:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-02 21:45 [PATCH] clocksource: Use the clocksource under test for the skew check timeout Mani Tofigh
2026-11-02 21:45 ` Mani Tofigh via B4 Relay
2026-11-03 20:20 ` Thomas Gleixner
2026-11-04 10:38 ` Aithal, Srikanth
2026-11-05 20:22 ` Mani Tofigh
2026-11-06 20:35 ` Thomas Gleixner [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=87zevlwvdz.ffs@fw13 \
--to=tglx@kernel.org \
--cc=Srikanth.Aithal@amd.com \
--cc=bp@alien8.de \
--cc=devnull+mt4022.columbia.edu@kernel.org \
--cc=jstultz@google.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=mt4022@columbia.edu \
--cc=sboyd@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tz2294@columbia.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.