All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Kang, Luwei" <luwei.kang@intel.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wei.liu2@citrix.com>,
	George Dunlap <George.Dunlap@eu.citrix.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Tim Deegan <tim@xen.org>,
	"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
	"Nakajima, Jun" <jun.nakajima@intel.com>
Subject: Re: [PATCH RESEND v1 6/7] x86: Implement Intel Processor Trace MSRs read/write
Date: Thu, 3 May 2018 05:22:15 +0000	[thread overview]
Message-ID: <82D7661F83C1A047AF7DC287873BF1E167F6D582@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <5AE3170702000078001BF1BE@prv1-mh.provo.novell.com>

> > +int pt_do_wrmsr(unsigned int msr, uint64_t msr_content) {
> > +    struct pt_desc *pt_desc = &current->arch.hvm_vmx.pt_desc;
> > +
> > +    if ( !opt_intel_pt )
> > +        return 1;
> > +
> > +    switch ( msr ) {
> > +    case MSR_IA32_RTIT_CTL:
> > +        pt_set_rtit_ctl(pt_desc, msr_content);
> > +        break;
> > +    case MSR_IA32_RTIT_STATUS:
> > +        pt_desc->guest_pt_ctx.status = msr_content;
> > +        break;
> > +    case MSR_IA32_RTIT_OUTPUT_BASE:
> > +        pt_desc->guest_pt_ctx.output_base = msr_content;
> > +        break;
> > +    case MSR_IA32_RTIT_OUTPUT_MASK:
> > +        pt_desc->guest_pt_ctx.output_mask = msr_content | 0x7F;
> > +        break;
> > +    case MSR_IA32_RTIT_CR3_MATCH:
> > +        pt_desc->guest_pt_ctx.cr3_match = msr_content;
> > +        break;
> > +    default:
> > +        pt_desc->guest_pt_ctx.addr[msr - MSR_IA32_RTIT_ADDR0_A] =
> > + msr_content;
> 
> At least these last ones need to have a canonical address check attached.

Get it. Will add address range number check and "goto gp_fault" if access unsupported MSRs.

> 
> And there is one more thing I've not found throughout the series: EPT violations and a few other VM exits have gained a new
> qualification bit, indicating that it's not the current instruction which has caused the exit.

Hi Jan,
    I don't quite understand here about EPT violations and other VM exit qualification bit. There may have an EPT violations when guest record trace to ToPA. Is this what is your concern? About new vm-exit qualification bit, do you mean there have new qualification bit for Intel PT?

> I can't imagine this to not require any change to the handling of such exits - in particular, such exits must never be handled by
> invoking the insn emulator. Aiui the only handling options here are to eliminate the condition causing the exit, or to crash the guest.
> There's no way to emulate the intended access.

Emulate which instructions? Can you give me an example?

Thanks,
Luwei Kang

> 
> Yet another apparently missing piece appears to be the corresponding XSAVE handling.
> 
> Jan
> 


_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-03  5:22 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 [this message]
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
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=82D7661F83C1A047AF7DC287873BF1E167F6D582@SHSMSX101.ccr.corp.intel.com \
    --to=luwei.kang@intel.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@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 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.