From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
paulmck@linux.vnet.ibm.com, bp@alien8.de, tglx@linutronix.de,
hpa@zytor.com, toshi.kani@hp.com, airlied@redhat.com,
benh@kernel.crashing.org, mst@redhat.com, vinod.koul@intel.com,
jgross@suse.com, daniel.vetter@ffwll.ch, luto@amacapital.net,
davem@davemloft.net, ben@decadent.org.uk,
benjamin.poirier@gmail.com, linux-fbdev@vger.kernel.org,
linux-arch@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-doc@vger.kernel.org, corbet@lwn.net
Subject: Re: [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT / non-PAT systems"
Date: Tue, 15 Mar 2016 23:24:22 +0100 [thread overview]
Message-ID: <20160315222422.GH1990@wotan.suse.de> (raw)
In-Reply-To: <20160305115255.GA11846@gmail.com>
On Sat, Mar 05, 2016 at 12:52:55PM +0100, Ingo Molnar wrote:
>
> * Luis R. Rodriguez <mcgrof@kernel.org> wrote:
>
> > The current documentation refers to using set_memory_wc() as a
> > possible hole strategy when you have overlapping ioremap() regions,
>
> The whole explanation should talk about virtual aliases over the same physical
> address, not some 'overlapping regions'.
>
> I see where this talk about 'overlap' comes: the memtype rbtree in
> arch/x86/mm/pat_rbtree.c indeed has memtype ranges that may overlap on the
> physical side. But it is highly confusing to call this 'overlapping' on the driver
> API documentation level without making it really clear what it's about.
Alright thanks, I think I'll just stick to aliasing. I'll go over the
threads and pick out only what is relevant.
Luis
prev parent reply other threads:[~2016-03-15 22:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 21:21 [PATCH] x86: PAT: Documentation: update overlapping ioremap hack recommendation Luis R. Rodriguez
2016-03-03 21:21 ` Luis R. Rodriguez
2016-03-03 21:42 ` Paul E. McKenney
2016-03-03 21:42 ` Paul E. McKenney
2016-03-04 19:23 ` Luis R. Rodriguez
2016-03-04 19:23 ` Luis R. Rodriguez
2016-03-04 21:09 ` Paul E. McKenney
2016-03-04 22:45 ` [PATCH v2] x86: PAT: Documentation: rewrite "MTRR effects on PAT / non-PAT systems" Luis R. Rodriguez
2016-03-04 22:45 ` Luis R. Rodriguez
2016-03-05 0:03 ` Paul E. McKenney
2016-03-05 0:03 ` Paul E. McKenney
2016-03-05 1:03 ` Luis R. Rodriguez
2016-03-05 1:03 ` Luis R. Rodriguez
2016-03-05 4:39 ` Elliott, Robert (Persistent Memory)
2016-03-15 22:21 ` Luis R. Rodriguez
2016-03-15 22:21 ` Luis R. Rodriguez
2016-03-05 11:52 ` Ingo Molnar
2016-03-05 11:52 ` Ingo Molnar
2016-03-15 22:24 ` Luis R. Rodriguez [this message]
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=20160315222422.GH1990@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=airlied@redhat.com \
--cc=ben@decadent.org.uk \
--cc=benh@kernel.crashing.org \
--cc=benjamin.poirier@gmail.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=daniel.vetter@ffwll.ch \
--cc=davem@davemloft.net \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=mst@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=toshi.kani@hp.com \
--cc=vinod.koul@intel.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).