mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: "Aiqun(Maria) Yu" <quic_aiquny@quicinc.com>
Cc: Will Deacon <will@kernel.org>,
	corbet@lwn.net, catalin.marinas@arm.com, maz@kernel.org,
	quic_pkondeti@quicinc.com, quic_kaushalk@quicinc.com,
	quic_satyap@quicinc.com, quic_shashim@quicinc.com,
	quic_songxue@quicinc.com, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: Add the arm64.nolse_atomics command line option
Date: Thu, 13 Jul 2023 20:08:48 +0100	[thread overview]
Message-ID: <ZLBLwG2LJ4gZLfbh@FVFF77S0Q05N.cambridge.arm.com> (raw)
In-Reply-To: <e02b9969-a3ca-a80d-1d32-25d2bf4c72b6@quicinc.com>

On Thu, Jul 13, 2023 at 10:08:34PM +0800, Aiqun(Maria) Yu wrote:
> On 7/13/2023 7:20 PM, Mark Rutland wrote:
> > Are you saying that LSE atomics to *cacheable* mappings do not work on your
> > system?
> > 
> > Specifically, when using a Normal Inner-Shareable Inner-Writeback
> > Outer-Writeback mapping, do the LSE atomics work or not work?
> *cacheable* mapping have the LSE atomic is not working if far atomic is
> performed.

Thanks for confirming; the fact that this doesn't work on *cacheable* memory is
definitely a major issue. I think everyone is confused here because of the
earlier mention of non-cachable accesses (which don't matter).

I know that some CPU implementations have EL3 control bits to force LSE atomics
to be performed near (e.g. in Cortex-A55, the CPUECTLR.ATOM control bits),
which would avoid the issue while still allowing the LSE atomics to be used.

If those can be configured in EL3 firmware, that would be a preferable
workaround.

Can you say which CPUs are integrated in this system? and/or can you check if
such control bits exist?

Thanks,
Mark.
 

  reply	other threads:[~2023-07-13 19:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-10  5:59 Maria Yu
2023-07-10  6:07 ` Randy Dunlap
2023-07-10  6:13   ` Aiqun(Maria) Yu
2023-07-10  7:27 ` Marc Zyngier
2023-07-10  8:19   ` Aiqun(Maria) Yu
2023-07-10  9:31     ` Marc Zyngier
2023-07-11  3:30       ` Aiqun(Maria) Yu
2023-07-11  6:57         ` Marc Zyngier
2023-07-11 10:12           ` Aiqun(Maria) Yu
2023-07-11 10:38             ` Marc Zyngier
2023-07-12  2:47               ` Aiqun(Maria) Yu
2023-07-12  7:29                 ` Marc Zyngier
2023-07-12  8:03                   ` Aiqun(Maria) Yu
2023-07-10  9:37 ` Will Deacon
2023-07-11  4:02   ` Aiqun(Maria) Yu
2023-07-11  8:22     ` Will Deacon
2023-07-11 10:15       ` Aiqun(Maria) Yu
2023-07-11 10:25         ` Will Deacon
2023-07-12  3:09           ` Aiqun(Maria) Yu
2023-07-12  7:36             ` Mark Rutland
2023-07-13  2:24               ` Aiqun(Maria) Yu
2023-07-13 11:20                 ` Mark Rutland
2023-07-13 14:08                   ` Aiqun(Maria) Yu
2023-07-13 19:08                     ` Mark Rutland [this message]
2023-07-14  1:56                       ` Aiqun(Maria) Yu
2023-07-14  8:23                         ` Will Deacon
2023-07-14 10:12                           ` Aiqun(Maria) Yu
2023-07-14 12:09                             ` Will Deacon
2023-07-17  2:01                               ` Aiqun(Maria) Yu
2023-07-11 10:34         ` Mark Rutland

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=ZLBLwG2LJ4gZLfbh@FVFF77S0Q05N.cambridge.arm.com \
    --to=mark.rutland@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=quic_aiquny@quicinc.com \
    --cc=quic_kaushalk@quicinc.com \
    --cc=quic_pkondeti@quicinc.com \
    --cc=quic_satyap@quicinc.com \
    --cc=quic_shashim@quicinc.com \
    --cc=quic_songxue@quicinc.com \
    --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®