public inbox for glibc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org> To: glibc-bugs@sourceware.org Subject: [Bug libc/28033] New: Need to check RTM_ALWAYS_ABORT for RTM Date: Wed, 30 Jun 2021 17:34:09 +0000 [thread overview] Message-ID: <bug-28033-131@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=28033 Bug ID: 28033 Summary: Need to check RTM_ALWAYS_ABORT for RTM Product: glibc Version: 2.34 Status: NEW Severity: normal Priority: P2 Component: libc Assignee: unassigned at sourceware dot org Reporter: hjl.tools at gmail dot com CC: drepper.fsp at gmail dot com Target Milestone: --- Target: i386,x86-64 From https://www.intel.com/content/www/us/en/support/articles/000059422/processors.html A new CPUID bit CPUID.07H.0H.EDX[11](RTM_ALWAYS_ABORT) will be enumerated, which is set to indicate to updated software that the loaded microcode is forcing RTM abort. We need to check RTM_ALWAYS_ABORT to verify that if RTM is usable. -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2021-06-30 17:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-06-30 17:34 hjl.tools at gmail dot com [this message] 2021-07-01 17:53 ` [Bug libc/28033] " cvs-commit at gcc dot gnu.org 2021-07-01 18:07 ` hjl.tools at gmail dot com 2022-02-01 14:08 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:26 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:36 ` cvs-commit at gcc dot gnu.org 2022-02-01 15:59 ` cvs-commit at gcc dot gnu.org 2022-02-01 16:06 ` cvs-commit at gcc dot gnu.org 2022-02-01 17:16 ` cvs-commit at gcc dot gnu.org
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-28033-131@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).