From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Semantics of MMIO mapping attributes accross archs
Date: Sun, 05 Jul 2015 13:02:48 +1000 [thread overview]
Message-ID: <1436065368.3948.48.camel@kernel.crashing.org> (raw)
In-Reply-To: <CAPcyv4hsJDJwv-yEJiiy2ptn7QYbCA1+3s9gTQuhz_C9UKGGsg@mail.gmail.com>
On Sat, 2015-07-04 at 07:12 -0700, Dan Williams wrote:
> Another side topic that has come up in this space is the desire to
> define a "memremap" api to clean up __iomem abuses for cases where
> "memory-like" mappings are needed.
>
> https://lkml.org/lkml/2015/6/22/100
Interesting. I had missed this. There is a similar question about
semantics (ordering etc...), ie, are they the same as memory for
example ?
Another thing we might look into is to what extent should we provide
access to the "SAO" mapping attribute that POWER7 and later support
(strong ordering, pretty-much x86 like) and whether this can be used
on ppc to reduce the need for barriers (that attribute is only available
for fully cachable mappings, not generally applicable to IO mappings).
That translate to: should your new memremap() take some kinds of flags
as an argument ? Though of course providing a cross-arch definition of
these flags would be tricky.
Ben.
next prev parent reply other threads:[~2015-07-05 3:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-04 8:17 Benjamin Herrenschmidt
2015-07-04 14:12 ` Dan Williams
2015-07-05 3:02 ` Benjamin Herrenschmidt [this message]
2015-07-05 18:55 ` Andy Lutomirski
2015-07-05 19:56 ` Benjamin Herrenschmidt
2015-07-05 20:09 ` Andy Lutomirski
2015-07-06 9:33 ` Will Deacon
2015-07-06 22:02 ` Benjamin Herrenschmidt
2015-07-07 9:56 ` Will Deacon
2015-07-07 10:29 ` Will Deacon
2015-07-06 9:52 ` Catalin Marinas
2015-07-06 17:14 ` Andy Lutomirski
2015-07-06 22:04 ` Benjamin Herrenschmidt
2015-07-06 19:11 ` Luck, Tony
2015-07-07 0:01 ` Luis R. Rodriguez
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=1436065368.3948.48.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=dan.j.williams@intel.com \
--cc=ksummit-discuss@lists.linuxfoundation.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