diff options
author | Oliver O'Halloran <oohall@gmail.com> | 2020-07-22 16:57:02 +1000 |
---|---|---|
committer | Michael Ellerman <mpe@ellerman.id.au> | 2020-07-26 23:34:22 +1000 |
commit | 01e12629af4e0e4864ed4d83e07783d7cb5b06be (patch) | |
tree | e4ed9e54f0ae7fc945e207dbde797657cdbcae0b /fs/debugfs | |
parent | 7a52ffabe867c0d93e47af113e5107340974047a (diff) |
powerpc/powernv/pci: Add explicit tracking of the DMA setup state
There's an optimisation in the PE setup which skips performing DMA
setup for a PE if we only have bridges in a PE. The assumption being
that only "real" devices will DMA to system memory, which is probably
fair. However, if we start off with only bridge devices in a PE then
add a non-bridge device the new device won't be able to use DMA because
we never configured it.
Fix this (admittedly pretty weird) edge case by tracking whether we've done
the DMA setup for the PE or not. If a non-bridge device is added to the PE
(via rescan or hotplug, or whatever) we can set up DMA on demand.
This also means the only remaining user of the old "DMA Weight" code is
the IODA1 DMA setup code that it was originally added for, which is good.
Signed-off-by: Oliver O'Halloran <oohall@gmail.com>
Reviewed-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Link: https://lore.kernel.org/r/20200722065715.1432738-3-oohall@gmail.com
Diffstat (limited to 'fs/debugfs')
0 files changed, 0 insertions, 0 deletions