linux-kernel - Re: [RFC PATCH 3/11] x86, mm, pat: Change reserve

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 16 Jul 2014 08:35:31 -0600
From:	Toshi Kani <toshi.kani@...com>
To:	Andy Lutomirski <luto@...capital.net>
Cc:	"H. Peter Anvin" <hpa@...or.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Ingo Molnar <mingo@...hat.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	Arnd Bergmann <arnd@...db.de>,
	Konrad Rzeszutek Wilk <konrad.wilk@...cle.com>,
	plagnioj@...osoft.com, tomi.valkeinen@...com,
	"linux-mm@...ck.org" <linux-mm@...ck.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Stefan Bader <stefan.bader@...onical.com>,
	Dave Airlie <airlied@...il.com>, Borislav Petkov <bp@...en8.de>
Subject: Re: [RFC PATCH 3/11] x86, mm, pat: Change reserve_memtype() to
 handle WT type

On Tue, 2014-07-15 at 17:28 -0700, Andy Lutomirski wrote:
> On Tue, Jul 15, 2014 at 4:53 PM, Toshi Kani <toshi.kani@...com> wrote:
 :
> > In this patch, I left using reserve_ram_pages_type() since I do not see
> > much reason to use WT for RAM, either.
> 
> I hereby predict that someone, some day, will build a system with
> nonvolatile "RAM", and someone will want this feature.  Just saying :)
> 
> More realistically, someone might want to write a silly driver that
> lets programs mmap some WT memory for testing.

Agreed.  This limitation needs to be addressed.  I meant to say that
this could be a separate effort.

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/