From: John David Anglin <dave.anglin@bell.net>
To: matoro <matoro_mailinglist_kernel@matoro.tk>
Cc: Magnus Lindholm <linmag7@gmail.com>,
Linux Parisc <linux-parisc@vger.kernel.org>,
deller@kernel.org, Deller <deller@gmx.de>,
Sam James <sam@gentoo.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [bisected] ext4 corruption on parisc since 6.12
Date: Tue, 3 Dec 2024 11:38:52 -0500 [thread overview]
Message-ID: <7551c27f-58d5-4e4b-ac7f-8d09be634104@bell.net> (raw)
In-Reply-To: <7e3682f8-ec11-40b0-898f-f3729d6f110b@bell.net>
On 2024-12-02 2:45 p.m., John David Anglin wrote:
> I also have in config:
> CONFIG_HAVE_UNSTABLE_SCHED_CLOCK=y
Here is a comment from <https://www.kernel.org/doc/Documentation/timers/timekeeping.txt>:
On SMP systems, it is crucial for performance that sched_clock() can be called
independently on each CPU without any synchronization performance hits.
Some hardware (such as the x86 TSC) will cause the sched_clock() function to
drift between the CPUs on the system. The kernel can work around this by
enabling the CONFIG_HAVE_UNSTABLE_SCHED_CLOCK option. This is another aspect
that makes sched_clock() different from the ordinary clock source.
Dave
--
John David Anglin dave.anglin@bell.net
prev parent reply other threads:[~2024-12-03 16:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 0:26 matoro
2024-12-02 1:47 ` John David Anglin
2024-12-02 4:55 ` matoro
2024-12-02 6:30 ` Magnus Lindholm
2024-12-02 14:54 ` John David Anglin
2024-12-02 15:31 ` matoro
2024-12-02 16:35 ` Helge Deller
2024-12-02 19:45 ` John David Anglin
2024-12-03 16:38 ` John David Anglin [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=7551c27f-58d5-4e4b-ac7f-8d09be634104@bell.net \
--to=dave.anglin@bell.net \
--cc=deller@gmx.de \
--cc=deller@kernel.org \
--cc=linmag7@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-parisc@vger.kernel.org \
--cc=matoro_mailinglist_kernel@matoro.tk \
--cc=sam@gentoo.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
all inboxes | Powered by JetHome®