From: Will Deacon <will@kernel.org>
To: Maria Yu <quic_aiquny@quicinc.com>
Cc: 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: Mon, 10 Jul 2023 10:37:52 +0100 [thread overview]
Message-ID: <20230710093751.GC32673@willie-the-truck> (raw)
In-Reply-To: <20230710055955.36551-1-quic_aiquny@quicinc.com>
On Mon, Jul 10, 2023 at 01:59:55PM +0800, Maria Yu wrote:
> In order to be able to disable lse_atomic even if cpu
> support it, most likely because of memory controller
> cannot deal with the lse atomic instructions, use a
> new idreg override to deal with it.
This should not be a problem for cacheable memory though, right?
Given that Linux does not issue atomic operations to non-cacheable mappings,
I'm struggling to see why there's a problem here.
Please can you explain the problem that you are trying to solve?
Will
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-07-10 9:38 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-10 5:59 [PATCH] arm64: Add the arm64.nolse_atomics command line option 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 [this message]
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
2023-07-14 1:56 ` Aiqun(Maria) Yu
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 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=20230710093751.GC32673@willie-the-truck \
--to=will@kernel.org \
--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 \
/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