From: David Clear <dclear@amd.com>
To: <catalin.marinas@arm.com>
Cc: <linux-arm-kernel@lists.infradead.org>, <ardb@kernel.org>,
<mark.rutland@arm.com>, <maz@kernel.org>, <will@kernel.org>
Subject: Re: ARM64: Question: How to map non-shareable memory
Date: Thu, 25 May 2023 16:47:02 -0700 [thread overview]
Message-ID: <20230525234702.53202-1-dclear@amd.com> (raw)
In-Reply-To: <ZG8co3v/TYllfHAv@arm.com>
On Thu, 25 May 2023 at 09:30:27, Catalin Marinas wrote:
> Hi David,
Hi Catalin, thanks for the detailed comments.
I'm finally coming around... The multi-core issues, and having to drop
into kernel mode for the DC IVAC eliminates any possible advantage
this avenue of investigation could have yielded.
> Your best bet is Normal Non-cacheable here.
Yes, we'll stay with Normal_NC. BTW the Cortex A72 issues these as
ReadNoSnoop / WriteNoSnoop, so that's why they made it through the NOC.
> On newer architecture
> versions Arm introduced ST64B/LD64B for similar performance reasons
> (FEAT_LS64 in Armv8.7) but I don't think there's hardware yet.
That's very interesting. Something to look forward to.
Thanks again for your time. Both you and Ard. I appreciate it.
Regards,
David.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-05-25 23:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-24 21:07 ARM64: Question: How to map non-shareable memory David Clear
2023-05-24 21:59 ` Ard Biesheuvel
2023-05-25 0:33 ` David Clear
2023-05-25 8:30 ` Catalin Marinas
2023-05-25 23:47 ` David Clear [this message]
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=20230525234702.53202-1-dclear@amd.com \
--to=dclear@amd.com \
--cc=ardb@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@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;
as well as URLs for NNTP newsgroup(s).