On 2018年07月02日 13:14, Jan Kiszka wrote:
On 2018-07-02 05:40, Jason Wang wrote:
On 2018年06月30日 14:13, Jan Kiszka wrote:
On 2018-04-05 19:41, Jan Kiszka wrote:
From: Jan Kiszka
Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
interrupt sources even if the guest did
On 2018-07-02 05:40, Jason Wang wrote:
>
>
> On 2018年06月30日 14:13, Jan Kiszka wrote:
>> On 2018-04-05 19:41, Jan Kiszka wrote:
>>> From: Jan Kiszka
>>>
>>> Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
>>> interrupt sources even if the guest did no consumed the pending
On 2018年06月30日 14:13, Jan Kiszka wrote:
On 2018-04-05 19:41, Jan Kiszka wrote:
From: Jan Kiszka
Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
interrupt sources even if the guest did no consumed the pending one,
easily causing interrupt storms.
Issue was observabl
On 2018-04-05 19:41, Jan Kiszka wrote:
> From: Jan Kiszka
>
> Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
> interrupt sources even if the guest did no consumed the pending one,
> easily causing interrupt storms.
>
> Issue was observable with Linux 4.16 e1000e driver
From: Jan Kiszka
Only signal MSI/MSI-X events on rising edges. So far we re-triggered the
interrupt sources even if the guest did no consumed the pending one,
easily causing interrupt storms.
Issue was observable with Linux 4.16 e1000e driver when MSI-X was used.
Vector 2 was causing interrupt s
