From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Vlad Ioan Topan <itopan@bitdefender.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>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>,
Jun Nakajima <jun.nakajima@intel.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH] x86/monitor: add support for descriptor access events
Date: Tue, 21 Mar 2017 12:04:02 +0000 [thread overview]
Message-ID: <ca10d56e-fe05-1de4-76f2-0b404cb09a51@citrix.com> (raw)
In-Reply-To: <1489161034-4381-1-git-send-email-itopan@bitdefender.com>
On 10/03/17 15:50, Vlad Ioan Topan 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: Vlad Ioan Topan <itopan@bitdefender.com>
How much extra overhead does this typically give? (I am curious, more
than anything else)
> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> index ccfae4f..cfe5aa2 100644
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -3645,6 +3645,41 @@ gp_fault:
> return X86EMUL_EXCEPTION;
> }
>
> +int hvm_descriptor_access_intercept(uint64_t exit_info, uint64_t exit_qualification,
> + uint8_t descriptor, bool_t is_write)
> +{
> + struct vcpu *v = current;
> + struct domain *d = v->domain;
> + struct hvm_emulate_ctxt ctxt = {};
> + int rc;
> +
> + if ( d->arch.monitor.descriptor_access_enabled )
> + {
> + ASSERT(v->arch.vm_event);
> + hvm_monitor_descriptor_access(exit_info, exit_qualification, descriptor, is_write);
> + }
> + else
> + {
> + hvm_emulate_init_once(&ctxt, NULL, guest_cpu_user_regs());
> + rc = hvm_emulate_one(&ctxt);
> + switch ( rc )
> + {
> + case X86EMUL_UNHANDLEABLE:
> + hvm_inject_hw_exception(TRAP_invalid_op, X86_EVENT_NO_EC);
> + break;
> + case X86EMUL_EXCEPTION:
> + if ( ctxt.ctxt.event_pending )
You can drop this if(). The expected behaviour of x86_emulate() makes
this true, and we now have an assertion to catch it being wrong. (I
should update other areas of code).
> + hvm_inject_event(&ctxt.ctxt.event);
> + /* fall through */
> + default:
> + hvm_emulate_writeback(&ctxt);
> + break;
> + }
> + }
> +
> + return X86EMUL_OKAY;
> +}
> +
> static bool is_cross_vendor(const struct x86_emulate_state *state,
> const struct x86_emulate_ctxt *ctxt)
> {
> diff --git a/xen/arch/x86/hvm/vmx/vmx.c b/xen/arch/x86/hvm/vmx/vmx.c
> index 894d7d4..2b2d193 100644
> @@ -3369,6 +3384,33 @@ static void vmx_handle_xrstors(void)
> domain_crash(current->domain);
> }
>
> +static void vmx_handle_descriptor_access(uint32_t exit_reason)
> +{
> + uint8_t instr_id;
> + uint64_t instr_info;
> + uint64_t exit_qualification;
> + uint8_t descriptor = VM_EVENT_DESC_INVALID;
> +
> + __vmread(EXIT_QUALIFICATION, &exit_qualification);
> + __vmread(VMX_INSTRUCTION_INFO, &instr_info);
Rather than all this hand decoding, can I ask you to introduce a
structure like ept_qual_t?
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-03-21 12:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-10 15:50 [PATCH] x86/monitor: add support for descriptor access events Vlad Ioan Topan
2017-03-10 19:41 ` Tamas K Lengyel
2017-03-14 12:07 ` Vlad-Ioan TOPAN
2017-03-13 21:24 ` Boris Ostrovsky
2017-03-14 12:15 ` Vlad-Ioan TOPAN
2017-03-14 12:50 ` Razvan Cojocaru
2017-03-14 13:15 ` Boris Ostrovsky
2017-03-16 9:25 ` Vlad-Ioan TOPAN
2017-03-14 13:18 ` Jan Beulich
2017-03-14 12:39 ` Wei Liu
2017-03-17 11:03 ` Jan Beulich
2017-03-20 19:21 ` Vlad-Ioan TOPAN
2017-03-21 8:04 ` Jan Beulich
2017-03-21 12:04 ` Andrew Cooper [this message]
2017-03-28 12:32 ` Vlad-Ioan TOPAN
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=ca10d56e-fe05-1de4-76f2-0b404cb09a51@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=ian.jackson@eu.citrix.com \
--cc=itopan@bitdefender.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).