All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kang, Luwei" <luwei.kang@intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"rth@twiddle.net" <rth@twiddle.net>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	Chao Peng <chao.p.peng@linux.intel.com>
Subject: RE: [PATCH v4 2/2] i386: Add support to get/set/migrate Intel Processor Trace feature
Date: Tue, 15 Oct 2019 12:51:48 +0000	[thread overview]
Message-ID: <82D7661F83C1A047AF7DC287873BF1E17382A209@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20191012031407.GK4084@habkost.net>

qemu> > diff --git a/target/i386/kvm.c b/target/i386/kvm.c index
> > f9f4cd1..097c953 100644
> > --- a/target/i386/kvm.c
> > +++ b/target/i386/kvm.c
> > @@ -1811,6 +1811,25 @@ static int kvm_put_msrs(X86CPU *cpu, int level)
> >                  kvm_msr_entry_add(cpu, MSR_MTRRphysMask(i), mask);
> >              }
> >          }
> > +        if (env->features[FEAT_7_0_EBX] & CPUID_7_0_EBX_INTEL_PT) {
> > +            int addr_num = kvm_arch_get_supported_cpuid(kvm_state,
> > +                                                    0x14, 1, R_EAX) &
> > + 0x7;
> > +
> > +            kvm_msr_entry_add(cpu, MSR_IA32_RTIT_CTL,
> > +                            env->msr_rtit_ctrl);
> > +            kvm_msr_entry_add(cpu, MSR_IA32_RTIT_STATUS,
> > +                            env->msr_rtit_status);
> > +            kvm_msr_entry_add(cpu, MSR_IA32_RTIT_OUTPUT_BASE,
> > +                            env->msr_rtit_output_base);
> 
> This causes the following crash on some hosts:
> 
>   qemu-system-x86_64: error: failed to set MSR 0x560 to 0x0
>   qemu-system-x86_64: target/i386/kvm.c:2673: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
> 
> Checking for CPUID_7_0_EBX_INTEL_PT is not enough: KVM has additional conditions that might prevent writing to this MSR
> (PT_CAP_topa_output && PT_CAP_single_range_output).  This causes QEMU to crash if some of the conditions aren't met.
> 
> Writing and reading this MSR (and the ones below) need to be conditional on KVM_GET_MSR_INDEX_LIST.
> 

Hi Eduardo,
    I found this issue can't be reproduced in upstream source code but can be reproduced on RHEL8.1. I haven't got the qemu source code of RHEL8.1. But after adding some trace in KVM, I found the KVM has reported the complete Intel PT CPUID information to qemu but the Intel PT CPUID (0x14) is lost when qemu setting the CPUID to KVM (cpuid level is 0xd). It looks like lost the below patch.

commit f24c3a79a415042f6dc195f029a2ba7247d14cac
Author: Luwei Kang <luwei.kang@intel.com>
Date:   Tue Jan 29 18:52:59 2019 -0500
    i386: extended the cpuid_level when Intel PT is enabled

    Intel Processor Trace required CPUID[0x14] but the cpuid_level
    have no change when create a kvm guest with
    e.g. "-cpu qemu64,+intel-pt".

Thanks,
Luwei Kang


WARNING: multiple messages have this Message-ID (diff)
From: "Kang, Luwei" <luwei.kang@intel.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Chao Peng <chao.p.peng@linux.intel.com>,
	"pbonzini@redhat.com" <pbonzini@redhat.com>,
	"rth@twiddle.net" <rth@twiddle.net>
Subject: RE: [PATCH v4 2/2] i386: Add support to get/set/migrate Intel Processor Trace feature
Date: Tue, 15 Oct 2019 12:51:48 +0000	[thread overview]
Message-ID: <82D7661F83C1A047AF7DC287873BF1E17382A209@SHSMSX104.ccr.corp.intel.com> (raw)
In-Reply-To: <20191012031407.GK4084@habkost.net>

qemu> > diff --git a/target/i386/kvm.c b/target/i386/kvm.c index
> > f9f4cd1..097c953 100644
> > --- a/target/i386/kvm.c
> > +++ b/target/i386/kvm.c
> > @@ -1811,6 +1811,25 @@ static int kvm_put_msrs(X86CPU *cpu, int level)
> >                  kvm_msr_entry_add(cpu, MSR_MTRRphysMask(i), mask);
> >              }
> >          }
> > +        if (env->features[FEAT_7_0_EBX] & CPUID_7_0_EBX_INTEL_PT) {
> > +            int addr_num = kvm_arch_get_supported_cpuid(kvm_state,
> > +                                                    0x14, 1, R_EAX) &
> > + 0x7;
> > +
> > +            kvm_msr_entry_add(cpu, MSR_IA32_RTIT_CTL,
> > +                            env->msr_rtit_ctrl);
> > +            kvm_msr_entry_add(cpu, MSR_IA32_RTIT_STATUS,
> > +                            env->msr_rtit_status);
> > +            kvm_msr_entry_add(cpu, MSR_IA32_RTIT_OUTPUT_BASE,
> > +                            env->msr_rtit_output_base);
> 
> This causes the following crash on some hosts:
> 
>   qemu-system-x86_64: error: failed to set MSR 0x560 to 0x0
>   qemu-system-x86_64: target/i386/kvm.c:2673: kvm_put_msrs: Assertion `ret == cpu->kvm_msr_buf->nmsrs' failed.
> 
> Checking for CPUID_7_0_EBX_INTEL_PT is not enough: KVM has additional conditions that might prevent writing to this MSR
> (PT_CAP_topa_output && PT_CAP_single_range_output).  This causes QEMU to crash if some of the conditions aren't met.
> 
> Writing and reading this MSR (and the ones below) need to be conditional on KVM_GET_MSR_INDEX_LIST.
> 

Hi Eduardo,
    I found this issue can't be reproduced in upstream source code but can be reproduced on RHEL8.1. I haven't got the qemu source code of RHEL8.1. But after adding some trace in KVM, I found the KVM has reported the complete Intel PT CPUID information to qemu but the Intel PT CPUID (0x14) is lost when qemu setting the CPUID to KVM (cpuid level is 0xd). It looks like lost the below patch.

commit f24c3a79a415042f6dc195f029a2ba7247d14cac
Author: Luwei Kang <luwei.kang@intel.com>
Date:   Tue Jan 29 18:52:59 2019 -0500
    i386: extended the cpuid_level when Intel PT is enabled

    Intel Processor Trace required CPUID[0x14] but the cpuid_level
    have no change when create a kvm guest with
    e.g. "-cpu qemu64,+intel-pt".

Thanks,
Luwei Kang



  reply	other threads:[~2019-10-15 12:51 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-04 16:48 [PATCH v4 1/2] i386: Add Intel Processor Trace feature support Luwei Kang
2018-03-04 16:48 ` [Qemu-devel] " Luwei Kang
2018-03-04 16:48 ` [PATCH v4 2/2] i386: Add support to get/set/migrate Intel Processor Trace feature Luwei Kang
2018-03-04 16:48   ` [Qemu-devel] " Luwei Kang
2019-10-12  3:14   ` Eduardo Habkost
2019-10-12  3:14     ` Eduardo Habkost
2019-10-15 12:51     ` Kang, Luwei [this message]
2019-10-15 12:51       ` Kang, Luwei
2019-10-15 13:29       ` Eduardo Habkost
2019-10-15 13:29         ` Eduardo Habkost
2019-10-21  6:02         ` Kang, Luwei
2019-10-21  6:02           ` Kang, Luwei
2019-10-22 21:44           ` Eduardo Habkost
2019-10-22 21:44             ` Eduardo Habkost
2019-10-24 11:22             ` Kang, Luwei
2019-10-24 11:22               ` Kang, Luwei
2019-10-24 13:24               ` Eduardo Habkost
2019-10-24 13:24                 ` Eduardo Habkost
2019-10-24 13:36                 ` Kang, Luwei
2019-10-24 13:36                   ` Kang, Luwei
2019-10-24 14:15                   ` Eduardo Habkost
2019-10-24 14:15                     ` Eduardo Habkost
2018-03-09 19:10 ` [PATCH v4 1/2] i386: Add Intel Processor Trace feature support Eduardo Habkost
2018-03-09 19:10   ` [Qemu-devel] " Eduardo Habkost
2018-03-12  9:07   ` Kang, Luwei
2018-03-12  9:07     ` [Qemu-devel] " Kang, Luwei
2018-03-12 16:45     ` Eduardo Habkost
2018-03-12 16:45       ` [Qemu-devel] " Eduardo Habkost
2018-03-13 11:16       ` Kang, Luwei
2018-03-13 11:16         ` [Qemu-devel] " Kang, Luwei

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=82D7661F83C1A047AF7DC287873BF1E17382A209@SHSMSX104.ccr.corp.intel.com \
    --to=luwei.kang@intel.com \
    --cc=chao.p.peng@linux.intel.com \
    --cc=ehabkost@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.