From: Keir Fraser <keir@xen.org>
To: "Hao, Xudong" <xudong.hao@intel.com>,
"JBeulich@suse.com" <JBeulich@suse.com>
Cc: Aravindh Puthiyaparambil <aravindh@virtuata.com>,
"Dong, Eddie" <eddie.dong@intel.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2 0/4] XEN: fix vmx exception mistake
Date: Wed, 30 May 2012 13:21:17 +0100 [thread overview]
Message-ID: <CBEBCF4D.41899%keir@xen.org> (raw)
In-Reply-To: <403610A45A2B5242BD291EDAE8B37D300FDCB4CB@SHSMSX102.ccr.corp.intel.com>
On 30/05/2012 12:16, "Hao, Xudong" <xudong.hao@intel.com> wrote:
>> -----Original Message-----
>> From: Keir Fraser [mailto:keir.xen@gmail.com] On Behalf Of Keir Fraser
>> Sent: Wednesday, May 30, 2012 6:40 PM
>> To: Hao, Xudong; JBeulich@suse.com
>> Cc: xen-devel@lists.xen.org; Dong, Eddie; Aravindh Puthiyaparambil; Ian
>> Jackson
>> Subject: Re: [PATCH v2 0/4] XEN: fix vmx exception mistake
>>
>> On 30/05/2012 03:35, "Xudong Hao" <xudong.hao@intel.com> wrote:
>>
>>> Changes from v1:
>>> - Define new struct hvm_trap to represent information of trap, include
>>> instruction length.
>>> - Renames hvm_inject_exception to hvm_inject_trap. Then define a couple of
>>> wrappers around that function for existing callers, so that their
>>> parameter
>>> lists actually *shrink*.
>>
>> I checked in the series, except for the bit that infers trap type from
>> within vmx_inject_trap(). Instead I plumbed through a trap-type field to
>> dom0 toolstack, so the type can be specified by the caller.
>>
>
> Thanks, that's more clean.
>
> The INT3 trap type should be HVMOP_TRAP_sw_exc in
> tools/tests/xen-access/xen-access.c.
Thanks I'll fix it and renam einslen -> insn_len as Jan suggested.
-- Keir
next prev parent reply other threads:[~2012-05-30 12:21 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-30 2:35 [PATCH v2 0/4] XEN: fix vmx exception mistake Xudong Hao
2012-05-30 2:35 ` [PATCH v2 1/4] xen: Define new struct hvm_trap and cleanup vmx exception Xudong Hao
2012-05-30 2:35 ` [PATCH v2 2/4] VMX: Fix the mistake of exception execution Xudong Hao
2012-05-30 9:18 ` Jan Beulich
2012-05-30 11:24 ` Hao, Xudong
2012-05-30 2:35 ` [PATCH v2 3/4] xen: Add instruction length parameter in hypercall HVMOP_inject_trap Xudong Hao
2012-05-30 9:19 ` Jan Beulich
2012-05-30 10:40 ` [PATCH v2 0/4] XEN: fix vmx exception mistake Keir Fraser
2012-05-30 11:16 ` Hao, Xudong
2012-05-30 12:21 ` Keir Fraser [this message]
2012-05-31 2:00 ` Hao, Xudong
2012-05-31 23:21 ` Aravindh Puthiyaparambil
2012-06-01 0:46 ` Hao, Xudong
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=CBEBCF4D.41899%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=aravindh@virtuata.com \
--cc=eddie.dong@intel.com \
--cc=xen-devel@lists.xen.org \
--cc=xudong.hao@intel.com \
/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).