Re: [Xen-devel] x86/vMSI-X emulation issue

2016-03-24 Thread Paul Durrant
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 24 March 2016 09:47 > To: Paul Durrant > Cc: Andrew Cooper; xen-devel > Subject: RE: [Xen-devel] x86/vMSI-X emulation issue > > >>> On 24.03.16 at 10:39, <paul.durr...@ci

Re: [Xen-devel] x86/vMSI-X emulation issue

2016-03-24 Thread Jan Beulich
>>> On 24.03.16 at 10:39, <paul.durr...@citrix.com> wrote: >> -Original Message- >> From: Jan Beulich [mailto:jbeul...@suse.com] >> Sent: 24 March 2016 09:35 >> To: Paul Durrant >> Cc: Andrew Cooper; xen-devel >> Subject: RE: [Xen-devel

Re: [Xen-devel] x86/vMSI-X emulation issue

2016-03-24 Thread Paul Durrant
> -Original Message- > From: Jan Beulich [mailto:jbeul...@suse.com] > Sent: 24 March 2016 09:35 > To: Paul Durrant > Cc: Andrew Cooper; xen-devel > Subject: RE: [Xen-devel] x86/vMSI-X emulation issue > > >>> On 24.03.16 at 10:09, <paul.durr...@cit

Re: [Xen-devel] x86/vMSI-X emulation issue

2016-03-24 Thread Jan Beulich
>>> On 24.03.16 at 10:09, wrote: >> From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of Jan >> Beulich >> Sent: 24 March 2016 07:52 >> > 2) Do aforementioned chopping automatically on seeing >> > X86EMUL_UNHANDLEABLE, on the basis that the .check >>

Re: [Xen-devel] x86/vMSI-X emulation issue

2016-03-24 Thread Paul Durrant
> -Original Message- > From: Xen-devel [mailto:xen-devel-boun...@lists.xen.org] On Behalf Of Jan > Beulich > Sent: 24 March 2016 07:52 > To: xen-devel > Cc: Andrew Cooper > Subject: Re: [Xen-devel] x86/vMSI-X emulation issue > > >>> On 23.03.16 at 18:05

Re: [Xen-devel] x86/vMSI-X emulation issue

2016-03-24 Thread Jan Beulich
>>> On 23.03.16 at 18:05, wrote: > All, > > so I've just learned that Windows (at least some versions and some > of their code paths) use REP MOVSD to read/write the MSI-X table. > The way at least msixtbl_write() works is not compatible with this > (msixtbl_read() also seems

[Xen-devel] x86/vMSI-X emulation issue

2016-03-23 Thread Jan Beulich
All, so I've just learned that Windows (at least some versions and some of their code paths) use REP MOVSD to read/write the MSI-X table. The way at least msixtbl_write() works is not compatible with this (msixtbl_read() also seems affected, albeit to a lesser degree), and apparently it just