Hi, Alex
>> Do we even need a timer? What if we simply spin?
>>
>> for (i = 0; i < 1000; i++) {
>> if (vdev->pci_aer_resume_signaled) {
>> break;
>> }
>> g_usleep(1000);
>> }
>>
>> if (i == 1000) {
>> /* We failed */
>> } else {
>> /* Proceed with reset */
>> }
>>
>>
Hi, Alex
3. Stall any access to the device until resume is signaled.
The code below doesn't actually do this, mmaps are disabled, but that
just means any device access will use the slow path through QEMU. That
path is still fully enabled and so is config space access.
I will modify the cod
On 2016/5/19 10:18, Alex Williamson wrote:
On Thu, 19 May 2016 09:49:00 +0800
Zhou Jie wrote:
On 2016/5/19 2:26, Alex Williamson wrote:
On Wed, 18 May 2016 11:31:09 +0800
Zhou Jie wrote:
From: Chen Fan
For supporting aer recovery, host and guest would run the same aer
recovery code, th
On 2016/5/19 10:18, Alex Williamson wrote:
On Thu, 19 May 2016 09:49:00 +0800
Zhou Jie wrote:
On 2016/5/19 2:26, Alex Williamson wrote:
On Wed, 18 May 2016 11:31:09 +0800
Zhou Jie wrote:
From: Chen Fan
For supporting aer recovery, host and guest would run the same aer
recovery code, th
On Thu, 19 May 2016 09:49:00 +0800
Zhou Jie wrote:
> On 2016/5/19 2:26, Alex Williamson wrote:
> > On Wed, 18 May 2016 11:31:09 +0800
> > Zhou Jie wrote:
> >
> >> From: Chen Fan
> >>
> >> For supporting aer recovery, host and guest would run the same aer
> >> recovery code, that would do the
On 2016/5/19 2:26, Alex Williamson wrote:
On Wed, 18 May 2016 11:31:09 +0800
Zhou Jie wrote:
From: Chen Fan
For supporting aer recovery, host and guest would run the same aer
recovery code, that would do the secondary bus reset if the error
is fatal, the aer recovery process:
1. error_de
On Wed, 18 May 2016 11:31:09 +0800
Zhou Jie wrote:
> From: Chen Fan
>
> For supporting aer recovery, host and guest would run the same aer
> recovery code, that would do the secondary bus reset if the error
> is fatal, the aer recovery process:
> 1. error_detected
> 2. reset_link (if fatal)
From: Chen Fan
For supporting aer recovery, host and guest would run the same aer
recovery code, that would do the secondary bus reset if the error
is fatal, the aer recovery process:
1. error_detected
2. reset_link (if fatal)
3. slot_reset/mmio_enabled
4. resume
It indicates that host w
