All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: bp@alien8.de, 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,
	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] x86: PAT: Documentation: update overlapping ioremap hack recommendation
Date: Fri, 4 Mar 2016 13:09:00 -0800	[thread overview]
Message-ID: <20160304210900.GT3577@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160304192326.GU25240@wotan.suse.de>

On Fri, Mar 04, 2016 at 08:23:26PM +0100, Luis R. Rodriguez wrote:
> On Thu, Mar 03, 2016 at 01:42:33PM -0800, Paul E. McKenney wrote:
> > On Thu, Mar 03, 2016 at 01:21:48PM -0800, Luis R. Rodriguez wrote:
> > > The current documentation refers to using set_memor_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. 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.
> > > 
> > > Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
> > 
> > Given an Acked-by or better from the guys on the TO line, I would be
> > happy to queue it.
> 
> I'll need to respin as fortunately I ended up actually not needing
> to do an overlap on atyfb, and instead just let MTRR be effective
> over an entire range that included both write-combining and strong
> UC attributes. It was a bit fuzzy as this while ago, and since its
> also obscure, its more reason to document now.
> 
> Will spin a v2.

Sounds good!

							Thanx, Paul

WARNING: multiple messages have this Message-ID (diff)
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "Luis R. Rodriguez" <mcgrof@kernel.org>
Cc: bp@alien8.de, 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,
	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] x86: PAT: Documentation: update overlapping ioremap hack recommendation
Date: Fri, 04 Mar 2016 21:09:00 +0000	[thread overview]
Message-ID: <20160304210900.GT3577@linux.vnet.ibm.com> (raw)
In-Reply-To: <20160304192326.GU25240@wotan.suse.de>

On Fri, Mar 04, 2016 at 08:23:26PM +0100, Luis R. Rodriguez wrote:
> On Thu, Mar 03, 2016 at 01:42:33PM -0800, Paul E. McKenney wrote:
> > On Thu, Mar 03, 2016 at 01:21:48PM -0800, Luis R. Rodriguez wrote:
> > > The current documentation refers to using set_memor_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. 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.
> > > 
> > > Signed-off-by: Luis R. Rodriguez <mcgrof@kernel.org>
> > 
> > Given an Acked-by or better from the guys on the TO line, I would be
> > happy to queue it.
> 
> I'll need to respin as fortunately I ended up actually not needing
> to do an overlap on atyfb, and instead just let MTRR be effective
> over an entire range that included both write-combining and strong
> UC attributes. It was a bit fuzzy as this while ago, and since its
> also obscure, its more reason to document now.
> 
> Will spin a v2.

Sounds good!

							Thanx, Paul


  reply	other threads:[~2016-03-04 21:09 UTC|newest]

Thread overview: 23+ 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 [this message]
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-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-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
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=20160304210900.GT3577@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=airlied@redhat.com \
    --cc=benh@kernel.crashing.org \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=daniel.vetter@ffwll.ch \
    --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=mcgrof@kernel.org \
    --cc=mingo@kernel.org \
    --cc=mst@redhat.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 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.