linux-kernel - Re: 2.6.26, PAT and AMD family 6

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, 7 May 2008 15:17:51 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Rene Herman <rene.herman@...access.nl>
Cc:	Yinghai Lu <yhlu.kernel@...il.com>, Ingo Molnar <mingo@...e.hu>,
	Linux Kernel <linux-kernel@...r.kernel.org>
Subject: Re: 2.6.26, PAT and AMD family 6

On Wed, 07 May 2008 21:08:30 +0200
> > 
> > we filter those for all kinds of things already, sorry.
> > What good is showing "pat" if "pat" isn't deemed usable (yet)????
> > Now *that* is deception :)
> 
> The trouble is -- if you hide that the CPU _should_ have PAT, how many
> people do you expect are going to look further and test? I knew that I
> should have PAT so I distrusted my CPU feature flag display but you've
> now limited your testers to people who've read the CPU datasheet.
> That's really no good.

and... why would we care? there's no upside even if you use pat.
pat is nice to avoid problems on newer systems that run out of mtrrs.
For older systems, right now, there isn't any.

 
> If Linux messes around with those flags already, it's doing things
> wrong already. /proc/cpuinfo is not a display of software features
> but of hardware features -- anything else is outright wrong. Being
> wrong for PAT also doesn't improve things.

that is your interpretation of what that file means.
It's... not so easy.
--
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/