linux-kernel - Re: [patch 1/2] x86: track memtype for RAM in page struct

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:	Sat, 27 Sep 2008 19:59:11 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Venki Pallipadi <venkatesh.pallipadi@...el.com>
Cc:	Christoph Lameter <cl@...ux-foundation.org>,
	Jeremy Fitzhardinge <jeremy@...p.org>,
	"arjan@...ux.intel.com" <arjan@...ux.intel.com>,
	"tglx@...utronix.de" <tglx@...utronix.de>,
	"hpa@...or.com" <hpa@...or.com>,
	"andi@...stfloor.org" <andi@...stfloor.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"Siddha, Suresh B" <suresh.b.siddha@...el.com>,
	Nick Piggin <nickpiggin@...oo.com.au>
Subject: Re: [patch 1/2] x86: track memtype for RAM in page struct - v3


* Venki Pallipadi <venkatesh.pallipadi@...el.com> wrote:

> On Tue, Sep 23, 2008 at 02:59:10PM -0700, Christoph Lameter wrote:
> > I'd suggest to avoid the open coding of page flag handling using set bit etc.
> > 
> > It may be best to slowly migrate the arch specific definitions into
> > page-flags.h. Otherwise we wont have a central authority on page flags.
> > 
> 
> OK. Below is the updated patch that does not use set/clear directly on page
> flag.
> 
> x86: track memtype for RAM in page struct
> 
> From: Suresh Siddha <suresh.b.siddha@...el.com>
> Subject: x86: track memtype for RAM in page struct

applied to tip/x86/pat, thanks! Nice patch.

	Ingo
--
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/