From: "Luck, Tony" <tony.luck@intel.com>
To: Andy Lutomirski <luto@amacapital.net>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Semantics of MMIO mapping attributes accross archs
Date: Mon, 6 Jul 2015 19:11:22 +0000 [thread overview]
Message-ID: <3908561D78D1C84285E8C5FCA982C28F32AA333A@ORSMSX114.amr.corp.intel.com> (raw)
In-Reply-To: <CALCETrV82gJKhYbvdrqt3SHE6=42=QBKD8BcQPSukk2nzi1+EA@mail.gmail.com>
>> 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 ?
The drivers/acpi/apei/* usages are just mapping bits of normal memory that
happens to be BIOS reserved. ioremap*() got used because it was available
and did the right thing with the page tables even though it broke the __iomem
annotations. memremap() sounds like a great idea for these.
-Tony
next prev parent reply other threads:[~2015-07-06 19:11 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
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 [this message]
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=3908561D78D1C84285E8C5FCA982C28F32AA333A@ORSMSX114.amr.corp.intel.com \
--to=tony.luck@intel.com \
--cc=benh@kernel.crashing.org \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=luto@amacapital.net \
/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