From: Luwei Kang <luwei.kang@intel.com>
To: kvm@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, mingo@redhat.com, bp@alien8.de,
hpa@zytor.com, x86@kernel.org, songliubraving@fb.com,
pbonzini@redhat.com, rkrcmar@redhat.com, peterz@infradead.org,
zsm@chromium.org, alexander.shishkin@linux.intel.com,
konrad.wilk@oracle.com, ak@linux.intel.com,
Luwei Kang <luwei.kang@intel.com>
Subject: [PATCH 0/3] Inject a PMI for KVM Guest when ToPA buffer is filled
Date: Sat, 19 Jan 2019 15:04:41 -0500 [thread overview]
Message-ID: <1547928284-2915-1-git-send-email-luwei.kang@intel.com> (raw)
Each intel processor trace table of physical addresses (ToPA) entry
has an INT bit. If this bit is set, the processor will signal a
performance-monitoring interrupt (PMI) when the corresponding trace
output region is filled. This patch set will inject a PMI for Intel
Processor Trace when ToPA buffer is filled.
Luwei Kang (3):
perf/x86/intel/pt: Move pt structure to global header
perf/x86/intel/pt: Inject PMI for KVM guest
KVM: x86: Add support of clear Trace_ToPA_PMI status
arch/x86/events/intel/pt.c | 12 +++++++++++-
arch/x86/events/intel/pt.h | 38 -------------------------------------
arch/x86/include/asm/intel_pt.h | 41 ++++++++++++++++++++++++++++++++++++++++
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/include/asm/msr-index.h | 8 ++++++++
arch/x86/kvm/vmx/pmu_intel.c | 8 +++++++-
arch/x86/kvm/x86.h | 6 ++++++
7 files changed, 74 insertions(+), 40 deletions(-)
--
1.8.3.1
next reply other threads:[~2019-01-19 20:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-19 20:04 Luwei Kang [this message]
2019-01-19 20:04 ` [PATCH 1/3] perf/x86/intel/pt: Move pt structure to global header Luwei Kang
2019-01-19 20:04 ` [PATCH 2/3] perf/x86/intel/pt: Inject PMI for KVM guest Luwei Kang
2019-01-30 17:02 ` Paolo Bonzini
2019-02-06 16:34 ` Peter Zijlstra
2019-02-07 8:42 ` Paolo Bonzini
2019-01-19 20:04 ` [PATCH 3/3] KVM: x86: Add support of clear Trace_ToPA_PMI status 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=1547928284-2915-1-git-send-email-luwei.kang@intel.com \
--to=luwei.kang@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=bp@alien8.de \
--cc=hpa@zytor.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@redhat.com \
--cc=songliubraving@fb.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
--cc=zsm@chromium.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;
as well as URLs for NNTP newsgroup(s).