From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Luwei Kang <luwei.kang@intel.com>
Cc: kevin.tian@intel.com, sstabellini@kernel.org,
wei.liu2@citrix.com, jbeulich@suse.com,
George.Dunlap@eu.citrix.com, andrew.cooper3@citrix.com,
tim@xen.org, xen-devel@lists.xen.org, jun.nakajima@intel.com
Subject: Re: [PATCH RESEND v1 0/7] Intel Processor Trace virtulization enabling
Date: Mon, 30 Apr 2018 11:42:33 -0400 [thread overview]
Message-ID: <20180430154233.GC3369@char.us.oracle.com> (raw)
In-Reply-To: <1516039953-2988-1-git-send-email-luwei.kang@intel.com>
On Tue, Jan 16, 2018 at 02:12:26AM +0800, Luwei Kang wrote:
> Hi All,
>
> Here is a patch-series which adding Processor Trace enabling in XEN guest. You can get It's software developer manuals from:
> https://software.intel.com/sites/default/files/managed/c5/15/architecture-instruction-set-extensions-programming-reference.pdf
> In Chapter 5 INTEL PROCESSOR TRACE: VMX IMPROVEMENTS.
Now Chapter 4.
>
> Introduction:
> Intel Processor Trace (Intel PT) is an extension of Intel Architecture that captures information about software execution using dedicated hardware facilities that cause only minimal performance perturbation to the software being traced. Details on the Intel PT infrastructure and trace capabilities can be found in the Intel 64 and IA-32 Architectures Software Developer’s Manual, Volume 3C.
>
> The suite of architecture changes serve to simplify the process of virtualizing Intel PT for use by a guest software. There are two primary elements to this new architecture support for VMX support improvements made for Intel PT.
> 1. Addition of a new guest IA32_RTIT_CTL value field to the VMCS.
> — This serves to speed and simplify the process of disabling trace on VM exit, and restoring it on VM entry.
> 2. Enabling use of EPT to redirect PT output.
> — This enables the VMM to elect to virtualize the PT output buffer using EPT. In this mode, the CPU will treat PT output addresses as Guest Physical Addresses (GPAs) and translate them using EPT. This means that Intel PT output reads (of the ToPA table) and writes (of trace output) can cause EPT violations, and other output events.
>
How does one test this functionality in Linux? As in does 'perf' take advantage of the Processor Trace
functionality?
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-04-30 15:42 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-15 18:12 [PATCH RESEND v1 0/7] Intel Processor Trace virtulization enabling Luwei Kang
2018-01-15 18:12 ` [PATCH RESEND v1 1/7] x86: add a flag to enable Intel processor trace Luwei Kang
2018-03-09 16:53 ` Wei Liu
2018-03-12 9:25 ` Kang, Luwei
2018-04-26 12:09 ` Wei Liu
2018-04-27 8:22 ` Kang, Luwei
2018-04-27 8:32 ` Wei Liu
2018-04-27 13:03 ` Jan Beulich
2018-04-27 23:16 ` Kang, Luwei
2018-04-26 12:29 ` Jan Beulich
2018-04-27 9:01 ` Kang, Luwei
2018-04-27 12:15 ` Jan Beulich
2018-04-27 23:18 ` Kang, Luwei
2018-01-15 18:12 ` [PATCH RESEND v1 2/7] x86: configure vmcs for Intel processor trace virtualization Luwei Kang
2018-04-26 12:34 ` Jan Beulich
2018-04-28 1:07 ` Kang, Luwei
2018-04-30 7:42 ` Jan Beulich
2018-05-02 7:22 ` Kang, Luwei
2018-05-02 9:09 ` Jan Beulich
2018-05-02 9:22 ` Kang, Luwei
2018-01-15 18:12 ` [PATCH RESEND v1 3/7] x86: add intel proecessor trace support for cpuid Luwei Kang
2018-04-30 15:43 ` Konrad Rzeszutek Wilk
2018-05-02 7:32 ` Kang, Luwei
2018-01-15 18:12 ` [PATCH RESEND v1 4/7] x86: add intel processor trace context Luwei Kang
2018-04-26 12:11 ` Wei Liu
2018-04-26 12:59 ` Jan Beulich
2018-04-28 1:26 ` Kang, Luwei
2018-01-15 18:12 ` [PATCH RESEND v1 5/7] x86: Implement Intel Processor Trace context switch Luwei Kang
2018-04-26 12:11 ` Wei Liu
2018-04-27 8:53 ` Kang, Luwei
2018-05-02 15:19 ` Wei Liu
2018-05-02 15:43 ` Jan Beulich
2018-05-02 16:15 ` Wei Liu
2018-05-02 16:51 ` Andrew Cooper
2018-05-03 7:27 ` Jan Beulich
2018-05-03 7:26 ` Jan Beulich
2018-05-03 7:51 ` Wei Liu
2018-04-26 13:12 ` Jan Beulich
2018-04-28 2:56 ` Kang, Luwei
2018-01-15 18:12 ` [PATCH RESEND v1 6/7] x86: Implement Intel Processor Trace MSRs read/write Luwei Kang
2018-04-26 13:20 ` Jan Beulich
2018-04-27 12:26 ` Jan Beulich
2018-05-03 5:22 ` Kang, Luwei
2018-05-03 7:33 ` Jan Beulich
2018-05-03 9:40 ` Kang, Luwei
2018-05-03 11:36 ` Jan Beulich
2018-05-04 3:53 ` Kang, Luwei
2018-05-04 12:06 ` Jan Beulich
2018-05-10 9:06 ` Kang, Luwei
2018-01-15 18:12 ` [PATCH RESEND v1 7/7] x86: Disable Intel Processor Trace when VMXON in L1 guest Luwei Kang
2018-01-16 8:41 ` [PATCH RESEND v1 0/7] Intel Processor Trace virtulization enabling Jan Beulich
2018-01-16 9:02 ` Kang, Luwei
2018-01-16 9:30 ` Jan Beulich
2018-01-16 9:45 ` Kang, Luwei
2018-04-26 12:12 ` Wei Liu
2018-05-03 4:06 ` Kang, Luwei
2018-05-03 5:55 ` Razvan Cojocaru
2018-05-03 8:06 ` Wei Liu
2018-05-04 4:10 ` Kang, Luwei
2018-05-03 9:49 ` Kang, Luwei
2018-05-03 10:01 ` Andrew Cooper
2018-05-04 3:08 ` Kang, Luwei
2018-05-10 9:26 ` Kang, Luwei
2018-05-10 9:56 ` Andrew Cooper
2018-05-15 2:50 ` Kang, Luwei
2018-04-30 15:42 ` Konrad Rzeszutek Wilk [this message]
2018-05-02 7:27 ` 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=20180430154233.GC3369@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=andrew.cooper3@citrix.com \
--cc=jbeulich@suse.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=luwei.kang@intel.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xen.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).