All of lore.kernel.org
 help / color / mirror / Atom feed
From: Adrian Pop <apop@bitdefender.com>
To: Jan Beulich <JBeulich@suse.com>, xen-devel@lists.xenproject.org
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>,
	Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v2] x86/monitor: add support for descriptor access events
Date: Thu, 6 Apr 2017 11:59:38 +0300	[thread overview]
Message-ID: <20170406085938.GA3749@hel> (raw)
In-Reply-To: <58E51AB3020000780014D56B@prv-mh.provo.novell.com>

Hello,

On Wed, Apr 05, 2017 at 08:26:27AM -0600, Jan Beulich wrote:
> >>> On 04.04.17 at 11:57, <apop@bitdefender.com> wrote:
> > --- a/xen/arch/x86/hvm/hvm.c
> > +++ b/xen/arch/x86/hvm/hvm.c
> > @@ -3572,6 +3572,43 @@ gp_fault:
> >      return X86EMUL_EXCEPTION;
> >  }
> >  
> > +int hvm_descriptor_access_intercept(uint64_t exit_info,
> > +                                    uint64_t vmx_exit_qualification,
> > +                                    uint8_t descriptor, bool is_write)
> 
> Why uint8_t?

The descriptor type from struct vm_event_desc_access is uint8_t since
there are only 4 possible descriptors:

> > +#define VM_EVENT_DESC_IDTR           1
> > +#define VM_EVENT_DESC_GDTR           2
> > +#define VM_EVENT_DESC_LDTR           3
> > +#define VM_EVENT_DESC_TR             4

Should it be something else?

> > +{
> > +    struct vcpu *curr = current;
> > +    struct domain *currd = curr->domain;
> > +    int rc;
> > +
> > +    if ( currd->arch.monitor.descriptor_access_enabled )
> > +    {
> > +        ASSERT(curr->arch.vm_event);
> > +        hvm_monitor_descriptor_access(exit_info, vmx_exit_qualification,
> > +                                      descriptor, is_write);
> > +    }
> > +    else
> > +    {
> > +        struct hvm_emulate_ctxt ctxt = {};
> > +
> > +        hvm_emulate_init_once(&ctxt, NULL, guest_cpu_user_regs());
> > +        rc = hvm_emulate_one(&ctxt);
> > +        switch ( rc )
> 
> You don't really need to go through a local variable here.

Ok.
 
> > --- a/xen/arch/x86/hvm/monitor.c
> > +++ b/xen/arch/x86/hvm/monitor.c
> > @@ -72,6 +72,28 @@ void hvm_monitor_msr(unsigned int msr, uint64_t value)
> >      }
> >  }
> >  
> > +void hvm_monitor_descriptor_access(uint64_t exit_info,
> > +                                   uint64_t vmx_exit_qualification,
> > +                                   uint8_t descriptor, bool is_write)
> > +{
> > +    struct vcpu *curr = current;
> > +    vm_event_request_t req = {
> > +        .reason = VM_EVENT_REASON_DESCRIPTOR_ACCESS,
> > +        .u.desc_access.descriptor = descriptor,
> > +        .u.desc_access.is_write = is_write,
> > +    };
> > +    if ( cpu_has_vmx )
> > +    {
> > +        req.u.desc_access.arch.vmx.instr_info = exit_info;
> > +        req.u.desc_access.arch.vmx.exit_qualification = vmx_exit_qualification;
> > +    }
> > +    else
> > +    {
> > +        req.u.desc_access.arch.svm.exitinfo = exit_info;
> > +    }
> > +    monitor_traps(curr, 1, &req);
> 
> true

Ok.

> > @@ -3361,6 +3376,40 @@ static void vmx_handle_xrstors(void)
> >      domain_crash(current->domain);
> >  }
> >  
> > +static void vmx_handle_idt_or_gdt(idt_or_gdt_instr_info_t instr_info,
> > +                                  uint64_t exit_qualification)
> > +{
> > +    uint8_t descriptor = instr_info.instr_identity
> > +        ? VM_EVENT_DESC_IDTR : VM_EVENT_DESC_GDTR;
> > +
> > +    hvm_descriptor_access_intercept(instr_info.raw, exit_qualification,
> > +                                    descriptor, instr_info.instr_write);
> > +}
> > +
> > +static void vmx_handle_ldt_or_tr(ldt_or_tr_instr_info_t instr_info,
> > +                                 uint64_t exit_qualification)
> > +{
> > +    uint8_t descriptor = instr_info.instr_identity
> > +        ? VM_EVENT_DESC_TR : VM_EVENT_DESC_LDTR;
> > +
> > +    hvm_descriptor_access_intercept(instr_info.raw, exit_qualification,
> > +                                    descriptor, instr_info.instr_write);
> > +}
> 
> I think these should be folded into their only caller (at once
> eliminating the need to make those unions transparent ones).

Ok.

> And again - why uint8_t?

Same as above.

> Jan

Thank you!

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

  reply	other threads:[~2017-04-06  8:59 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
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 [this message]
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=20170406085938.GA3749@hel \
    --to=apop@bitdefender.com \
    --cc=JBeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=ian.jackson@eu.citrix.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 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.