* Re: msr: Write to unrecognized MSR 0x38d by i7z
[not found] ` <20200915111012.GZ2674@hirez.programming.kicks-ass.net>
@ 2020-09-15 12:14 ` Borislav Petkov
0 siblings, 0 replies; only message in thread
From: Borislav Petkov @ 2020-09-15 12:14 UTC (permalink / raw)
To: peterz, Abhishek Jaiantilal, raininja, Richard Hull
Cc: Roman Stingler, x86, lkml
On Tue, Sep 15, 2020 at 01:10:12PM +0200, peterz@infradead.org wrote:
> On Tue, Sep 15, 2020 at 12:59:53PM +0200, Roman Stingler wrote:
> > Hi, when I open i7z I get following message in dmesg
> >
> > [17548.541965] msr: Write to unrecognized MSR 0x38f by i7z
> > Please report to x86@kernel.org
> > [17548.542030] msr: Write to unrecognized MSR 0x38d by i7z
> > Please report to x86@kernel.org
>
> That's PERF_GLOBAL_CTRL and PERF_FIXED_CTR_CTRL, userspace doesn't get
> to prod at those. Use the perf syscall.
Adding the authors/contributors of/to i7z.
Guys please consider converting your tool off of straight poking at MSRs
and to using proper kernel interfaces. If there are none for your use
case, feel free to define some and we'll help review them and get them
upstream. Poking at MSRs behind the kernel's back is a very very bad
idea.
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-09-15 12:15 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <c38cf5d6-1b6f-7b21-0179-c2849f75e8de@symvaro.com>
[not found] ` <20200915111012.GZ2674@hirez.programming.kicks-ass.net>
2020-09-15 12:14 ` msr: Write to unrecognized MSR 0x38d by i7z Borislav Petkov
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®