From: jnair@caviumnetworks.com (Jayachandran C)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/2] ioremap_wc on arm64
Date: Mon, 22 May 2017 11:53:50 +0000 [thread overview]
Message-ID: <20170522115349.GA82957@localhost> (raw)
In-Reply-To: <20170522085615.GC30129@e104818-lin.cambridge.arm.com>
On Mon, May 22, 2017 at 09:56:16AM +0100, Catalin Marinas wrote:
> On Mon, May 22, 2017 at 07:01:45AM +0000, Jayachandran C wrote:
> > From its definition, the device "gather" attribute seems to be a better
> > fit for implementing write combining mapping in ioremap_wc(). And on
> > ThunderX2, Device GRE mapping has optimizations that makes it much faster
> > than normal uncached mapping.
> >
> > I am not sure of the reasoning behind the original decision to make
> > ioremap_wc use "Normal Non-Cached" attribute, since all the other variants
> > of ioremap use device attributes, and ioremap_wc looks like an exception.
>
> The reason we kept it as Normal NC is that Device_GRE does not allow
> unaligned accesses.
There does not to be an expectation to have unaligned access on __iomem
pointers. I also see that memremap can call ioremap_wc (which is a Normal
mapping) or ioremap_wt(which is a Device mapping), so that is inconsistent
as well.
Was this added for a specific use case? Also, do you think this patchset
is acceptable?
Thanks,
JC.
next prev parent reply other threads:[~2017-05-22 11:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 7:01 [PATCH 0/2] ioremap_wc on arm64 Jayachandran C
2017-05-22 7:01 ` [PATCH 1/2] arm64: add PROT_DEVICE_GRE for Device GRE mapping Jayachandran C
2017-05-22 7:01 ` [PATCH 2/2] arm64: switch ioremap_wc to use Device GRE Jayachandran C
2017-05-22 8:56 ` [PATCH 0/2] ioremap_wc on arm64 Catalin Marinas
2017-05-22 11:53 ` Jayachandran C [this message]
2017-05-22 11:58 ` Alexander Graf
2017-05-22 12:22 ` Will Deacon
2017-05-22 14:21 ` Jayachandran C
2017-05-22 15:49 ` Catalin Marinas
2017-05-23 10:09 ` Jayachandran C
2017-05-23 14:08 ` Catalin Marinas
2017-05-24 13:33 ` Jayachandran C
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=20170522115349.GA82957@localhost \
--to=jnair@caviumnetworks.com \
--cc=linux-arm-kernel@lists.infradead.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).