From: Thomas Gleixner <tglx@linutronix.de>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>, paulmck@kernel.org
Cc: John Stultz <jstultz@google.com>, Stephen Boyd <sboyd@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
x86@kernel.org, joel@joelfernandes.org
Subject: Re: [PATCH] clocksource: disable irq when holding watchdog_lock.
Date: Wed, 25 Oct 2023 23:28:49 +0200 [thread overview]
Message-ID: <8734xy5r3i.ffs@tglx> (raw)
In-Reply-To: <a1f1ec27-169a-4853-84d0-7d67d62a7741@I-love.SAKURA.ne.jp>
On Tue, Oct 24 2023 at 23:52, Tetsuo Handa wrote:
> On 2023/10/24 22:00, Thomas Gleixner wrote:
>> Interesting. Can you please tell what the replacement clocksource is
>> when the TSC is disabled?
>
> Where can I find the replacement clocksource from?
/sys/kernel/devices/system/clocksource/clocksource0/active_clocksource
but I already figured it out. It selects kvm_clock as fallback, but that
happens way later. At that point during AP bringup timekeeping is still
based on jiffies. So that TSC unstable marking is not an issue
vs. timekeeping.
I have no idea what the kernel, VirtualPox or Windoze are doing during
that time. I fear you need to add some debug on your own or if
VirtualPox has a monitor/debugger you might use that to inspect what the
guest is doing.
Thanks,
tglx
next prev parent reply other threads:[~2023-10-25 21:28 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-13 14:51 [PATCH] clocksource: disable irq when holding watchdog_lock Tetsuo Handa
2023-10-16 17:46 ` John Stultz
2023-10-16 21:47 ` Thomas Gleixner
2023-10-16 23:03 ` Paul E. McKenney
2023-10-17 6:49 ` Thomas Gleixner
2023-10-17 14:11 ` Paul E. McKenney
2023-10-17 10:37 ` Tetsuo Handa
2023-10-17 14:10 ` Paul E. McKenney
2023-10-19 9:30 ` Tetsuo Handa
2023-10-19 12:14 ` Thomas Gleixner
2023-10-19 14:26 ` Tetsuo Handa
2023-10-20 3:30 ` Paul E. McKenney
2023-10-20 12:50 ` Tetsuo Handa
2023-10-20 13:40 ` Paul E. McKenney
2023-10-24 13:00 ` Thomas Gleixner
2023-10-24 14:52 ` Tetsuo Handa
2023-10-25 21:28 ` Thomas Gleixner [this message]
2023-10-25 21:31 ` [PATCH] x86/tsc: Defer marking TSC unstable to a worker Thomas Gleixner
2023-10-26 9:39 ` [tip: x86/urgent] " tip-bot2 for Thomas Gleixner
2023-10-27 18:46 ` tip-bot2 for Thomas Gleixner
2023-10-20 9:02 ` [PATCH] clocksource: disable irq when holding watchdog_lock Sebastian Andrzej Siewior
2023-10-26 2:33 ` kernel test robot
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=8734xy5r3i.ffs@tglx \
--to=tglx@linutronix.de \
--cc=bigeasy@linutronix.de \
--cc=joel@joelfernandes.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=sboyd@kernel.org \
--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