xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Adrian Pop <apop@bitdefender.com>
To: Boris Ostrovsky <boris.ostrovsky@oracle.com>
Cc: Kevin Tian <kevin.tian@intel.com>,
	Tamas K Lengyel <tamas@tklengyel.com>,
	Wei Liu <wei.liu2@citrix.com>,
	Jun Nakajima <jun.nakajima@intel.com>,
	Razvan Cojocaru <rcojocaru@bitdefender.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <ian.jackson@eu.citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	xen-devel@lists.xenproject.org
Subject: Re: [PATCH v2] x86/monitor: add support for descriptor access events
Date: Tue, 4 Apr 2017 16:45:39 +0300	[thread overview]
Message-ID: <20170404134539.GA32165@hel> (raw)
In-Reply-To: <2d6ca461-bff8-24c3-521f-ffcf009c0b60@oracle.com>

On Tue, Apr 04, 2017 at 09:23:28AM -0400, Boris Ostrovsky wrote:
> On 04/04/2017 05:57 AM, Adrian Pop wrote:
> > Adds monitor support for descriptor access events (reads & writes of
> > IDTR/GDTR/LDTR/TR) for the x86 architecture (VMX and SVM).
> >
> > Signed-off-by: Adrian Pop <apop@bitdefender.com>
> 
> 
> > --- a/xen/arch/x86/hvm/svm/svm.c
> > +++ b/xen/arch/x86/hvm/svm/svm.c
> > @@ -856,6 +856,23 @@ static void svm_set_rdtsc_exiting(struct vcpu *v, bool_t enable)
> >      vmcb_set_general2_intercepts(vmcb, general2_intercepts);
> >  }
> >  
> > +static void svm_set_descriptor_access_exiting(struct vcpu *v, bool enable)
> > +{
> > +    struct vmcb_struct *vmcb = v->arch.hvm_svm.vmcb;
> > +    u32 general1_intercepts = vmcb_get_general1_intercepts(vmcb);
> > +    u32 mask = GENERAL1_INTERCEPT_IDTR_READ | GENERAL1_INTERCEPT_GDTR_READ \
> > +            | GENERAL1_INTERCEPT_LDTR_READ | GENERAL1_INTERCEPT_TR_READ \
> > +            | GENERAL1_INTERCEPT_IDTR_WRITE | GENERAL1_INTERCEPT_GDTR_WRITE \
> > +            | GENERAL1_INTERCEPT_LDTR_WRITE | GENERAL1_INTERCEPT_TR_WRITE;
> 
> I didn't notice this last time --- there is no need for line
> continuation here.
> 
> With that fixed,
> 
> Reviewed-by: Boris Ostrovsky <boris.ostrovsky@oracle.com>

Oh, yes.  I'll remove the escapes for the next version.  Thank you!

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

  reply	other threads:[~2017-04-04 13:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04  9:57 [PATCH v2] x86/monitor: add support for descriptor access events Adrian Pop
2017-04-04 10:52 ` Razvan Cojocaru
2017-04-04 11:46   ` Adrian Pop
2017-04-04 13:23 ` Boris Ostrovsky
2017-04-04 13:45   ` Adrian Pop [this message]
2017-04-04 15:26 ` Andrew Cooper
2017-04-04 17:11   ` Adrian Pop
2017-04-05  7:13 ` Tian, Kevin
2017-04-05 14:26 ` Jan Beulich
2017-04-06  8:59   ` Adrian Pop
2017-04-06  9:20     ` Jan Beulich
2017-04-06  9:37       ` Adrian Pop
2017-04-06 14:09         ` Jan Beulich
2017-04-07 10:01           ` Adrian Pop

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=20170404134539.GA32165@hel \
    --to=apop@bitdefender.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=rcojocaru@bitdefender.com \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=tamas@tklengyel.com \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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).