[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <DBB25F77-EEEC-467C-8E15-F5D23E901631@zytor.com>
Date: Fri, 04 Dec 2015 14:57:57 -0800
From: "H. Peter Anvin" <hpa@...or.com>
To: Borislav Petkov <bp@...en8.de>
CC: Andi Kleen <ak@...ux.intel.com>, 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 2:48:37 PM PST, Borislav Petkov <bp@...en8.de> wrote:
>On Fri, Dec 04, 2015 at 02:35:38PM -0800, H. Peter Anvin wrote:
>> 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.
>
>Yeah, that doesn't stop alien, non-GPL drivers from doing
>
> asm("rdmsr ..)
>
>Hell, they can even do naked byte opcodes " ...0f 32... "
>
>But I see your point, thanks!
Yes, we can't keep them from being stupid, and they clearly are being so in the first place, but we can at least make it a bit easier to not be. Since it is so easy to do that dumb thing let's not make it harder.
--
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/
Powered by blists - more mailing lists