Hi, Alex
Clearly this has only been tested for a single instance of an AER error
event and resume per device. Are the things you're intending to block
actually blocked for subsequent events? Note how complete_all() fills
the done field to let all current and future waiters go through and
nowhe
On Mon, 1 Aug 2016 10:14:06 +0800
Zhou Jie wrote:
> Hi, Alex
>
> On 2016/7/30 1:12, Alex Williamson wrote:
> > On Tue, 19 Jul 2016 15:32:43 +0800
> > Zhou Jie wrote:
> >
> >> From: Chen Fan
> >>
> >> During aer err occurs and resume do following to
> >> protect device from being accessed.
>
Hi, Alex
On 2016/7/30 1:12, Alex Williamson wrote:
On Tue, 19 Jul 2016 15:32:43 +0800
Zhou Jie wrote:
From: Chen Fan
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar regi
On Tue, 19 Jul 2016 15:32:43 +0800
Zhou Jie wrote:
> From: Chen Fan
>
> During aer err occurs and resume do following to
> protect device from being accessed.
> 1. Make config space read only.
> 2. Disable INTx/MSI Interrupt.
> 3. Do nothing for bar regions.
>
> Signed-off-by: Zhou Jie
> ---
From: Chen Fan
During aer err occurs and resume do following to
protect device from being accessed.
1. Make config space read only.
2. Disable INTx/MSI Interrupt.
3. Do nothing for bar regions.
Signed-off-by: Zhou Jie
---
drivers/vfio/pci/vfio_pci.c | 30 ++
