From: Alexandru Stefan ISAILA <aisaila@bitdefender.com>
To: "tamas@tklengyel.com" <tamas@tklengyel.com>
Cc: "suravee.suthikulpanit@amd.com" <suravee.suthikulpanit@amd.com>,
"rcojocaru@bitdefender.com" <rcojocaru@bitdefender.com>,
"andrew.cooper3@citrix.com" <andrew.cooper3@citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>,
"jbeulich@suse.com" <jbeulich@suse.com>,
"boris.ostrovsky@oracle.com" <boris.ostrovsky@oracle.com>
Subject: Re: [PATCH v1 2/4] hvm/svm: Enable Breakpoint events
Date: Mon, 5 Feb 2018 09:52:29 +0000 [thread overview]
Message-ID: <1517824349.4937.8.camel@bitdefender.com> (raw)
In-Reply-To: <CABfawhnSRkPwn089o4zTJAsfF3TV5c=DkuKTkJrN0L3m5qu7fw@mail.gmail.com>
On Vi, 2018-02-02 at 08:42 -0700, Tamas K Lengyel wrote:
> On Fri, Feb 2, 2018 at 2:37 AM, Alexandru Isaila
> <aisaila@bitdefender.com> wrote:
> >
> > This commit enables the breakpoint events for svm.
> >
> > Signed-off-by: Alexandru Isaila <aisaila@bitdefender.com>
> > ---
> > xen/arch/x86/hvm/svm/svm.c | 52
> > ++++++++++++++++++++++++++++++++++++-------
> > xen/include/asm-x86/monitor.h | 3 ++-
> > 2 files changed, 46 insertions(+), 9 deletions(-)
> >
> > diff --git a/xen/arch/x86/hvm/svm/svm.c
> > b/xen/arch/x86/hvm/svm/svm.c
> > index dcbd550..14a5f60 100644
> > --- a/xen/arch/x86/hvm/svm/svm.c
> > +++ b/xen/arch/x86/hvm/svm/svm.c
> > @@ -59,6 +59,7 @@
> > #include <asm/hap.h>
> > #include <asm/apic.h>
> > #include <asm/debugger.h>
> > +#include <asm/hvm/monitor.h>
> > #include <asm/xstate.h>
> >
> > void svm_asm_do_resume(void);
> > @@ -1079,7 +1080,8 @@ static void svm_ctxt_switch_to(struct vcpu
> > *v)
> > static void noreturn svm_do_resume(struct vcpu *v)
> > {
> > struct vmcb_struct *vmcb = v->arch.hvm_svm.vmcb;
> > - bool_t debug_state = v->domain->debugger_attached;
> > + bool_t debug_state = v->domain->debugger_attached
> > + || v->domain-
> > >arch.monitor.software_breakpoint_enabled;
> > bool_t vcpu_guestmode = 0;
> > struct vlapic *vlapic = vcpu_vlapic(v);
> >
> > @@ -2407,6 +2409,23 @@ static bool svm_get_pending_event(struct
> > vcpu *v, struct x86_event *info)
> > return true;
> > }
> >
> > +static void svm_propagate_intr(struct vcpu *v, unsigned long
> > insn_len)
> > +{
> > + struct vmcb_struct *vmcb = v->arch.hvm_svm.vmcb;
> > + struct x86_event event = {
> > + .vector = vmcb->eventinj.fields.type,
> > + .type = vmcb->eventinj.fields.type,
> > + .error_code = vmcb->exitinfo1,
> > + };
> > +
> > + if ( event.type >= X86_EVENTTYPE_SW_INTERRUPT )
> > + event.insn_len = insn_len;seems
> > + else
> > + event.insn_len = 0;
> > +
> > + hvm_inject_event(&event);
> > +}
> > +
> > static struct hvm_function_table __initdata svm_function_table = {
> > .name = "SVM",
> > .cpu_up_prepare = svm_cpu_up_prepare,
> > @@ -2619,14 +2638,31 @@ void svm_vmexit_handler(struct
> > cpu_user_regs *regs)
> > break;
> >
> > case VMEXIT_EXCEPTION_BP:
> > - if ( !v->domain->debugger_attached )
> > - goto unexpected_exit_type;
> > - /* AMD Vol2, 15.11: INT3, INTO, BOUND intercepts do not
> > update RIP. */
> > - if ( (inst_len = __get_instruction_length(v, INSTR_INT3))
> > == 0 )
> > + inst_len = __get_instruction_length(v, INSTR_INT3);
> > +
> > + if ( inst_len == 0 )
> > break;
> > - __update_guest_eip(regs, inst_len);
> > - current->arch.gdbsx_vcpu_event = TRAP_int3;
> > - domain_pause_for_debugger();
> > +
> > + if ( !v->domain->debugger_attached )
> I think this would be easier to follow if you switched it around.
This is just the way that is on the vmx side. If you think it's better
to change it then I will
>
> >
> > + {
> > + /* AMD Vol2, 15.11: INT3, INTO, BOUND intercepts do not
> > update RIP. */
> > + int rc;
> > +
> > + rc = hvm_monitor_debug(regs->rip,
> > + HVM_MONITOR_SOFTWARE_BREAKPOINT
> > ,
> > + X86_EVENTTYPE_SW_EXCEPTION,
> > + inst_len);
> > + if ( rc < 0 )
> > + goto unexpected_exit_type;
> > + if ( !rc )
> > + svm_propagate_intr(v, inst_len);
> > + }
> > + else
> > + {
> > + __update_guest_eip(regs, inst_len);
> > + current->arch.gdbsx_vcpu_event = TRAP_int3;
> > + domain_pause_for_debugger();
> > + }
> > break;
> >
> > case VMEXIT_EXCEPTION_NM:
> > diff --git a/xen/include/asm-x86/monitor.h b/xen/include/asm-
> > x86/monitor.h
> > index 3706b7a..68a210a 100644
> > --- a/xen/include/asm-x86/monitor.h
> > +++ b/xen/include/asm-x86/monitor.h
> > @@ -94,7 +94,8 @@ static inline uint32_t
> > arch_monitor_get_capabilities(struct domain *d)
> > }
> > else if ( cpu_has_svm )
> > {
> > - capabilities = (1U <<
> > XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST);
> > + capabilities = (1U <<
> > XEN_DOMCTL_MONITOR_EVENT_GUEST_REQUEST) |
> > + (1U <<
> > XEN_DOMCTL_MONITOR_EVENT_SOFTWARE_BREAKPOINT);
> Since breakpoints are also supported for both svm and vmx, you can
> just set it once, no need for the extra if block.
>
> Tamas
>
> ________________________
> This email was scanned by Bitdefender
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-02-05 9:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-02 9:37 [PATCH v1 0/4] hvm/svm: Enable vm events for SVM Alexandru Isaila
2018-02-02 9:37 ` [PATCH v1 1/4] asm-x86/monitor: Enable svm monitor events Alexandru Isaila
2018-02-02 15:38 ` Tamas K Lengyel
2018-02-02 9:37 ` [PATCH v1 2/4] hvm/svm: Enable Breakpoint events Alexandru Isaila
2018-02-02 15:42 ` Tamas K Lengyel
2018-02-05 9:52 ` Alexandru Stefan ISAILA [this message]
2018-02-02 15:58 ` Andrew Cooper
2018-02-02 16:27 ` Alexandru Stefan ISAILA
2018-02-02 9:37 ` [PATCH v1 3/4] hvm/svm: Enable MSR events Alexandru Isaila
2018-02-02 9:37 ` [PATCH v1 4/4] hvm/svm: Enable CR events Alexandru Isaila
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=1517824349.4937.8.camel@bitdefender.com \
--to=aisaila@bitdefender.com \
--cc=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=jbeulich@suse.com \
--cc=rcojocaru@bitdefender.com \
--cc=suravee.suthikulpanit@amd.com \
--cc=tamas@tklengyel.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 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).