On Tue, Aug 01, 2017 at 06:59:08PM +0100, Robin Murphy wrote:
> Currently, we handle all DMA aliases equally when calculating MSI
> requester IDs for the generic infrastructure. This turns out to be the
> wrong thing to do in the face of pure DMA quirks like those of Marvell
> SATA cards, where in
On Tue, Aug 01, 2017 at 06:59:08PM +0100, Robin Murphy wrote:
> Currently, we handle all DMA aliases equally when calculating MSI
> requester IDs for the generic infrastructure. This turns out to be the
> wrong thing to do in the face of pure DMA quirks like those of Marvell
> SATA cards, where in
On 01/08/17 18:59, Robin Murphy wrote:
> Currently, we handle all DMA aliases equally when calculating MSI
> requester IDs for the generic infrastructure. This turns out to be the
> wrong thing to do in the face of pure DMA quirks like those of Marvell
> SATA cards, where in the usual case the
On 01/08/17 18:59, Robin Murphy wrote:
> Currently, we handle all DMA aliases equally when calculating MSI
> requester IDs for the generic infrastructure. This turns out to be the
> wrong thing to do in the face of pure DMA quirks like those of Marvell
> SATA cards, where in the usual case the
Currently, we handle all DMA aliases equally when calculating MSI
requester IDs for the generic infrastructure. This turns out to be the
wrong thing to do in the face of pure DMA quirks like those of Marvell
SATA cards, where in the usual case the last thing seen in the alias
walk is the DMA
Currently, we handle all DMA aliases equally when calculating MSI
requester IDs for the generic infrastructure. This turns out to be the
wrong thing to do in the face of pure DMA quirks like those of Marvell
SATA cards, where in the usual case the last thing seen in the alias
walk is the DMA
6 matches
Mail list logo