linux-kernel - Re: [tip:perf/core] x86, tracing, perf: Add trace point for MSR accesses

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:	Fri, 04 Dec 2015 14:35:38 -0800
From:	"H. Peter Anvin" <hpa@...or.com>
To:	Borislav Petkov <bp@...en8.de>, Andi Kleen <ak@...ux.intel.com>
CC:	Ingo Molnar <mingo@...nel.org>, linux-tip-commits@...r.kernel.org,
	vincent.weaver@...ne.edu, eranian@...gle.com, efault@....de,
	peterz@...radead.org, jolsa@...hat.com,
	torvalds@...ux-foundation.org, tglx@...utronix.de,
	rostedt@...dmis.org, acme@...hat.com, linux-kernel@...r.kernel.org
Subject: Re: [tip:perf/core] x86, tracing, perf: Add trace point for MSR accesses

On December 4, 2015 10:30:17 AM PST, Borislav Petkov <bp@...en8.de> wrote:
>On Fri, Dec 04, 2015 at 10:28:02AM -0800, Andi Kleen wrote:
>> Because making them GPL would prevent any non GPL driver from
>> using MSRs with tracing compiled in, which doesn't make any sense.
>
>I know what EXPORT_SYMBOL_GPL means - I'm questioning the need of
>making
>them available to non-GPL drivers.

How about this: it is easy too easy to hard code MSR accesses, and the last things we need is alien non-GPL drivers doing their own low-level hacks bypassing these facilities.
-- 
Sent from my Android device with K-9 Mail. Please excuse brevity and formatting.
--
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/