[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] [PATCH] x86/MSI-X: correctly track interrupt masking state

On 22/04/16 08:20, Jan Beulich wrote:
> When a guest unmasks MSI-X interrupts before enabling MSI-X on the
> device, so far nothing updates the {host,guest}_masked internal state;
> this to date only gets done when MSI-X is already enabled. This is why
> half way recent Linux works (as it enables MSI-X first), while Windows
> doesn't (as it enables MSI-X only after having set up und unmasked all
> vectors). Since with a successful write to the vector control field
> everything is ready internally, we should also update internal tracking
> state there, regardless of the device's MSI-X enabled state.
> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>

Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.