From: Luwei Kang <luwei.kang@intel.com>
To: kvm@vger.kernel.org
Cc: 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,
Luwei Kang <luwei.kang@intel.com>
Subject: [PATCH v5 03/11] perf/x86/intel/pt: Introduce a new function to get the capability of Intel PT
Date: Sun, 4 Mar 2018 20:07:13 +0800 [thread overview]
Message-ID: <1520165241-15819-4-git-send-email-luwei.kang@intel.com> (raw)
In-Reply-To: <1520165241-15819-1-git-send-email-luwei.kang@intel.com>
Because of the guest CPUID information may diffrent with
with host(some bits may mask off in guest) so introduce a
new function pt_cap_get_ex() to get the capability of Intel PT.
Signed-off-by: Luwei Kang <luwei.kang@intel.com>
---
arch/x86/events/intel/pt.c | 10 ++++++++++
arch/x86/include/asm/intel_pt.h | 2 ++
2 files changed, 12 insertions(+)
diff --git a/arch/x86/events/intel/pt.c b/arch/x86/events/intel/pt.c
index d89dd8c..817104e 100644
--- a/arch/x86/events/intel/pt.c
+++ b/arch/x86/events/intel/pt.c
@@ -86,6 +86,16 @@ u32 pt_cap_get(enum pt_capabilities cap)
}
EXPORT_SYMBOL_GPL(pt_cap_get);
+u32 pt_cap_get_ex(u32 *caps, enum pt_capabilities cap)
+{
+ struct pt_cap_desc *cd = &pt_caps[cap];
+ u32 c = caps[cd->leaf * PT_CPUID_REGS_NUM + cd->reg];
+ unsigned int shift = __ffs(cd->mask);
+
+ return (c & cd->mask) >> shift;
+}
+EXPORT_SYMBOL_GPL(pt_cap_get_ex);
+
static ssize_t pt_cap_show(struct device *cdev,
struct device_attribute *attr,
char *buf)
diff --git a/arch/x86/include/asm/intel_pt.h b/arch/x86/include/asm/intel_pt.h
index 2de4db0..486e11f 100644
--- a/arch/x86/include/asm/intel_pt.h
+++ b/arch/x86/include/asm/intel_pt.h
@@ -27,9 +27,11 @@ enum pt_capabilities {
#if defined(CONFIG_PERF_EVENTS) && defined(CONFIG_CPU_SUP_INTEL)
void cpu_emergency_stop_pt(void);
extern u32 pt_cap_get(enum pt_capabilities cap);
+extern u32 pt_cap_get_ex(u32 *caps, enum pt_capabilities cap);
#else
static inline void cpu_emergency_stop_pt(void) {}
static inline u32 pt_cap_get(enum pt_capabilities cap) { return 0; }
+static u32 pt_cap_get_ex(u32 *caps, enum pt_capabilities cap) { return 0; }
#endif
#endif /* _ASM_X86_INTEL_PT_H */
--
1.8.3.1
next prev parent reply other threads:[~2018-03-05 1:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 12:07 [PATCH v5 00/11] Intel Processor Trace virtulization enabling Luwei Kang
2018-03-04 12:07 ` [PATCH v5 01/11] perf/x86/intel/pt: Move Intel-PT MSR bit definitions to a public header Luwei Kang
2018-03-04 12:07 ` [PATCH v5 02/11] perf/x86/intel/pt: Change pt_cap_get() to a public function Luwei Kang
2018-03-04 12:07 ` Luwei Kang [this message]
2018-03-16 17:28 ` [PATCH v5 03/11] perf/x86/intel/pt: Introduce a new function to get the capability of Intel PT Paolo Bonzini
2018-03-19 7:17 ` Kang, Luwei
2018-03-19 9:04 ` Paolo Bonzini
2018-03-04 12:07 ` [PATCH v5 04/11] KVM: x86: Add Intel Processor Trace virtualization mode Luwei Kang
2018-03-04 12:07 ` [PATCH v5 05/11] KVM: x86: Add Intel Processor Trace cpuid emulation Luwei Kang
2018-03-04 12:07 ` [PATCH v5 06/11] KVM: x86: Add Intel processor trace context for each vcpu Luwei Kang
2018-03-04 12:07 ` [PATCH v5 07/11] KVM: x86: Implement Intel Processor Trace context switch Luwei Kang
2018-03-04 12:07 ` [PATCH v5 08/11] KVM: x86: Introduce a function to initialize the PT configuration Luwei Kang
2018-03-04 12:07 ` [PATCH v5 09/11] KVM: x86: Implement Intel Processor Trace MSRs read/write Luwei Kang
2018-03-04 12:07 ` [PATCH v5 10/11] KVM: x86: Set intercept for Intel PT MSRs Luwei Kang
2018-03-04 12:07 ` [PATCH v5 11/11] KVM: x86: Disable Intel Processor Trace when VMXON in L1 guest Luwei Kang
2018-03-16 17:30 ` Paolo Bonzini
2018-03-19 7:31 ` Kang, Luwei
2018-03-19 9:05 ` Paolo Bonzini
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=1520165241-15819-4-git-send-email-luwei.kang@intel.com \
--to=luwei.kang@intel.com \
--cc=hpa@zytor.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--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®