From: Ingo Molnar <mingo@kernel.org>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
"Maciej W. Rozycki" <macro@linux-mips.org>,
Julia Lawall <julia.lawall@lip6.fr>,
Toshi Kani <toshi.kani@hp.com>,
Paul McKenney <paulmck@linux.vnet.ibm.com>,
Dave Airlie <airlied@redhat.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
linux-arch@vger.kernel.org, X86 ML <x86@kernel.org>,
Daniel Vetter <daniel.vetter@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Borislav Petkov <bp@alien8.de>,
Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>,
Andy Lutomirski <luto@kernel.org>,
Brian Gerst <brgerst@gmail.com>
Subject: Re: Overlapping ioremap() calls, set_memory_*() semantics
Date: Sat, 16 Apr 2016 11:20:18 +0200 [thread overview]
Message-ID: <20160416092018.GA8453@gmail.com> (raw)
In-Reply-To: <1460731649.24985.86.camel@hpe.com>
* Toshi Kani <toshi.kani@hpe.com> wrote:
> On x86, ioremap() and remap_pfn_range() already fail on a conflicting cache
> type if it is not allowed by the rule defined in is_new_memtype_allowed().
> This exception handling is necessary for remap_pfn_range() called by
> /dev/mem, but I do not think it's necessary for ioremap(). I think we can
> start from adding a warning message to ioremap().
Agreed, we should warn and map the situation before doing any behavioral change
that isn't a fix.
Thanks,
Ingo
next prev parent reply other threads:[~2016-04-16 9:20 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 21:28 Overlapping ioremap() calls, set_memory_*() semantics Luis R. Rodriguez
2016-03-04 9:44 ` Ingo Molnar
2016-03-04 18:18 ` Toshi Kani
2016-03-04 18:51 ` Luis R. Rodriguez
2016-03-04 21:39 ` Toshi Kani
2016-03-05 11:42 ` Ingo Molnar
2016-03-05 11:40 ` Ingo Molnar
2016-03-07 17:03 ` Toshi Kani
2016-03-08 12:16 ` Ingo Molnar
2016-03-09 0:29 ` Toshi Kani
2016-03-09 9:15 ` Ingo Molnar
2016-03-11 22:13 ` Toshi Kani
2016-03-16 1:45 ` Luis R. Rodriguez
2016-03-16 1:45 ` Luis R. Rodriguez
2016-03-16 1:45 ` Luis R. Rodriguez
2016-03-17 22:44 ` Toshi Kani
2016-04-13 21:16 ` Luis R. Rodriguez
2016-04-15 14:47 ` Toshi Kani
2016-04-16 9:20 ` Ingo Molnar [this message]
2016-03-21 17:38 ` Maciej W. Rozycki
2016-04-13 21:03 ` Luis R. Rodriguez
2016-03-11 6:47 ` Andy Lutomirski
2016-03-11 22:36 ` Toshi Kani
2016-03-13 1:02 ` Andy Lutomirski
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=20160416092018.GA8453@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=airlied@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=benh@kernel.crashing.org \
--cc=bp@alien8.de \
--cc=brgerst@gmail.com \
--cc=daniel.vetter@intel.com \
--cc=hpa@zytor.com \
--cc=julia.lawall@lip6.fr \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=macro@linux-mips.org \
--cc=mcgrof@kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=toshi.kani@hp.com \
--cc=toshi.kani@hpe.com \
--cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.