From: Andy Lutomirski <luto@amacapital.net>
To: Toshi Kani <toshi.kani@hpe.com>
Cc: Ingo Molnar <mingo@kernel.org>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
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 <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: Thu, 10 Mar 2016 22:47:55 -0800 [thread overview]
Message-ID: <CALCETrUQsf7S-b+zDrof0g61NnSB3XuqdAxjsHyJfjT3D39D3Q@mail.gmail.com> (raw)
In-Reply-To: <1457370228.15454.311.camel@hpe.com>
On Mon, Mar 7, 2016 at 9:03 AM, Toshi Kani <toshi.kani@hpe.com> wrote:
> Let me try to summarize...
>
> The original issue Luis brought up was that drivers written to work with
> MTRR may create a single ioremap range covering multiple cache attributes
> since MTRR can overwrite cache attribute of a certain range. Converting
> such drivers with PAT-based ioremap interfaces, i.e. ioremap_wc() and
> ioremap_nocache(), requires a separate ioremap map for each cache
> attribute, which can be challenging as it may result in overlapping ioremap
> ranges (in his term) with different cache attributes.
>
> So, Luis asked about 'sematics of overlapping ioremap()' calls. Hence, I
> responded that aliasing mapping itself is supported, but alias with
> different cache attribute is not. We have checks in place to detect such
> condition. Overlapping ioremap calls with a different cache attribute
> either fails or gets redirected to the existing cache attribute on x86.
A little off-topic, but someone reminded me recently: most recent CPUs
have self-snoop. It's poorly documented, but on self-snooping CPUs, I
think that a lot of the aliasing issues go away. We may be able to
optimize the code quite a bit on these CPUs.
I also wonder whether we can drop a bunch of the memtype tracking.
After all, if we have aliases of different types on a self-snooping
CPU and /dev/mem is locked down hard enough, we could maybe get away
with letting self-snoop handle all the conflicts.
(We could also make /dev/mem always do UC if it would help.)
--Andy
next prev parent reply other threads:[~2016-03-11 6:48 UTC|newest]
Thread overview: 28+ 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-03 21:28 ` Luis R. Rodriguez
2016-03-04 9:44 ` Ingo Molnar
2016-03-04 18:18 ` Toshi Kani
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-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-17 22:44 ` Toshi Kani
2016-04-13 21:16 ` Luis R. Rodriguez
2016-04-15 14:47 ` Toshi Kani
2016-04-15 14:47 ` Toshi Kani
2016-04-16 9:20 ` Ingo Molnar
2016-04-16 9:20 ` Ingo Molnar
2016-03-21 17:38 ` Maciej W. Rozycki
2016-04-13 21:03 ` Luis R. Rodriguez
2016-03-11 6:47 ` Andy Lutomirski [this message]
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=CALCETrUQsf7S-b+zDrof0g61NnSB3XuqdAxjsHyJfjT3D39D3Q@mail.gmail.com \
--to=luto@amacapital.net \
--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=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mcgrof@kernel.org \
--cc=mingo@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 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).