2015-04-18 02:23-0400, Wei Huang: > This patch enables AMD guest VM to access (R/W) PMU related MSRs, which > include PERFCTR[0..3] and EVNTSEL[0..3]. > > Signed-off-by: Wei Huang <wei@xxxxxxxxxx> > --- Reviewed-by: Radim Krčmář <rkrcmar@xxxxxxxxxx> > diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c > @@ -2268,27 +2268,17 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, struct msr_data *msr_info) > * which we perfectly emulate ;-). Any other value should be at least > * reported, some guests depend on them. (This comment is a bit outdated now too.) > */ > - case MSR_K7_EVNTSEL0: > - case MSR_K7_EVNTSEL1: > - case MSR_K7_EVNTSEL2: > - case MSR_K7_EVNTSEL3: > - if (data != 0) > - vcpu_unimpl(vcpu, "unimplemented perfctr wrmsr: " > - "0x%x data 0x%llx\n", msr, data); > - break; > - /* at least RHEL 4 unconditionally writes to the perfctr registers, > - * so we ignore writes to make it happy. > - */ > @@ -2513,6 +2503,12 @@ int kvm_get_msr_common(struct kvm_vcpu *vcpu, u32 msr, u64 *pdata) > case MSR_K7_EVNTSEL0: > case MSR_K7_EVNTSEL1: > case MSR_K7_EVNTSEL2: | case MSR_K7_EVNTSEL3: | case MSR_K7_PERFCTR0: > case MSR_K7_PERFCTR1: > case MSR_K7_PERFCTR2: > case MSR_K7_PERFCTR3: (As we depend on continuous ranges anyway, the GCCism comes to mind: 'case MSR_K7_PERFCTR0 ... MSR_K7_PERFCTR3:') > case MSR_P6_PERFCTR0: > case MSR_P6_PERFCTR1: > case MSR_P6_EVNTSEL0: -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
