From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Razvan Cojocaru <rcojocaru@bitdefender.com>, xen-devel@lists.xen.org
Cc: mdontu@bitdefender.com, tim@xen.org, JBeulich@suse.com
Subject: Re: [PATCH RFC V2 2/6] xen: Optimize introspection access to guest state
Date: Fri, 11 Jul 2014 17:54:01 +0100 [thread overview]
Message-ID: <53C016A9.6070701@citrix.com> (raw)
In-Reply-To: <1405093418-23481-2-git-send-email-rcojocaru@bitdefender.com>
On 11/07/14 16:43, Razvan Cojocaru wrote:
> Speed optimization for introspection purposes: a handful of registers
> are sent along with each mem_event. This requires enlargement of the
> mem_event_request / mem_event_response stuctures, and additional code
> to fill in relevant values. Since the EPT event processing code needs
> more data than CR3 or MSR event processors, hvm_mem_event_fill_regs()
> fills in less data than p2m_mem_event_fill_regs(), in order to avoid
> overhead. Struct hvm_hw_cpu has been considered instead of the custom
> struct mem_event_regs_st, but its size would cause quick filling up
> of the mem_event ring buffer.
>
> Changes since V1:
> - Replaced guest_x86_mode with cs_arbytes in the mem_event_regs_st
> structure.
> - Removed superfluous preprocessor check for __x86_64__ in
> p2m_mem_event_fill_regs().
>
> Signed-off-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
> ---
> xen/arch/x86/hvm/hvm.c | 33 ++++++++++++++++++++++
> xen/arch/x86/mm/p2m.c | 60 ++++++++++++++++++++++++++++++++++++++++
> xen/include/public/mem_event.h | 38 +++++++++++++++++++++++++
> 3 files changed, 131 insertions(+)
>
> diff --git a/xen/arch/x86/hvm/hvm.c b/xen/arch/x86/hvm/hvm.c
> index ef2411c..89a0382 100644
> --- a/xen/arch/x86/hvm/hvm.c
> +++ b/xen/arch/x86/hvm/hvm.c
> @@ -6085,6 +6085,38 @@ int hvm_debug_op(struct vcpu *v, int32_t op)
> return rc;
> }
>
> +static inline void hvm_mem_event_fill_regs(mem_event_request_t *req)
For C functions like this, the compiler is far better at guessing the
inlineabilty of the function than the programmer. You don't need to
call it out explicitly.
> +{
> + struct cpu_user_regs *regs = guest_cpu_user_regs();
> + struct vcpu *v = current;
> +
> + req->regs.rax = regs->eax;
> + req->regs.rcx = regs->ecx;
> + req->regs.rdx = regs->edx;
> + req->regs.rbx = regs->ebx;
> + req->regs.rsp = regs->esp;
> + req->regs.rbp = regs->ebp;
> + req->regs.rsi = regs->esi;
> + req->regs.rdi = regs->edi;
> +
> + req->regs.r8 = regs->r8;
> + req->regs.r9 = regs->r9;
> + req->regs.r10 = regs->r10;
> + req->regs.r11 = regs->r11;
> + req->regs.r12 = regs->r12;
> + req->regs.r13 = regs->r13;
> + req->regs.r14 = regs->r14;
> + req->regs.r15 = regs->r15;
> +
> + req->regs.rflags = regs->eflags;
> + req->regs.rip = regs->eip;
> +
> + req->regs.msr_efer = v->arch.hvm_vcpu.guest_efer;
> + req->regs.cr0 = v->arch.hvm_vcpu.guest_cr[0];
> + req->regs.cr3 = v->arch.hvm_vcpu.guest_cr[3];
> + req->regs.cr4 = v->arch.hvm_vcpu.guest_cr[4];
> +}
> +
> static int hvm_memory_event_traps(long p, uint32_t reason,
> unsigned long value, unsigned long old,
> bool_t gla_valid, unsigned long gla)
> @@ -6129,6 +6161,7 @@ static int hvm_memory_event_traps(long p, uint32_t reason,
> req.gla = old;
> }
>
> + hvm_mem_event_fill_regs(&req);
> mem_event_put_request(d, &d->mem_event->access, &req);
>
> return 1;
> diff --git a/xen/arch/x86/mm/p2m.c b/xen/arch/x86/mm/p2m.c
> index 642ec28..13fdf78 100644
> --- a/xen/arch/x86/mm/p2m.c
> +++ b/xen/arch/x86/mm/p2m.c
> @@ -1314,6 +1314,63 @@ void p2m_mem_paging_resume(struct domain *d)
> }
> }
>
> +static inline void p2m_mem_event_fill_regs(mem_event_request_t *req)
> +{
> + struct cpu_user_regs *regs = guest_cpu_user_regs();
> + struct segment_register seg;
> + struct hvm_hw_cpu ctxt;
> + struct vcpu *v = current;
> +
> + memset(&ctxt, 0, sizeof(struct hvm_hw_cpu));
You don't need to zero ctxt if you are about to save into it.
> +
> + /* Architecture-specific vmcs/vmcb bits */
> + hvm_funcs.save_cpu_ctxt(v, &ctxt);
> +
> + req->regs.rax = regs->eax;
> + req->regs.rcx = regs->ecx;
> + req->regs.rdx = regs->edx;
> + req->regs.rbx = regs->ebx;
> + req->regs.rsp = regs->esp;
> + req->regs.rbp = regs->ebp;
> + req->regs.rsi = regs->esi;
> + req->regs.rdi = regs->edi;
> +
> + req->regs.r8 = regs->r8;
> + req->regs.r9 = regs->r9;
> + req->regs.r10 = regs->r10;
> + req->regs.r11 = regs->r11;
> + req->regs.r12 = regs->r12;
> + req->regs.r13 = regs->r13;
> + req->regs.r14 = regs->r14;
> + req->regs.r15 = regs->r15;
> +
> + req->regs.rflags = regs->eflags;
> + req->regs.rip = regs->eip;
> +
> + req->regs.dr7 = v->arch.debugreg[7];
> + req->regs.cr0 = ctxt.cr0;
> + req->regs.cr2 = ctxt.cr2;
> + req->regs.cr3 = ctxt.cr3;
> + req->regs.cr4 = ctxt.cr4;
> +
> + req->regs.sysenter_cs = ctxt.sysenter_cs;
> + req->regs.sysenter_esp = ctxt.sysenter_esp;
> + req->regs.sysenter_eip = ctxt.sysenter_eip;
> +
> + req->regs.msr_efer = ctxt.msr_efer;
> + req->regs.msr_star = ctxt.msr_star;
> + req->regs.msr_lstar = ctxt.msr_lstar;
> +
> + hvm_get_segment_register(v, x86_seg_fs, &seg);
> + req->regs.fs_base = seg.base;
> +
> + hvm_get_segment_register(v, x86_seg_gs, &seg);
> + req->regs.gs_base = seg.base;
> +
> + hvm_get_segment_register(v, x86_seg_cs, &seg);
> + req->regs.cs_arbytes = seg.attr.bytes;;
Stray double semicolon.
> +}
> +
> bool_t p2m_mem_access_check(paddr_t gpa, bool_t gla_valid, unsigned long gla,
> bool_t access_r, bool_t access_w, bool_t access_x,
> mem_event_request_t **req_ptr)
> @@ -1407,6 +1464,9 @@ bool_t p2m_mem_access_check(paddr_t gpa, bool_t gla_valid, unsigned long gla,
> if ( p2ma != p2m_access_n2rwx )
> vcpu_pause_nosync(v);
>
> + if ( req )
> + p2m_mem_event_fill_regs(req);
Should this not be part of the if ( req ) just above the pause_nosync() ?
> +
> /* VCPU may be paused, return whether we promoted automatically */
> return (p2ma == p2m_access_n2rwx);
> }
> diff --git a/xen/include/public/mem_event.h b/xen/include/public/mem_event.h
> index 3831b41..b9af728 100644
> --- a/xen/include/public/mem_event.h
> +++ b/xen/include/public/mem_event.h
> @@ -48,6 +48,43 @@
> #define MEM_EVENT_REASON_MSR 7 /* MSR was hit: gfn is MSR value, gla is MSR address;
> does NOT honour HVMPME_onchangeonly */
>
> +/* Using a custom struct (not hvm_hw_cpu) so as to not fill
> + * the mem_event ring buffer too quickly. */
> +typedef struct mem_event_regs_st {
> + uint64_t rax;
> + uint64_t rcx;
> + uint64_t rdx;
> + uint64_t rbx;
> + uint64_t rsp;
> + uint64_t rbp;
> + uint64_t rsi;
> + uint64_t rdi;
> + uint64_t r8;
> + uint64_t r9;
> + uint64_t r10;
> + uint64_t r11;
> + uint64_t r12;
> + uint64_t r13;
> + uint64_t r14;
> + uint64_t r15;
> + uint64_t rflags;
> + uint64_t dr7;
> + uint64_t rip;
> + uint64_t cr0;
> + uint64_t cr2;
> + uint64_t cr3;
> + uint64_t cr4;
> + uint64_t sysenter_cs;
> + uint64_t sysenter_esp;
> + uint64_t sysenter_eip;
> + uint64_t msr_efer;
> + uint64_t msr_star;
> + uint64_t msr_lstar;
> + uint64_t fs_base;
> + uint64_t gs_base;
> + uint32_t cs_arbytes;
This trailing uint32_t means that sizeof(mem_event_regs_t) is different
between 32 and 64 bit builds, breaking compatibility between a 64bit xen
and 32bit dom0.
The easiest fix is to add an explicit uint32_t _pad field at the end.
~Andrew
> +} mem_event_regs_t;
> +
> typedef struct mem_event_st {
> uint32_t flags;
> uint32_t vcpu_id;
> @@ -65,6 +102,7 @@ typedef struct mem_event_st {
> uint16_t available:12;
>
> uint16_t reason;
> + mem_event_regs_t regs;
> } mem_event_request_t, mem_event_response_t;
>
> DEFINE_RING_TYPES(mem_event, mem_event_request_t, mem_event_response_t);
next prev parent reply other threads:[~2014-07-11 16:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-11 15:43 [PATCH RFC V2 1/6] xen: Emulate with no writes Razvan Cojocaru
2014-07-11 15:43 ` [PATCH RFC V2 2/6] xen: Optimize introspection access to guest state Razvan Cojocaru
2014-07-11 16:54 ` Andrew Cooper [this message]
2014-07-11 16:57 ` Andrew Cooper
2014-07-11 18:03 ` Razvan Cojocaru
2014-07-11 18:09 ` Andrew Cooper
2014-07-11 15:43 ` [PATCH RFC V2 3/6] xen: Force-enable relevant MSR events; optimize the number of sent MSR events Razvan Cojocaru
2014-07-11 17:03 ` Andrew Cooper
2014-07-11 18:09 ` Razvan Cojocaru
[not found] ` <CAGU+ausrcu=L7Kf30gZJXRnnxrKe7EMYXTGByOY4agwoK0nXeA@mail.gmail.com>
2014-07-11 18:18 ` Aravindh Puthiyaparambil (aravindp)
2014-07-11 18:19 ` Andrew Cooper
2014-07-11 18:22 ` Razvan Cojocaru
2014-07-11 18:29 ` Andrew Cooper
2014-07-11 15:43 ` [PATCH RFC V2 4/6] xen: Support for VMCALL mem_events Razvan Cojocaru
2014-07-11 17:23 ` Andrew Cooper
2014-07-11 18:15 ` Razvan Cojocaru
2015-03-17 13:50 ` Razvan Cojocaru
2015-03-17 13:58 ` Jan Beulich
2015-03-17 14:07 ` Razvan Cojocaru
2015-03-17 14:20 ` Jan Beulich
2015-03-17 14:33 ` Razvan Cojocaru
2014-07-11 15:43 ` [PATCH RFC V2 5/6] xen, libxc: Request page fault injection via libxc Razvan Cojocaru
2014-07-11 18:06 ` Andrew Cooper
2014-07-17 11:53 ` Ian Campbell
2014-07-17 12:07 ` Razvan Cojocaru
2014-07-17 12:22 ` Razvan Cojocaru
2014-07-17 12:38 ` Andrew Cooper
2014-07-11 15:43 ` [PATCH RFC V2 6/6] xen: Handle resumed instruction based on previous mem_event reply Razvan Cojocaru
2014-07-11 18:36 ` Andrew Cooper
2014-07-11 18:41 ` Razvan Cojocaru
2014-07-11 19:12 ` Andrew Cooper
2014-07-11 16:23 ` [PATCH RFC V2 1/6] xen: Emulate with no writes Andrew Cooper
2014-07-11 18:00 ` Razvan Cojocaru
2014-07-14 8:37 ` Razvan Cojocaru
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=53C016A9.6070701@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=JBeulich@suse.com \
--cc=mdontu@bitdefender.com \
--cc=rcojocaru@bitdefender.com \
--cc=tim@xen.org \
--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).