public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/30428] New AMD cache size computation logic does not work for some CPUs, hypervisors
Date: Thu, 14 Sep 2023 20:48:36 +0000 [thread overview]
Message-ID: <bug-30428-131-KTIUQlu5lH@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-30428-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=30428
Florian Weimer <fweimer at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|--- |2.39
--- Comment #4 from Florian Weimer <fweimer at redhat dot com> ---
Fixed for 2.39 via:
commit dcad5c8578130dec7f35fd5b0885304b59f9f543
Author: Sajan Karumanchi <sajan.karumanchi@amd.com>
Date: Tue Aug 1 15:20:55 2023 +0000
x86: Fix for cache computation on AMD legacy cpus.
Some legacy AMD CPUs and hypervisors have the _cpuid_ '0x8000_001D'
set to Zero, thus resulting in zeroed-out computed cache values.
This patch reintroduces the old way of cache computation as a
fail-safe option to handle these exceptions.
Fixed 'level4_cache_size' value through handle_amd().
Reviewed-by: Premachandra Mallappa <premachandra.mallappa@amd.com>
Tested-by: Florian Weimer <fweimer@redhat.com>
It seems that we are still missing the backport to 2.37.
--
You are receiving this mail because:
You are on the CC list for the bug.
prev parent reply other threads:[~2023-09-14 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:42 [Bug dynamic-link/30428] New: " fw at deneb dot enyo.de
2023-05-08 17:03 ` [Bug dynamic-link/30428] " fweimer at redhat dot com
2023-05-08 17:09 ` fweimer at redhat dot com
2023-05-08 20:29 ` fweimer at redhat dot com
2023-05-09 14:55 ` jamborm at gcc dot gnu.org
2023-06-11 17:52 ` sam at gentoo dot org
2023-07-04 17:34 ` fweimer at redhat dot com
2023-09-14 20:33 ` jamborm at gcc dot gnu.org
2023-09-14 20:48 ` fweimer at redhat dot com [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=bug-30428-131-KTIUQlu5lH@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).