public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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: Tue, 24 Oct 2023 15:00:15 +0200	[thread overview]
Message-ID: <871qdkch0g.ffs@tglx> (raw)
In-Reply-To: <2c822e13-775c-4e55-bf2f-152dbca0c910@I-love.SAKURA.ne.jp>

On Thu, Oct 19 2023 at 23:26, Tetsuo Handa wrote:
> On 2023/10/19 21:14, Thomas Gleixner wrote:
>> Maybe because of this:
>>>>> (This environment is Oracle VM VirtualBox on Windows 11 host.)
>
> I don't think that I'm the only user running Linux on Oracle VM VirtualBox on Windows. ;-)
>
>> So you could boot with "nosmp clocksource=acpi_pm" on the command line
>> and compare that against a "nosmp" boot.
>
> This did not make much difference.

Interesting. Can you please tell what the replacement clocksource is
when the TSC is disabled?

> Just for testing, I booted several Fedora/Ubuntu kernels used by installation ISO image.
> 5.11 / 6.0 / 6.6 Fedora kernels all showed this problem. On the other hand, 5.15 Ubuntu
> kernel does not show this problem. Thus, I'd rather suspect kernel config dependent
> problem than platform dependent problem.
>
> Fedora-Everything-netinst-x86_64-Rawhide-20231018.n.0.iso
> [    0.000000] Linux version 6.6.0-0.rc6.47.fc40.x86_64 (mockbuild@65b4f242683a45f6bd4621fe8c018a9d) (gcc (GCC) 13.2.1 20231011 (Red Hat 13.2.1-4), GNU ld version 2.41-7.fc40) #1 SMP PREEMPT_DYNAMIC Mon Oct 16 13:34:35 UTC 2023
>
> Fedora-Server-netinst-x86_64-37-1.7.iso
> [    0.000000] Linux version 6.0.7-301.fc37.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 12.2.1 20220819 (Red Hat 12.2.1-2), GNU ld version 2.38-24.fc37) #1 SMP PREEMPT_DYNAMIC Fri Nov 4 18:35:48 UTC 2022
>
> Fedora-Everything-netinst-x86_64-34-1.2.iso
> [    0.000000] Linux version 5.11.12-300.fc34.x86_64 (mockbuild@bkernel01.iad2.fedoraproject.org) (gcc (GCC) 11.0.1 20210324 (Red Hat 11.0.1-0), GNU ld version 2.35.1-41.fc34) #1 SMP Wed Apr 7 16:31:13 UTC 2021
>
> ubuntu-22.04.3-live-server-amd64.iso
> [    0.000001] kvm-clock: using sched offset of 33909880646 cycles
> [    0.000004] clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns

Are the others using kvm-clock too? I haven't seen that in the snippets
you provided before.

Thanks,

        tglx



  parent reply	other threads:[~2023-10-24 13:00 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 [this message]
2023-10-24 14:52                 ` Tetsuo Handa
2023-10-25 21:28                   ` Thomas Gleixner
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=871qdkch0g.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