Re: [Xen-devel] [PATCH v2 0/4] XEN: fix vmx exception mistake

[Aravindh Puthiyaparambil <aravindh@xxxxxxxxxxxx>]

On Wed, May 30, 2012 at 7:00 PM, Hao, Xudong <xudong.hao@xxxxxxxxx> wrote:
> Hi, Aravindh
>
> This series patches has be checked in xen unstable tree 
> Cset#25424~25429(except for #25426), can you test by your case?

I ran my tests (injecting software interrupts and hardware exceptions)
and they all passed.

Thanks,
Aravindh

>> -----Original Message-----
>> From: Keir Fraser [mailto:keir.xen@xxxxxxxxx] On Behalf Of Keir Fraser
>> Sent: Wednesday, May 30, 2012 8:21 PM
>> To: Hao, Xudong; JBeulich@xxxxxxxx
>> Cc: xen-devel@xxxxxxxxxxxxx; Dong, Eddie; Aravindh Puthiyaparambil; Ian
>> Jackson
>> Subject: Re: [PATCH v2 0/4] XEN: fix vmx exception mistake
>>
>> On 30/05/2012 12:16, "Hao, Xudong" <xudong.hao@xxxxxxxxx> wrote:
>>
>> >> -----Original Message-----
>> >> From: Keir Fraser [mailto:keir.xen@xxxxxxxxx] On Behalf Of Keir Fraser
>> >> Sent: Wednesday, May 30, 2012 6:40 PM
>> >> To: Hao, Xudong; JBeulich@xxxxxxxx
>> >> Cc: xen-devel@xxxxxxxxxxxxx; 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@xxxxxxxxx> 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
>>
>>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel