From: Jian Zhou <jianjay.zhou@huawei.com>
To: Paolo Bonzini <pbonzini@redhat.com>, <kvm@vger.kernel.org>,
<gleb@kernel.org>, <tglx@linutronix.de>, <mingo@redhat.com>,
<hpa@zytor.com>, <x86@kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <herongguang.he@huawei.com>, <zhang.zhanghailiang@huawei.com>,
<weidong.huang@huawei.com>, <peter.huangpeng@huawei.com>
Subject: Re: [PATCH v2 3/4] KVM: X86: Migration is supported
Date: Thu, 12 Nov 2015 15:06:15 +0800 [thread overview]
Message-ID: <56443A67.4070208@huawei.com> (raw)
In-Reply-To: <56435B9A.1070004@redhat.com>
On 2015/11/11 23:15, Paolo Bonzini wrote:
>
>
> On 23/10/2015 11:15, Jian Zhou wrote:
>> data *msr_info)
>> }
>> break;
>> case MSR_IA32_DEBUGCTLMSR:
>> - if (!data) {
>> - /* We support the non-activated case already */
>> - break;
>> - } else if (data & ~(DEBUGCTLMSR_LBR | DEBUGCTLMSR_BTF)) {
>> - /* Values other than LBR and BTF are vendor-specific,
>> - thus reserved and should throw a #GP */
>> + supported = DEBUGCTLMSR_LBR | DEBUGCTLMSR_BTF |
>> + DEBUGCTLMSR_FREEZE_LBRS_ON_PMI;
>> +
>> + if (data & ~supported) {
>> + /*
>> + * Values other than LBR/BTF/FREEZE_LBRS_ON_PMI
>> + * are not supported, thus reserved and should throw a #GP
>> + */
>> + vcpu_unimpl(vcpu, "%s: MSR_IA32_DEBUGCTLMSR 0x%llx, nop\n",
>> + __func__, data);
>> return 1;
>> }
>> - vcpu_unimpl(vcpu, "%s: MSR_IA32_DEBUGCTLMSR 0x%llx, nop\n",
>> - __func__, data);
>> + if (kvm_x86_ops->set_debugctlmsr) {
>> + if (kvm_x86_ops->set_debugctlmsr(vcpu, data))
>> + return 1;
>> + }
>> + else
>> + return 1;
>> +
>> break;
>> case 0x200 ... 0x2ff:
>> return kvm_mtrr_set_msr(vcpu, msr, data);
>> @@ -2078,6 +2090,33 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
>> vcpu_unimpl(vcpu, "disabled perfctr wrmsr: "
>> "0x%x data 0x%llx\n", msr, data);
>> break;
>> + case MSR_LBR_STATUS:
>> + if (kvm_x86_ops->set_debugctlmsr) {
>> + vcpu->arch.lbr_status = (data == 0) ? 0 : 1;
>> + if (data)
>> + kvm_x86_ops->set_debugctlmsr(vcpu,
>> + DEBUGCTLMSR_LBR | DEBUGCTLMSR_FREEZE_LBRS_ON_PMI);
>> + } else
>> + vcpu_unimpl(vcpu, "lbr is disabled, ignored wrmsr: "
>> + "0x%x data 0x%llx\n", msr, data);
>> + break;
>> + case MSR_LBR_SELECT:
>> + case MSR_LBR_TOS:
>> + case MSR_PENTIUM4_LER_FROM_LIP:
>> + case MSR_PENTIUM4_LER_TO_LIP:
>> + case MSR_PENTIUM4_LBR_TOS:
>> + case MSR_IA32_LASTINTFROMIP:
>> + case MSR_IA32_LASTINTTOIP:
>> + case MSR_LBR_CORE2_FROM ... MSR_LBR_CORE2_FROM + 0x7:
>> + case MSR_LBR_CORE2_TO ... MSR_LBR_CORE2_TO + 0x7:
>> + case MSR_LBR_NHM_FROM ... MSR_LBR_NHM_FROM + 0x1f:
>> + case MSR_LBR_NHM_TO ... MSR_LBR_NHM_TO + 0x1f:
>> + if (kvm_x86_ops->set_lbr_msr)
>> + kvm_x86_ops->set_lbr_msr(vcpu, msr, data);
>> + else
>> + vcpu_unimpl(vcpu, "lbr is disabled, ignored wrmsr: "
>> + "0x%x data 0x%llx\n", msr, data);
>
> I think you can just do this in kvm_x86_ops->set_msr. The old
> implementation for DEBUGCTL MSR can be moved to svm.c.
I think you mean "moved to vmx.c"?
Thanks,
Jian
> Paolo
>
> .
>
next prev parent reply other threads:[~2015-11-12 7:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 9:15 [PATCH v2 0/4] KVM: VMX: enable LBR virtualization Jian Zhou
2015-10-23 9:15 ` [PATCH v2 1/4] KVM: X86: Add arrays to save/restore LBR MSRs Jian Zhou
2015-10-23 12:14 ` kbuild test robot
2015-10-23 9:15 ` [PATCH v2 2/4] KVM: X86: LBR MSRs of supported CPU types Jian Zhou
2015-10-23 9:15 ` [PATCH v2 3/4] KVM: X86: Migration is supported Jian Zhou
2015-11-11 15:15 ` Paolo Bonzini
2015-11-12 7:06 ` Jian Zhou [this message]
2015-11-12 9:00 ` Paolo Bonzini
2015-11-12 10:39 ` Jian Zhou
2015-10-23 9:15 ` [PATCH v2 4/4] KVM: VMX: details of LBR virtualization implementation Jian Zhou
2015-11-09 1:33 ` [PATCH v2 0/4] KVM: VMX: enable LBR virtualization Jian Zhou
2015-11-09 9:06 ` Paolo Bonzini
2015-11-09 9:26 ` Jian Zhou
2015-11-11 15:23 ` Paolo Bonzini
2015-11-12 8:06 ` Jian Zhou
-- strict thread matches above, loose matches on Subject: below --
2015-10-23 8:46 Jian Zhou
2015-10-23 8:47 ` [PATCH v2 3/4] KVM: X86: Migration is supported Jian Zhou
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=56443A67.4070208@huawei.com \
--to=jianjay.zhou@huawei.com \
--cc=gleb@kernel.org \
--cc=herongguang.he@huawei.com \
--cc=hpa@zytor.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.huangpeng@huawei.com \
--cc=tglx@linutronix.de \
--cc=weidong.huang@huawei.com \
--cc=x86@kernel.org \
--cc=zhang.zhanghailiang@huawei.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).