From: Alexander Shishkin <alexander.shishkin@linux.intel.com>
To: Luwei Kang <luwei.kang@intel.com>
Cc: kvm@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, x86@kernel.org, pbonzini@redhat.com,
rkrcmar@redhat.com, linux-kernel@vger.kernel.org,
joro@8bytes.org, peterz@infradead.org,
chao.p.peng@linux.intel.com
Subject: Re: [PATCH v7 11/13] KVM: x86: Implement Intel Processor Trace MSRs read/write
Date: Fri, 4 May 2018 13:11:32 +0300 [thread overview]
Message-ID: <20180504101132.ybh3b7ggpl2ny77v@um.fi.intel.com> (raw)
In-Reply-To: <1525349323-9938-12-git-send-email-luwei.kang@intel.com>
On Thu, May 03, 2018 at 08:08:41PM +0800, Luwei Kang wrote:
> From: Chao Peng <chao.p.peng@linux.intel.com>
>
> Implement Intel Processor Trace MSRs read/write.
There needs to be a commit message here.
> Signed-off-by: Chao Peng <chao.p.peng@linux.intel.com>
> Signed-off-by: Luwei Kang <luwei.kang@intel.com>
> ---
> arch/x86/include/asm/intel_pt.h | 8 ++
> arch/x86/kvm/vmx.c | 163 ++++++++++++++++++++++++++++++++++++++++
> arch/x86/kvm/x86.c | 33 +++++++-
> 3 files changed, 203 insertions(+), 1 deletion(-)
>
> diff --git a/arch/x86/include/asm/intel_pt.h b/arch/x86/include/asm/intel_pt.h
> index 43ad260..dc0f3f0 100644
> --- a/arch/x86/include/asm/intel_pt.h
> +++ b/arch/x86/include/asm/intel_pt.h
> @@ -5,6 +5,14 @@
> #define PT_CPUID_LEAVES 2
> #define PT_CPUID_REGS_NUM 4 /* number of regsters (eax, ebx, ecx, edx) */
>
> +#define MSR_IA32_RTIT_STATUS_MASK (~(RTIT_STATUS_FILTEREN | \
> + RTIT_STATUS_CONTEXTEN | RTIT_STATUS_TRIGGEREN | \
> + RTIT_STATUS_ERROR | RTIT_STATUS_STOPPED | \
> + RTIT_STATUS_BYTECNT))
> +
> +#define MSR_IA32_RTIT_OUTPUT_BASE_MASK \
> + (~((1UL << cpuid_query_maxphyaddr(vcpu)) - 1) | 0x7f)
How does this macro make sense in the intel_pt.h? It also relies on vcpu
being in the scope.
> enum pt_mode {
> PT_MODE_SYSTEM = 0,
> PT_MODE_HOST,
> diff --git a/arch/x86/kvm/vmx.c b/arch/x86/kvm/vmx.c
> index 3ed02a8..2a29ab9 100644
> --- a/arch/x86/kvm/vmx.c
> +++ b/arch/x86/kvm/vmx.c
> @@ -2769,6 +2769,77 @@ static void vmx_set_interrupt_shadow(struct kvm_vcpu *vcpu, int mask)
> vmcs_write32(GUEST_INTERRUPTIBILITY_INFO, interruptibility);
> }
>
> +static int vmx_rtit_ctl_check(struct kvm_vcpu *vcpu, u64 data)
> +{
> + struct vcpu_vmx *vmx = to_vmx(vcpu);
> + unsigned long value;
> +
> + /*
> + * Any MSR write that attempts to change bits marked reserved will
> + * case a #GP fault.
> + */
> + if (data & vmx->pt_desc.ctl_bitmask)
> + return 1;
> +
> + /*
> + * Any attempt to modify IA32_RTIT_CTL while TraceEn is set will
> + * result in a #GP unless the same write also clears TraceEn.
> + */
> + if ((vmx->pt_desc.guest.ctl & RTIT_CTL_TRACEEN) &&
> + ((vmx->pt_desc.guest.ctl ^ data) & ~RTIT_CTL_TRACEEN))
> + return 1;
> +
> + /*
> + * WRMSR to IA32_RTIT_CTL that sets TraceEn but clears this bit
> + * and FabricEn would cause #GP, if
> + * CPUID.(EAX=14H, ECX=0):ECX.SNGLRGNOUT[bit 2] = 0
> + */
> + if ((data & RTIT_CTL_TRACEEN) && !(data & RTIT_CTL_TOPA) &&
> + !(data & RTIT_CTL_FABRIC_EN) &&
> + !__pt_cap_get(vmx->pt_desc.caps, PT_CAP_single_range_output))
You seem to be doing a lot of __pt_cap_get()s on each wrmsr. Did you consider
decoding the capabilities once and storing the decoded values instead, so
that in functions like these you can access them by
if (vmx->pt_desc.caps[PT_CAP_single_range_output]) ...
?
Regards,
--
Alex
next prev parent reply other threads:[~2018-05-04 10:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-03 12:08 [PATCH v7 00/13] Intel Processor Trace virtualization enabling Luwei Kang
2018-05-03 10:33 ` Alexander Shishkin
2018-05-03 12:08 ` [PATCH v7 01/13] perf/x86/intel/pt: Move Intel-PT MSRs bit definitions to a public header Luwei Kang
2018-05-03 12:08 ` [PATCH v7 02/13] perf/x86/intel/pt: Change pt_cap_get() to a public function Luwei Kang
2018-05-03 12:08 ` [PATCH v7 03/13] perf/x86/intel/pt: Add new bit definitions for Intel PT MSRs Luwei Kang
2018-05-03 12:08 ` [PATCH v7 04/13] perf/x86/intel/pt: add new capability for Intel PT Luwei Kang
2018-05-03 12:08 ` [PATCH v7 05/13] perf/x86/intel/pt: Introduce a new function to get capability of " Luwei Kang
2018-05-03 10:50 ` Alexander Shishkin
2018-05-03 11:04 ` Kang, Luwei
2018-05-03 12:13 ` Alexander Shishkin
2018-05-03 12:30 ` Paolo Bonzini
2018-05-03 12:30 ` Kang, Luwei
2018-05-03 12:32 ` Paolo Bonzini
2018-05-03 12:50 ` Kang, Luwei
2018-05-03 12:59 ` Alexander Shishkin
2018-05-03 12:08 ` [PATCH v7 06/13] KVM: x86: Add Intel Processor Trace virtualization mode Luwei Kang
2018-05-03 11:32 ` Alexander Shishkin
2018-05-03 11:50 ` Paolo Bonzini
2018-05-03 12:02 ` Alexander Shishkin
2018-05-03 12:30 ` Paolo Bonzini
2018-05-03 12:48 ` Alexander Shishkin
2018-05-03 12:50 ` Paolo Bonzini
2018-05-03 13:38 ` Alexander Shishkin
2018-05-03 13:48 ` Paolo Bonzini
2018-05-04 10:38 ` Alexander Shishkin
2018-05-04 21:52 ` Paolo Bonzini
2018-05-04 10:45 ` Peter Zijlstra
2018-05-04 21:44 ` Paolo Bonzini
2018-05-04 22:15 ` Peter Zijlstra
2018-05-07 10:47 ` Paolo Bonzini
2018-05-03 11:52 ` Paolo Bonzini
2018-05-03 12:09 ` Alexander Shishkin
2018-05-03 12:31 ` Paolo Bonzini
2018-05-03 12:08 ` [PATCH v7 07/13] KVM: x86: Add Intel Processor Trace cpuid emulation Luwei Kang
2018-05-03 12:08 ` [PATCH v7 08/13] KVM: x86: Add Intel processor trace context for each vcpu Luwei Kang
2018-05-03 11:39 ` Alexander Shishkin
2018-05-03 11:53 ` Paolo Bonzini
2018-05-03 12:08 ` [PATCH v7 09/13] KVM: x86: Implement Intel Processor Trace context switch Luwei Kang
2018-05-04 10:29 ` Alexander Shishkin
2018-05-04 21:49 ` Paolo Bonzini
2018-05-03 12:08 ` [PATCH v7 10/13] KVM: x86: Introduce a function to initialize the PT configuration Luwei Kang
2018-05-03 12:08 ` [PATCH v7 11/13] KVM: x86: Implement Intel Processor Trace MSRs read/write Luwei Kang
2018-05-04 10:11 ` Alexander Shishkin [this message]
2018-05-04 21:47 ` Paolo Bonzini
2018-05-03 12:08 ` [PATCH v7 12/13] KVM: x86: Set intercept for Intel PT " Luwei Kang
2018-05-03 12:08 ` [PATCH v7 13/13] KVM: x86: Disable Intel Processor Trace when VMXON in L1 guest Luwei Kang
2018-05-04 10:23 ` Alexander Shishkin
2018-05-04 21:49 ` Paolo Bonzini
2018-05-03 12:13 [PATCH v7 00/13] Intel Processor Trace virtualization enabling Luwei Kang
2018-05-03 12:13 ` [PATCH v7 11/13] KVM: x86: Implement Intel Processor Trace MSRs read/write Luwei Kang
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=20180504101132.ybh3b7ggpl2ny77v@um.fi.intel.com \
--to=alexander.shishkin@linux.intel.com \
--cc=chao.p.peng@linux.intel.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luwei.kang@intel.com \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®