On Wed, 25 Jan 2017, Marc Zyngier wrote:
> Hi Thomas,
>
> Any comment on that one?
Yes, it got lost in my backlog. Thanks for the reminder.
tglx
On Wed, 25 Jan 2017, Marc Zyngier wrote:
> Hi Thomas,
>
> Any comment on that one?
Yes, it got lost in my backlog. Thanks for the reminder.
tglx
Hi Thomas,
Any comment on that one?
Thanks,
M.
On 17/01/17 16:00, Marc Zyngier wrote:
> Since commit f3b0946d629c ("genirq/msi: Make sure PCI MSIs are
> activated early"), we can end-up activating a PCI/MSI twice (once
> at allocation time, and once at startup time).
>
> This is
Hi Thomas,
Any comment on that one?
Thanks,
M.
On 17/01/17 16:00, Marc Zyngier wrote:
> Since commit f3b0946d629c ("genirq/msi: Make sure PCI MSIs are
> activated early"), we can end-up activating a PCI/MSI twice (once
> at allocation time, and once at startup time).
>
> This is
Since commit f3b0946d629c ("genirq/msi: Make sure PCI MSIs are
activated early"), we can end-up activating a PCI/MSI twice (once
at allocation time, and once at startup time).
This is normally of no consequences, except that there is some
HW out there that may misbehave if activate is used more
Since commit f3b0946d629c ("genirq/msi: Make sure PCI MSIs are
activated early"), we can end-up activating a PCI/MSI twice (once
at allocation time, and once at startup time).
This is normally of no consequences, except that there is some
HW out there that may misbehave if activate is used more
6 matches
Mail list logo