public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Florian Weimer <fweimer@redhat.com>
To: Adhemerval Zanella <adhemerval.zanella@linaro.org>
Cc: libc-alpha@sourceware.org,  "H . J . Lu" <hjl.tools@gmail.com>,
	 Noah Goldstein <goldstein.w.n@gmail.com>,
	 Sajan Karumanchi <sajan.karumanchi@gmail.com>,
	 bmerry@sarao.ac.za,  pmallapp@amd.com,
	Michael Hudson-Doyle <michael.hudson@canonical.com>,
	Simon Chopin <simon.chopin@canonical.com>
Subject: Re: [PATCH v3 0/3] x86: Improve ERMS usage on Zen3+
Date: Mon, 25 Mar 2024 16:15:47 +0100	[thread overview]
Message-ID: <87il1a8hr0.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <20240208130840.533348-1-adhemerval.zanella@linaro.org> (Adhemerval Zanella's message of "Thu, 8 Feb 2024 10:08:37 -0300")

* Adhemerval Zanella:

> Adhemerval Zanella (3):
>   x86: Fix Zen3/Zen4 ERMS selection (BZ 30994)
>   x86: Do not prefer ERMS for memset on Zen3+
>   x86: Expand the comment on when REP STOSB is used on memset
>
>  sysdeps/x86/dl-cacheinfo.h                    | 43 ++++++++++---------
>  .../multiarch/memset-vec-unaligned-erms.S     |  4 +-
>  2 files changed, 26 insertions(+), 21 deletions(-)

Should we backport this into release branches?

This issue was first raised as an Ubuntu downstream bug, so maybe they'd
appreciate a backport for this?  We want this backport in Fedora, so it
would help us, too.

Thanks,
Florian


  parent reply	other threads:[~2024-03-25 15:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-08 13:08 Adhemerval Zanella
2024-02-08 13:08 ` [PATCH v3 1/3] x86: Fix Zen3/Zen4 ERMS selection (BZ 30994) Adhemerval Zanella
2024-02-12 15:56   ` H.J. Lu
2024-02-08 13:08 ` [PATCH v3 2/3] x86: Do not prefer ERMS for memset on Zen3+ Adhemerval Zanella
2024-02-12 15:56   ` H.J. Lu
2024-02-08 13:08 ` [PATCH v3 3/3] x86: Expand the comment on when REP STOSB is used on memset Adhemerval Zanella
2024-02-12 15:56   ` H.J. Lu
2024-03-25 15:15 ` Florian Weimer [this message]
2024-03-25 15:19   ` [PATCH v3 0/3] x86: Improve ERMS usage on Zen3+ H.J. Lu

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=87il1a8hr0.fsf@oldenburg.str.redhat.com \
    --to=fweimer@redhat.com \
    --cc=adhemerval.zanella@linaro.org \
    --cc=bmerry@sarao.ac.za \
    --cc=goldstein.w.n@gmail.com \
    --cc=hjl.tools@gmail.com \
    --cc=libc-alpha@sourceware.org \
    --cc=michael.hudson@canonical.com \
    --cc=pmallapp@amd.com \
    --cc=sajan.karumanchi@gmail.com \
    --cc=simon.chopin@canonical.com \
    /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).