From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>, bp@alien8.de
Cc: "Luis R. Rodriguez" <mcgrof@kernel.org>,
mingo@kernel.org, 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: Sat, 5 Mar 2016 02:03:46 +0100 [thread overview]
Message-ID: <20160305010346.GW25240@wotan.suse.de> (raw)
Message-ID: <20160305010346.fcqowarW7typV0jA3O06-jOFanN0h7HIXAYUgdphJYY@z> (raw)
In-Reply-To: <20160305000304.GA3577@linux.vnet.ibm.com>
On Fri, Mar 04, 2016 at 04:03:04PM -0800, Paul E. McKenney wrote:
> On Fri, Mar 04, 2016 at 02:45:01PM -0800, Luis R. Rodriguez wrote:
> > The current documentation refers to using set_memory_wc() as a
> > possible hole strategy when you have overlapping ioremap() regions,
> > that's incorrect as set_memory_*() helpers can only be used on RAM,
> > not IO memory. Using set_memory_wc() will not fail, that's a problem
> > which must be corrected in the future. This fixes that, and updates
> > the documention to *strongly* discourage overlapping ioremap() memory
> > uses, but also documents a possible solution should there really be
> > no other option to remain compatible on both PAT and MTRR memory
> > constarained systems. While at it, this provides some same guidlines
> > to system designers to remain sane and compatible on both PAT and
> > non-PAT systems.
> >
> > As per Toshi this also fixes the table for the effective memory type
> > when using MTRR WC on PAT UC- to WC.
> >
> > Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
>
> And I was really confused during my earlier reply. For some reason
> I read the filename as memory-barriers.txt.
>
> This one is not mine. Too much time in standards committee meetings,
> I guess. ;-)
Heh, OK yeah I was confused why you wanted to pick it up but played along.
Boris, can this go through you as its a follow up that previously went
through you ?
Luis
next prev parent reply other threads:[~2016-03-05 1:03 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 [this message]
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
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=20160305010346.GW25240@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).