From: "H.J. Lu" <hjl.tools@gmail.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
libc-alpha@sourceware.org,
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 08:19:07 -0700 [thread overview]
Message-ID: <CAMe9rOpqdtE117FggvoYxAXDeqe2K6Ui3DOMC87xTBBfVV=WkA@mail.gmail.com> (raw)
In-Reply-To: <87il1a8hr0.fsf@oldenburg.str.redhat.com>
On Mon, Mar 25, 2024 at 8:15 AM Florian Weimer <fweimer@redhat.com> wrote:
>
> * 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?
Yes.
> 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
>
--
H.J.
prev parent reply other threads:[~2024-03-25 15:19 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 ` [PATCH v3 0/3] x86: Improve ERMS usage on Zen3+ Florian Weimer
2024-03-25 15:19 ` H.J. Lu [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='CAMe9rOpqdtE117FggvoYxAXDeqe2K6Ui3DOMC87xTBBfVV=WkA@mail.gmail.com' \
--to=hjl.tools@gmail.com \
--cc=adhemerval.zanella@linaro.org \
--cc=bmerry@sarao.ac.za \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@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).