Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1218549

Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup

Path csiph.com!eternal-september.org!feeder.eternal-september.org!aioe.org!bofh.it!news.nic.it!robomod
From "Luis R. Rodriguez" <mcgrof@suse.com>
Newsgroups linux.kernel
Subject Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup
Date Thu, 03 Sep 2015 22:00:02 +0200
Message-ID <q4IPU-503-11@gated-at.bofh.it> (permalink)
References <q3zOG-4hj-15@gated-at.bofh.it> <q3zOG-4hj-13@gated-at.bofh.it> <q4sL7-7ii-9@gated-at.bofh.it> <q4BEK-3hX-9@gated-at.bofh.it> <q4GXM-2jT-21@gated-at.bofh.it> <q4Hh8-2W4-29@gated-at.bofh.it> <q4HKb-3tz-47@gated-at.bofh.it> <q4ImR-4s7-9@gated-at.bofh.it>
X-Original-To Toshi Kani <toshi.kani@hpe.com>
MIME-Version 1.0
Content-Type text/plain; charset=us-ascii
Content-Disposition inline
User-Agent Mutt/1.5.21 (2010-09-15)
Sender robomod@news.nic.it
List-ID <linux-kernel.vger.kernel.org>
X-Mailing-List linux-kernel@vger.kernel.org
Approved robomod@news.nic.it
Lines 76
Organization linux.* mail to news gateway
X-Original-Cc Prarit Bhargava <prarit@redhat.com>, Stuart Hayes <stuart.w.hayes@gmail.com>, tglx@linutronix.de, mingo@redhat.com, "H. Peter Anvin" <hpa@zytor.com>, linux-kernel@vger.kernel.org, x86@kernel.org, mcgrof@do-not-panic.com, Toshi Kani <toshi.kani@hp.com>
X-Original-Date Thu, 3 Sep 2015 21:51:34 +0200
X-Original-Message-ID <20150903195134.GW8051@wotan.suse.de>
X-Original-References <55E477DE.2060106@gmail.com> <55E47B4D.1050103@gmail.com> <20150903024542.GS8051@wotan.suse.de> <55E83A3E.3030000@redhat.com> <20150903175902.GU8051@wotan.suse.de> <55E88D06.3040608@redhat.com> <20150903184029.GV8051@wotan.suse.de> <1441308162.3277.20.camel@hpe.com>
X-Original-Sender linux-kernel-owner@vger.kernel.org
Xref csiph.com linux.kernel:1218549

Show key headers only | View raw


