linux-kernel - Re: [git-pull -tip] x86: Addition of cpufeatures to friendly access miscellaneous MSRs

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] [day] [month] [year] [list]

Date:	Mon, 11 May 2009 17:49:32 -0700
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Jaswinder Singh Rajput <jaswinder@...nel.org>
CC:	Ingo Molnar <mingo@...e.hu>, "H. Peter Anvin" <hpa@...nel.org>,
	Robert Richter <robert.richter@....com>,
	x86 maintainers <x86@...nel.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [git-pull -tip] x86: Addition of cpufeatures to friendly access
 miscellaneous MSRs

Jaswinder Singh Rajput wrote:
> 
> The basic point of these patchset is to friendly access miscellaneous
> MSRs in kernel and userspace.
> 
> Some of these patches are using hardware cpufeature and others are
> software.
> 
> In kernel some of these MSRs are frequently used and doing checking
> before accessing these MSR in various places.
> 
> So I think it will be right approach to check in one place and set
> related cpufeature and in other places we only need to check cpufeature
> and then access MSR.
> 
> This patchset is only adding cpufeature. I will release accessing
> cpufeatures in upcoming series.
> 

For those that have in-kernel users, this is fine (and valid), but this 
is the wrong order in which to do things, since you patchset doesn't 
verify where those happen.  Rather, it's better to follow each 
cpufeature with its users rather than a batch of producers followed by a 
set of consumers.

Note: I do *not* consider debugfs only consumers to be valid in this 
context.

	-hpa

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