public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: linux-tip-commits@vger.kernel.org,
	Ondrej Lichtner <olichtne@redhat.com>,
	"Herton R. Krzesinski" <herton@redhat.com>,
	x86@kernel.org
Subject: Re: [tip: x86/mm] x86/uaccess: Improve performance by aligning writes to 8 bytes in copy_user_generic(), on non-FSRM/ERMS CPUs
Date: Fri, 28 Mar 2025 22:47:46 +0100	[thread overview]
Message-ID: <Z-cZAmfQqXi3bw2c@gmail.com> (raw)
In-Reply-To: <174319666347.14745.18304475049279156644.tip-bot2@tip-bot2>


* tip-bot2 for Herton R. Krzesinski <tip-bot2@linutronix.de> wrote:

> The following commit has been merged into the x86/mm branch of tip:
> 
> Commit-ID:     411d2763b3ba0e3a99cd27ce813738d530b2320d
> Gitweb:        https://git.kernel.org/tip/411d2763b3ba0e3a99cd27ce813738d530b2320d
> Author:        Herton R. Krzesinski <herton@redhat.com>
> AuthorDate:    Thu, 20 Mar 2025 11:22:13 -03:00
> Committer:     Ingo Molnar <mingo@kernel.org>
> CommitterDate: Fri, 28 Mar 2025 21:56:49 +01:00
> 
> x86/uaccess: Improve performance by aligning writes to 8 bytes in copy_user_generic(), on non-FSRM/ERMS CPUs
> 
> History of the performance regression:
> ======================================
> 
> Since the a series of user copy updates were merged upstream
        ^^^^^
> ~2 years ago via:

That was my mistake in a last-minute edit to the changelog.
I force-pushed a fix:

  |  Since the following series of user copy updates were merged upstream
  |  ~2 years ago via:

Thanks,

	Ingo

  reply	other threads:[~2025-03-28 21:47 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20 14:22 [PATCH] x86: write aligned to 8 bytes in copy_user_generic (when without FSRM/ERMS) Herton R. Krzesinski
2025-03-20 14:35 ` Mateusz Guzik
2025-03-20 17:51   ` Herton Krzesinski
2025-03-20 18:02     ` Mateusz Guzik
2025-03-20 18:37       ` Herton Krzesinski
2025-03-20 21:31       ` David Laight
2025-03-28 21:17 ` [tip: x86/mm] x86/uaccess: Improve performance by aligning writes to 8 bytes in copy_user_generic(), on non-FSRM/ERMS CPUs tip-bot2 for Herton R. Krzesinski
2025-03-28 21:47   ` Ingo Molnar [this message]
2025-03-28 21:53 ` [tip: x86/urgent] " tip-bot2 for Herton R. Krzesinski
2025-03-28 22:04 ` tip-bot2 for Herton R. Krzesinski
2025-03-28 22:11   ` Ingo Molnar
2025-05-02  6:19 ` [PATCH] x86: write aligned to 8 bytes in copy_user_generic (when without FSRM/ERMS) Nicholas Sielicki

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=Z-cZAmfQqXi3bw2c@gmail.com \
    --to=mingo@kernel.org \
    --cc=herton@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tip-commits@vger.kernel.org \
    --cc=olichtne@redhat.com \
    --cc=x86@kernel.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