On 11/24/2016 09:13 AM, Jan Beulich wrote:
> Signed-off-by: Jan Beulich
Reviewed-by: Boris Ostrovsky
(even though it's already been applied)
___
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
On 24/11/16 14:33, Jan Beulich wrote:
On 24.11.16 at 15:19, wrote:
>> On 24/11/16 14:13, Jan Beulich wrote:
>>> Signed-off-by: Jan Beulich
>> Reviewed-by: Andrew Cooper
>>
>> There is an opposite problem on the Intel side, delivering some #UD with
>> an error code (although the guest behavi
On Thu, Nov 24, 2016 at 07:33:48AM -0700, Jan Beulich wrote:
> >>> On 24.11.16 at 15:19, wrote:
> > On 24/11/16 14:13, Jan Beulich wrote:
> >> Signed-off-by: Jan Beulich
> >
> > Reviewed-by: Andrew Cooper
> >
> > There is an opposite problem on the Intel side, delivering some #UD with
> > an e
>>> On 24.11.16 at 15:19, wrote:
> On 24/11/16 14:13, Jan Beulich wrote:
>> Signed-off-by: Jan Beulich
>
> Reviewed-by: Andrew Cooper
>
> There is an opposite problem on the Intel side, delivering some #UD with
> an error code (although the guest behaviour does appear to be correct,
> so perha
On 24/11/16 14:13, Jan Beulich wrote:
> Signed-off-by: Jan Beulich
Reviewed-by: Andrew Cooper
There is an opposite problem on the Intel side, delivering some #UD with
an error code (although the guest behaviour does appear to be correct,
so perhaps hardware swallows it). I will do a companion
