public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: Noah Goldstein <goldstein.w.n@gmail.com>,
	"H.J. Lu" <hjl.tools@gmail.com>
Cc: libc-alpha <libc-alpha@sourceware.org>, toolchain@gentoo.org
Subject: Re: [2.33] FAIL: string/tst-memset-rtm
Date: Tue, 01 Feb 2022 21:40:50 +0100	[thread overview]
Message-ID: <110578597.nniJfEyVGO@pinacolada> (raw)
In-Reply-To: <CAMe9rOqA64aRsSvDqTMPZQBct8AaqApE7C5CbF0cMf7CdVa+8w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1002 bytes --]

Am Dienstag, 1. Februar 2022, 15:09:42 CET schrieb H.J. Lu:
> On Tue, Feb 1, 2022 at 12:04 AM Noah Goldstein <goldstein.w.n@gmail.com> wrote:
> >
> > On Tue, Feb 1, 2022 at 1:30 AM Andreas K. Huettel via Libc-alpha
> > <libc-alpha@sourceware.org> wrote:
> > >
> > > > > FAIL: string/tst-memset-rtm
> > > > >
> > > > > tst-memset-rtm.out says
> > > > > error: ../sysdeps/x86/tst-string-rtm.h:63: TSX abort rate: 100.00% (3000 out of 3000)
> > > > > error: 1 test failures
> > > > >

> 
> Should be fixed by these backports:
> 
> 1b8f2456b9 x86: Use CHECK_FEATURE_PRESENT to check HLE [BZ #27398]
> 54fdfa2b33 x86: Black list more Intel CPUs for TSX [BZ #27398]
> 0a5f5e2dc1 x86: Check RTM_ALWAYS_ABORT for RTM [BZ #28033]
> 5cb6edb6cd x86: Copy IBT and SHSTK usable only if CET is enabled
> 

Confirmed, with these four commits things are fine. Thank you!

-- 
Andreas K. Hüttel
dilfridge@gentoo.org
Gentoo Linux developer
(council, toolchain, base-system, perl, libreoffice)

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 981 bytes --]

      reply	other threads:[~2022-02-01 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 22:56 Andreas K. Huettel
2022-01-31 23:36 ` H.J. Lu
2022-02-01  7:29   ` Andreas K. Huettel
2022-02-01  8:04     ` Noah Goldstein
2022-02-01 14:09       ` H.J. Lu
2022-02-01 20:40         ` Andreas K. Huettel [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=110578597.nniJfEyVGO@pinacolada \
    --to=dilfridge@gentoo.org \
    --cc=goldstein.w.n@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=toolchain@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).