From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Tamas K Lengyel <tamas@tklengyel.com>,
Razvan Cojocaru <rcojocaru@bitdefender.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Emulating in response of an int3 vm_event
Date: Tue, 1 Dec 2015 10:40:35 +0000 [thread overview]
Message-ID: <565D7923.5080806@citrix.com> (raw)
In-Reply-To: <CABfawhkiBYY8vxtGkRDVV_jS6HF794+scRH+bQ1TRVLJ50MtVQ@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1164 bytes --]
On 01/12/15 01:21, Tamas K Lengyel wrote:
>
>
> On Mon, Nov 30, 2015 at 7:01 PM, Razvan Cojocaru
> <rcojocaru@bitdefender.com <mailto:rcojocaru@bitdefender.com>> wrote:
>
> On 12/01/2015 01:32 AM, Tamas K Lengyel wrote:
> > Hi all,
> > I'm trying to extend the current vm_event system to be able to
> emulate
> > over an in-guest breakpoint using the
> VM_EVENT_FLAG_SET_EMUL_READ_DATA
> > feature. The idea is to have the vm_event listener send back the
> > contents of the memory that was overwritten by the breakpoint
> > instruction, have Xen emulate one instruction, and resume execution
> > normally afterwards. This would eliminate the need of removing the
> > breakpoint, singlestepping, and placing the breakpoint back again.
> >
> > Unfortunately I encounter this crash when I call
> > hvm_mem_access_emulate_one in the event response handler:
> >
> > (XEN) vm_event.c:72:d0v0 Checking flags on int3 response 37
> > (XEN) Xen BUG at /share/src/xen/xen/include/asm/hvm/vmx/vmx.h:372
>
This BUG() is the cause of the crash.
It is a bad parameter to VMREAD, by the looks of it.
~Andrew
[-- Attachment #1.2: Type: text/html, Size: 2672 bytes --]
[-- Attachment #2: Type: text/plain, Size: 126 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2015-12-01 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-30 23:32 Emulating in response of an int3 vm_event Tamas K Lengyel
2015-12-01 0:01 ` Razvan Cojocaru
2015-12-01 1:21 ` Tamas K Lengyel
2015-12-01 10:40 ` Andrew Cooper [this message]
2015-12-01 10:51 ` Andrew Cooper
2015-12-01 13:15 ` Jan Beulich
2015-12-02 18:21 ` Tamas K Lengyel
2015-12-02 18:34 ` Andrew Cooper
2015-12-02 18:38 ` Tamas K Lengyel
2015-12-02 18:41 ` Andrew Cooper
2015-12-03 11:09 ` Jan Beulich
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=565D7923.5080806@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=rcojocaru@bitdefender.com \
--cc=tamas@tklengyel.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.