On Thu, Dec 14, 2017 at 08:20:18AM -0700, Alex Williamson wrote:
> DPC supports shared interrupts, but it plays very loosely with testing
> whether the interrupt is generated by DPC before generating spurious
> log messages, such as:
>
> dpc :10:01.2:pcie010: DPC containment event, status:0x1
On Thu, Dec 14, 2017 at 08:20:18AM -0700, Alex Williamson wrote:
> DPC supports shared interrupts, but it plays very loosely with testing
> whether the interrupt is generated by DPC before generating spurious
> log messages, such as:
>
> dpc :10:01.2:pcie010: DPC containment event, status:0x1
DPC supports shared interrupts, but it plays very loosely with testing
whether the interrupt is generated by DPC before generating spurious
log messages, such as:
dpc :10:01.2:pcie010: DPC containment event, status:0x1f00 source:0x
Testing the status register for zero or -1 is not suffic
3 matches
Mail list logo