diff options
| author | Thiago Jung Bauermann <[email protected]> | 2020-08-18 19:11:26 -0300 |
|---|---|---|
| committer | Michael Ellerman <[email protected]> | 2020-09-14 23:07:14 +1000 |
| commit | eae9eec476d13fad9af6da1f44a054ee02b7b161 (patch) | |
| tree | daa6ac7bb25222157542c1623c5157a2f26119c4 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | 231b232df8f67e7d37af01259c21f2a131c3911e (diff) | |
powerpc/pseries/svm: Allocate SWIOTLB buffer anywhere in memory
POWER secure guests (i.e., guests which use the Protected Execution
Facility) need to use SWIOTLB to be able to do I/O with the
hypervisor, but they don't need the SWIOTLB memory to be in low
addresses since the hypervisor doesn't have any addressing limitation.
This solves a SWIOTLB initialization problem we are seeing in secure
guests with 128 GB of RAM: they are configured with 4 GB of
crashkernel reserved memory, which leaves no space for SWIOTLB in low
addresses.
To do this, we use mostly the same code as swiotlb_init(), but
allocate the buffer using memblock_alloc() instead of
memblock_alloc_low().
Fixes: 2efbc58f157a ("powerpc/pseries/svm: Force SWIOTLB for secure guests")
Signed-off-by: Thiago Jung Bauermann <[email protected]>
Reviewed-by: Konrad Rzeszutek Wilk <[email protected]>
Signed-off-by: Michael Ellerman <[email protected]>
Link: https://lore.kernel.org/r/[email protected]
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions