[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1410188863.28990.209.camel@misato.fc.hp.com>
Date: Mon, 08 Sep 2014 09:07:43 -0600
From: Toshi Kani <toshi.kani@...com>
To: Andy Lutomirski <luto@...capital.net>
Cc: Yigal Korman <yigal@...xistor.com>,
"H. Peter Anvin" <hpa@...or.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>, akpm@...uxfoundation.org,
Arnd Bergmann <arnd@...db.de>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Juergen Gross <jgross@...e.com>,
Stefan Bader <stefan.bader@...onical.com>,
Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>
Subject: Re: [PATCH 4/5] x86, mm: Add set_memory_wt() for WT
On Sun, 2014-09-07 at 09:49 -0700, Andy Lutomirski wrote:
> On Sun, Sep 7, 2014 at 1:49 AM, Yigal Korman <yigal@...xistor.com> wrote:
> > I think that what confused Andy (or at least me) is the documentation in Documentation/x86/pat.txt
> > If it's possible, can you please update pat.txt as part of the patch?
>
> Indeed. That file seems to indicate several times that the intended
> use of set_memory_xyz is for RAM.
Good point. pat.txt is correct that the "intended" use of
set_memory_xyz() is for RAM since there is no other way to set non-WB
attribute for RAM. For reserved memory, one should call ioremap_xyz()
to map with the xyz attribute directly. From the functionality POV,
set_memory_xyz() works for reserved memory, but such usage is not
intended.
Should I drop the patch 4/5 until we can track the use of WT for RAM?
Thanks,
-Toshi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists