From: Venkatesh Srinivas <venkateshs@google.com>
To: linux-kernel@vger.kernel.org
Cc: Andi Kleen <ak@linux.intel.com>,
Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
virtualization@lists.linux-foundation.org,
David Ahern <dsahern@gmail.com>,
zheng.z.yan@intel.com, mingo@elte.hu
Subject: Re: [PATCH] perf/x86/intel: Use rdmsrl_safe when initializing RAPL PMU.
Date: Fri, 14 Mar 2014 16:07:10 -0700 [thread overview]
Message-ID: <20140314230710.GA5487@google.com> (raw)
In-Reply-To: <53233516.10005@gmail.com>
On Fri, Mar 14, 2014 at 10:57:58AM -0600, David Ahern wrote:
>On 3/14/14, 10:17 AM, Andi Kleen wrote:
>>>The Intel ISR section for RDMSR seems to say: "Specifying a reserved
>>>or unimplemented
>>>MSR address in ECX will also cause a general protection exception".
>>>
>>> From a guest's perspective, MSR_RAPL_POWER_UNIT is unimplemented; kvm matches
>>>this behavior.
>>
>>MSRs are model specific and defined per model number. If you report a model
>>number you're expected to implement the MSRs defined for that model number.
>>
>>AFAIK Xen just reports 0 for unknown MSRs (and I'm surprised KVM doesn't too)
>>
>>I would suggest to fix KVM.
>
>I believe ignore_msrs parameter to kvm handles that.
>
>David
Hi,
cc-ing the virtualization mailing list for more detail on the kvm
default for ignore_msrs (it defaults off).
1) Just returning 0 for unsupported MSRs is not workable -- 0 may be a
meaningful value for an MSR. RDMSR/WRMSR already have a mechanism
for out-of-band errors, #GP.
2) #GP has been KVM's default behavior for quite some time. Even if we
believe changing KVM's default is appropriate, Linux w/ the RAPL PMU
code enabled will fail to boot on existing KVM versions. W/ this
change, Linux will boot on prior KVM versions.
Thanks,
-- vs;
parent reply other threads:[~2014-03-14 23:07 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <53233516.10005@gmail.com>]
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=20140314230710.GA5487@google.com \
--to=venkateshs@google.com \
--cc=ak@linux.intel.com \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=zheng.z.yan@intel.com \
/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).