From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Dave Hansen <dave.hansen@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de, x86@kernel.org,
bp@alien8.de, stable@vger.kernel.org
Subject: Re: [PATCH] x86/cpu: Provide default cache line size if not enumerated
Date: Thu, 30 May 2024 17:13:28 +0300 [thread overview]
Message-ID: <ZliJiM8g5p-uJSPd@smile.fi.intel.com> (raw)
In-Reply-To: <ZkspXhQFcWvBkL2q@smile.fi.intel.com>
On Mon, May 20, 2024 at 01:43:42PM +0300, Andy Shevchenko wrote:
> On Fri, May 17, 2024 at 01:05:34PM -0700, Dave Hansen wrote:
> >
> > From: Dave Hansen <dave.hansen@linux.intel.com>
> >
> > tl;dr: CPUs with CPUID.80000008H but without CPUID.01H:EDX[CLFSH]
> > will end up reporting cache_line_size()==0 and bad things happen.
> > Fill in a default on those to avoid the problem.
> >
> > Long Story:
> >
> > The kernel dies a horrible death if c->x86_cache_alignment (aka.
> > cache_line_size() is 0. Normally, this value is populated from
>
> Missing ) ?
>
> > c->x86_clflush_size.
> >
> > Right now the code is set up to get c->x86_clflush_size from two
> > places. First, modern CPUs get it from CPUID. Old CPUs that don't
> > have leaf 0x80000008 (or CPUID at all) just get some sane defaults
> > from the kernel in get_cpu_address_sizes().
> >
> > The vast majority of CPUs that have leaf 0x80000008 also get
> > ->x86_clflush_size from CPUID. But there are oddballs.
> >
> > Intel Quark CPUs[1] and others[2] have leaf 0x80000008 but don't set
> > CPUID.01H:EDX[CLFSH], so they skip over filling in ->x86_clflush_size:
> >
> > cpuid(0x00000001, &tfms, &misc, &junk, &cap0);
> > if (cap0 & (1<<19))
> > c->x86_clflush_size = ((misc >> 8) & 0xff) * 8;
> >
> > So they: land in get_cpu_address_sizes(), set vp_bits_from_cpuid=0 and
> > never fill in c->x86_clflush_size, assign c->x86_cache_alignment, and
> > hilarity ensues in code like:
> >
> > buffer = kzalloc(ALIGN(sizeof(*buffer), cache_line_size()),
> > GFP_KERNEL);
> >
> > To fix this, always provide a sane value for ->x86_clflush_size.
> >
> > Big thanks to Andy Shevchenko for finding and reporting this and also
> > providing a first pass at a fix. But his fix was only partial and only
> > worked on the Quark CPUs. It would not, for instance, have worked on
> > the QEMU config.
> >
> > 1. https://raw.githubusercontent.com/InstLatx64/InstLatx64/master/GenuineIntel/GenuineIntel0000590_Clanton_03_CPUID.txt
> > 2. You can also get this behavior if you use "-cpu 486,+clzero"
> > in QEMU.
>
> Tested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> (as this obviously fixes the issue as it makes a partial revert of the culprit
> change).
What's the status of this? (It seems you have to rebase it on top of the
existing patches in the same area).
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-05-30 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-17 20:05 [PATCH] x86/cpu: Provide default cache line size if not enumerated Dave Hansen
2024-05-20 10:43 ` Andy Shevchenko
2024-05-30 14:13 ` Andy Shevchenko [this message]
2024-05-30 14:16 ` Dave Hansen
2024-05-30 15:04 ` Andy Shevchenko
2024-05-30 9:47 ` Jörn Heusipp
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=ZliJiM8g5p-uJSPd@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=bp@alien8.de \
--cc=dave.hansen@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tglx@linutronix.de \
--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