From: ard.biesheuvel@linaro.org (Ard Biesheuvel)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/3] fix memremap on ARM
Date: Thu, 3 Mar 2016 19:07:05 +0100 [thread overview]
Message-ID: <CAKv+Gu8uGiy85vC=2sMuMCCP0J7e0qwnAxACR25bePC0zHw=8w@mail.gmail.com> (raw)
In-Reply-To: <CAPcyv4iDMGsksCh4cHU3xooodn1e2tfSc70xTo-B_C2Ppnwsrw@mail.gmail.com>
On 3 March 2016 at 19:01, Dan Williams <dan.j.williams@intel.com> wrote:
> On Thu, Mar 3, 2016 at 9:57 AM, Ard Biesheuvel
> <ard.biesheuvel@linaro.org> wrote:
>> On 3 March 2016 at 18:55, Dan Williams <dan.j.williams@intel.com> wrote:
>>> On Thu, Mar 3, 2016 at 9:41 AM, Ard Biesheuvel
> [..]
>>> Hmm, then what about Russell's suggestoin, if I'm not
>>> mischaracterizing, that ioremap_cache() move to its old
>>> ioremap_cached() name. The latter has less cross-arch confusion.
>>
>> That would be appropriate as soon as we get rid of all the abuses of
>> ioremap_cache() (for some of which I am responsible myself, in the ARM
>> UEFI code). If we change it now, we're likely to break stuff.
>>
>
> Ok, sounds good. I'll take care of the x86 ioremap_cache() removal
> and leave the eventual ARM conversion to you.
OK. But I'd still like Russell to indicate whether he agrees with all
of this, i.e., wire up memremap() to perform MT_MEMORY_RW mappings in
the vmalloc area of memory regions that may be potentially be covered
by highmem as well.
next prev parent reply other threads:[~2016-03-03 18:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 17:34 [PATCH v2 0/3] fix memremap on ARM Ard Biesheuvel
2016-02-26 17:34 ` [PATCH v2 1/3] Revert "mtd: pxa2xx-flash: switch from ioremap_cache to memremap" Ard Biesheuvel
2016-02-26 17:34 ` [PATCH v2 2/3] memremap: add arch specific hook for MEMREMAP_WB mappings Ard Biesheuvel
2016-02-26 17:34 ` [PATCH v2 3/3] ARM: memremap: implement arch_memremap_wb() Ard Biesheuvel
2016-03-03 16:24 ` [PATCH v2 0/3] fix memremap on ARM Ard Biesheuvel
2016-03-03 17:13 ` Russell King - ARM Linux
2016-03-03 17:16 ` Ard Biesheuvel
2016-03-03 17:27 ` Dan Williams
2016-03-03 17:30 ` Ard Biesheuvel
2016-03-03 17:33 ` Dan Williams
2016-03-03 17:41 ` Ard Biesheuvel
2016-03-03 17:55 ` Dan Williams
2016-03-03 17:57 ` Ard Biesheuvel
2016-03-03 18:01 ` Dan Williams
2016-03-03 18:07 ` Ard Biesheuvel [this message]
2016-03-03 19:36 ` Russell King - ARM Linux
2016-03-03 19:42 ` Ard Biesheuvel
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='CAKv+Gu8uGiy85vC=2sMuMCCP0J7e0qwnAxACR25bePC0zHw=8w@mail.gmail.com' \
--to=ard.biesheuvel@linaro.org \
--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).