public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "decui at microsoft dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/30037] glibc 2.34 and newer segfault if CPUID leaf 0x2 reports zero Date: Tue, 24 Jan 2023 04:03:55 +0000 [thread overview] Message-ID: <bug-30037-131-jb4OB0AwPm@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-30037-131@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=30037 Dexuan Cui <decui at microsoft dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |decui at microsoft dot com --- Comment #1 from Dexuan Cui <decui at microsoft dot com> --- I'm reading "Intel® 64 and IA-32 Architectures Software Developer’s Manual Volume 2A: Instruction Set Reference, A-L" for the definition of CPUID leaf 0x2: " INPUT EAX = 02H: TLB/Cache/Prefetch Information Returned in EAX, EBX, ECX, EDX When CPUID executes with EAX set to 02H, the processor returns information about the processor’s internal TLBs, cache and prefetch hardware in the EAX, EBX, ECX, and EDX registers. The information is reported in encoded form and fall into the following categories: • The least-significant byte in register EAX (register AL) will always return 01H. Software should ignore this value and not interpret it as an informational descriptor. • The most significant bit (bit 31) of each register indicates whether the register contains valid information (set to 0) or is reserved (set to 1). • If a register contains valid information, the information is contained in 1 byte descriptors. There are four types of encoding values for the byte descriptor, the encoding type is noted in the second column of Table 3-12. Table 3-12 lists the encoding of these descriptors. Note that the order of descriptors in the EAX, EBX, ECX, and EDX registers is not defined; that is, specific bytes are not designated to contain descriptors for specific cache, prefetch, or TLB types. The descriptors may appear in any order. Note also a processor may report a general descriptor type (FFH) and not report any byte descriptor of “cache type” via CPUID leaf 2. " -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2023-01-24 4:03 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-01-24 3:48 [Bug libc/30037] New: " decui at microsoft dot com 2023-01-24 4:03 ` decui at microsoft dot com [this message] 2023-01-24 4:18 ` [Bug libc/30037] " decui at microsoft dot com 2023-01-25 20:35 ` goldstein.w.n at gmail dot com 2023-01-27 18:13 ` hjl.tools at gmail dot com 2023-02-24 16:27 ` ayi at janestreet dot com 2023-02-24 16:29 ` ayi at janestreet dot com 2023-03-13 12:16 ` ioanna.alifieraki at gmail dot com 2023-03-13 17:59 ` fweimer at redhat dot com 2023-07-17 7:29 ` fweimer at redhat dot com
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-30037-131-jb4OB0AwPm@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: linkBe 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).