From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jason Andryuk <jason.andryuk@amd.com>,
Teddy Astie <teddy.astie@vates.tech>
Cc: Jan Beulich <jbeulich@suse.com>,
xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>,
Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH for-4.21 1/2] x86/AMD: avoid REP MOVSB for Zen3/4
Date: Wed, 8 Oct 2025 13:20:46 +0200 [thread overview]
Message-ID: <aOZJDh9vwbcTwBIy@Mac.lan> (raw)
In-Reply-To: <f42bb989-c9e5-43d5-82e2-9b6f95c008fa@amd.com>
On Mon, Sep 29, 2025 at 07:35:53PM -0400, Jason Andryuk wrote:
> On 2025-09-25 08:18, Teddy Astie wrote:
> > Le 25/09/2025 à 12:48, Jan Beulich a écrit :
> > > Along with Zen2 (which doesn't expose ERMS), both families reportedly
> > > suffer from sub-optimal aliasing detection when deciding whether REP MOVSB
> > > can actually be carried out the accelerated way. Therefore we want to
> > > avoid its use in the common case (memset(), copy_page_hot()).
> >
> > s/memset/memcpy (memset probably uses rep stosb which is not affected IIUC)
> >
> > >
> > > Reported-by: Andrew Cooper <andrew.cooper3@citrix.com>
> > > Signed-off-by: Jan Beulich <jbeulich@suse.com>
>
> With Teddy's suggested change:
>
> Reviewed-by: Jason Andryuk <jason.andryuk@amd.com>
Acked-by: Roger Pau Monné <roger.pau@citrix.com>
It would be nice to have some actual figures whether this makes any
difference though. Teddy, I think Vates had been doing some testing
in this regard, do you think you could measure whether the patch makes
any noticeable difference in PV network traffic for example? (as
that's a heavy user of grant copy).
Thanks, Roger.
next prev parent reply other threads:[~2025-10-08 11:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-25 10:45 [PATCH 0/2] x86: ERMS follow-on Jan Beulich
2025-09-25 10:46 ` [PATCH for-4.21 1/2] x86/AMD: avoid REP MOVSB for Zen3/4 Jan Beulich
2025-09-25 12:18 ` Teddy Astie
2025-09-25 12:58 ` Jan Beulich
2025-09-30 13:03 ` Teddy Astie
2025-10-07 12:19 ` Jan Beulich
2025-09-29 23:35 ` Jason Andryuk
2025-10-08 11:20 ` Roger Pau Monné [this message]
2025-10-08 16:06 ` Jan Beulich
2025-10-09 7:20 ` Oleksii Kurochko
2025-10-08 16:33 ` Andrew Cooper
2025-10-09 7:27 ` Jan Beulich
2025-09-25 10:48 ` [PATCH 2/2] x86: guard synthetic feature and bug enumerators Jan Beulich
2025-09-29 23:36 ` Jason Andryuk
2025-10-07 12:22 ` Jan Beulich
2025-10-07 19:38 ` Jason Andryuk
2025-10-08 5:56 ` Jan Beulich
2025-10-11 0:30 ` Jason Andryuk
2025-10-13 6:39 ` Jan Beulich
2025-10-08 17:19 ` Andrew Cooper
2025-10-09 7:45 ` Jan Beulich
2025-10-09 7:51 ` Jan Beulich
2025-10-13 13:06 ` [PATCH for-4.21 v2] x86/AMD: avoid REP MOVSB for Zen3/4 Jan Beulich
[not found] ` <693449f18cc4480ea2cb2161a9361354@DM4PR03MB7015.namprd03.prod.outlook.com>
2026-01-06 21:07 ` Andrew Cooper
2026-01-07 7:22 ` Jan Beulich
2026-01-07 10:42 ` Andrew Cooper
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=aOZJDh9vwbcTwBIy@Mac.lan \
--to=roger.pau@citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=jbeulich@suse.com \
--cc=oleksii.kurochko@gmail.com \
--cc=teddy.astie@vates.tech \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.