On Thu, Sep 03, 2015 at 01:22:42PM -0600, Toshi Kani wrote:
> On Thu, 2015-09-03 at 20:40 +0200, Luis R. Rodriguez wrote:
> > On Thu, Sep 03, 2015 at 02:10:14PM -0400, Prarit Bhargava wrote:
> > > 
> > > 
> > > On 09/03/2015 01:59 PM, Luis R. Rodriguez wrote:
> > > > On Thu, Sep 03, 2015 at 08:17:02AM -0400, Prarit Bhargava wrote:
> > > > > 
> > > > > 
> > > > > On 09/02/2015 10:45 PM, Luis R. Rodriguez wrote:
> > > > > > On Mon, Aug 31, 2015 at 11:05:33AM -0500, Stuart Hayes wrote:
> > > > > > > Increase the range of chunk sizes tried in mtrr_cleanup() so it is 
> > > > > > > able to map large memory configs into MTRRs.
> > > > > > > 
> > > > > > > Currently, mtrr_cleanup() will fail with large memory 
> > > > > > > configurations, because it limits chunk_size to 2GB, which means 
> > > > > > > that each MTRR can only cover 2GB of memory.  With a memory size 
> > > > > > > of, say, 256GB, and ten variable MTRRs (such as some recent Intel 
> > > > > > > CPUs have), it is not possible to set up the MTRRs to cover all of
> > > > > > > memory.
> > > > > > 
> > > > > > Linux drivers no longer use MTRR so why is the cleanup needed, ie, 
> > > > > > what would happen if the cleanup is just skipped in your case ?
> > > > > 
> > > > > The infiniband & video drivers still use MTRR (or at least it was my
> > > > > understanding that they do). 
> > > > 
> > > > There were a few stragglers left on v4.2, I have transformed them in the 
> > > > latest development changes and those tranformations are now part of 
> > > > linux-next. If this is specific to a driver you may want to first ensure 
> > > > you backport the required patch that transforms the driver to use proper 
> > > > PAT interfaces, v4.2 should have most updates but there were still a few 
> > > > left. Just make sure your driver doesn't call mtrr_add() directly and if 
> > > > it doesn't then you should be OK.
> > > > 
> > > > > In any case, Stuart -- could you try booting with
> > > > > 'disable_mtrr_cleanup' as a kernel parameter?
> > > > 
> > > > Indeed, please I'd like to hear back. Be sure to have the respective 
> > > > driver transformation in place, what driver are you using exactly? In 
> > > > the event that you argue this is still needed I'd like to know exaclty 
> > > > *why*, the comit log does not mention any of that at all.
> > > > 
> > > 
> > > Well ... we are trying to also fix this in older kernels too, *cough* RHEL
> > > *cough*, so that's where the patch comes from.  If upstream is going to
> > > deprecate/remove mtrr support so be it. 
> > 
> > Check linux-next, and Documentation/x86/mtrr.txt
> > 
> > https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/tree/Docume
> > ntation/x86/mtrr.txt
> > 
> > The platform use of MTRR is the only thing you should be concerned over but 
> > as noted returning MTRR_TYPE_INVALID should suffice if the OS does not make
> > any driver use / modifications.
> 
> The following sentence in the "mtrr.txt" is not correct.  (Sorry I should have
> caught it earlier.)  mtrr_type_lookup() returns MTRR_TYPE_INVALID when MTRRs
> are disabled, i.e. MTRRs are not set by neither firmware nor OS.  Most of the
> firmwares enable them, though.
>
> "If MTRRs are only set up by the platform firmware code though and the OS does
> not make any specific MTRR mapping requests mtrr_type_lookup() should always
> return MTRR_TYPE_INVALID."

So this should be clarified to say -- that because platform firmware *may* make
use of MTRRs, even if all OS drivers are no longer making use of MTRRs
directly, we still need mtrr_type_lookup() to return the right type ?

 Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Back to linux.kernel | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Stuart Hayes <stuart.w.hayes@gmail.com> - 2015-08-31 18:10 +0200
  Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-03 04:50 +0200
    Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Prarit Bhargava <prarit@redhat.com> - 2015-09-03 14:20 +0200
      Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-03 20:00 +0200
        Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Prarit Bhargava <prarit@redhat.com> - 2015-09-03 20:20 +0200
          Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-03 20:50 +0200
            Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Toshi Kani <toshi.kani@hpe.com> - 2015-09-03 21:30 +0200
              Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-03 22:00 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Toshi Kani <toshi.kani@hpe.com> - 2015-09-03 23:40 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-04 00:10 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Toshi Kani <toshi.kani@hpe.com> - 2015-09-04 00:30 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-04 00:50 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Toshi Kani <toshi.kani@hpe.com> - 2015-09-04 01:30 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-04 02:00 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Toshi Kani <toshi.kani@hpe.com> - 2015-09-04 03:00 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Luis R. Rodriguez" <mcgrof@suse.com> - 2015-09-04 03:50 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup Toshi Kani <toshi.kani@hpe.com> - 2015-09-04 17:00 +0200
                Re: Fwd: [PATCH] x86: Use larger chunks in mtrr_cleanup "Jan Beulich" <JBeulich@suse.com> - 2015-09-04 09:00 +0200

csiph-web