On 18/07/2016 23:03, li...@eikelenboom.it wrote:
> On 2016-07-18 22:57, Andrew Cooper wrote:
>> On 18/07/2016 20:26, Sander Eikelenboom wrote:
>>> Monday, July 18, 2016, 7:48:20 PM, you wrote:
>>>
On 18/07/16 11:21, li...@eikelenboom.it wrote:
> Hi Jan,
>
> It seems that since
On 2016-07-18 22:57, Andrew Cooper wrote:
On 18/07/2016 20:26, Sander Eikelenboom wrote:
Monday, July 18, 2016, 7:48:20 PM, you wrote:
On 18/07/16 11:21, li...@eikelenboom.it wrote:
Hi Jan,
It seems that since your patch series starting with commit:
2016-06-22 x86/vMSI-X: defer intercept
On 18/07/2016 20:26, Sander Eikelenboom wrote:
> Monday, July 18, 2016, 7:48:20 PM, you wrote:
>
>> On 18/07/16 11:21, li...@eikelenboom.it wrote:
>>> Hi Jan,
>>>
>>> It seems that since your patch series starting with commit:
>>> 2016-06-22 x86/vMSI-X: defer intercept handler registration
>>>
Monday, July 18, 2016, 7:48:20 PM, you wrote:
> On 18/07/16 11:21, li...@eikelenboom.it wrote:
>> Hi Jan,
>>
>> It seems that since your patch series starting with commit:
>> 2016-06-22 x86/vMSI-X: defer intercept handler registration
>> 74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798
>>
>> The
On 18/07/16 11:21, li...@eikelenboom.it wrote:
> Hi Jan,
>
> It seems that since your patch series starting with commit:
> 2016-06-22 x86/vMSI-X: defer intercept handler registration
> 74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798
>
> The shutdown of a guest which has a PCI device passed through which
Hi Jan,
It seems that since your patch series starting with commit:
2016-06-22 x86/vMSI-X: defer intercept handler registration
74c6dc2d0ac4dcab0c6243cdf6ed550c1532b798
The shutdown of a guest which has a PCI device passed through which uses
MSI-X interrupts causes
a host crash, see the splat