From: Borislav Petkov <bp@alien8.de>
To: peterz@infradead.org,
Abhishek Jaiantilal <abhishek.jaiantilal@colorado.edu>,
raininja <daniel.mclellan@gmail.com>,
Richard Hull <rm_hull@yahoo.co.uk>
Cc: Roman Stingler <roman.stingler@symvaro.com>,
x86@kernel.org, lkml <linux-kernel@vger.kernel.org>
Subject: Re: msr: Write to unrecognized MSR 0x38d by i7z
Date: Tue, 15 Sep 2020 14:14:33 +0200 [thread overview]
Message-ID: <20200915121433.GF14436@zn.tnic> (raw)
In-Reply-To: <20200915111012.GZ2674@hirez.programming.kicks-ass.net>
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
parent reply other threads:[~2020-09-15 12:15 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20200915111012.GZ2674@hirez.programming.kicks-ass.net>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200915121433.GF14436@zn.tnic \
--to=bp@alien8.de \
--cc=abhishek.jaiantilal@colorado.edu \
--cc=daniel.mclellan@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=rm_hull@yahoo.co.uk \
--cc=roman.stingler@symvaro.com \
--cc=x86@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).