mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Bradley Morgan <include@grrlz.net>,
	will@kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC]  [Question] memset.S old code stuff
Date: Tue, 4 Aug 2026 18:20:43 +0100	[thread overview]
Message-ID: <anIfa959Zjws1iJz@J2N7QTR9R3> (raw)
In-Reply-To: <anIMAh8nL5rWS6d9@arm.com>

On Tue, Aug 04, 2026 at 04:57:54PM +0100, Catalin Marinas wrote:
> On Thu, Jul 23, 2026 at 12:17:15AM +0100, Bradley Morgan wrote:
> > Hey folks, sorry for the crazy asm emails, I see that in memset.S in
> > arch/arm64/lib/memset.S, the code is incredibly old code, like 2013 old
> > (heh).
> > 
> > I was wondering if I could say, adapt it from optimized-routines (same
> > treatment as memcpy.S essentially.
> 
> I think Robin attempted until he realised the use of the Q registers in
> the Cortex Strings library, mentioned here:
> 
> https://lore.kernel.org/all/cover.1571073960.git.robin.murphy@arm.com/

We also subsequently looked at moving away from Cortex-strings entirely,
e.g.

  https://lore.kernel.org/linux-arm-kernel/20230314115030.347976-1-mark.rutland@arm.com/

... but there were open questions on the semantics, and no clear path
forwards at the time.

Writing the code isn't the hard part. We need to get wider agreement on
the semantics, test on a variety of platforms, etc.

For now, I think it'd be best to leave as-is, since it's a time sink for
reviewers.

Mark.

  reply	other threads:[~2026-08-04 17:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-22 23:17 Bradley Morgan
2026-08-04 15:57 ` Catalin Marinas
2026-08-04 17:20   ` Mark Rutland [this message]
2026-08-04 17:29     ` Bradley Morgan

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=anIfa959Zjws1iJz@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=include@grrlz.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=will@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

all inboxes | Powered by JetHome®