diff options
| author |   Wei Yang <weiyang@linux.vnet.ibm.com> | 2015-10-22 09:22:17 +0800 |
|---|---|---|
| committer |   Michael Ellerman <mpe@ellerman.id.au> | 2016-02-10 12:04:57 +1100 |
| commit | f2dd0afeea0ed0e740c4b066c76a556a8b870e58 (patch) | |
| tree | 9e455698169dce902847adbe75ff378d489bedef /tools/perf/scripts/python/call-graph-from-postgresql.py | |
| parent | powerpc/powernv: use one M64 BAR in Single PE mode for one VF BAR (diff) | |
| download | wireguard-linux-f2dd0afeea0ed0e740c4b066c76a556a8b870e58.tar.xz wireguard-linux-f2dd0afeea0ed0e740c4b066c76a556a8b870e58.zip | |
powerpc/powernv: replace the hard coded boundary with gate
At the moment 64bit-prefetchable window can be maximum 64GB, which is
currently got from device tree. This means that in shared mode the maximum
supported VF BAR size is 64GB/256=256MB. While this size could exhaust the
whole 64bit-prefetchable window. This is a design decision to set a
boundary to 64MB of the VF BAR size. Since VF BAR size with 64MB would
occupy a quarter of the 64bit-prefetchable window, this is affordable.
This patch replaces magic limit of 64MB with "gate", which is 1/4 of the
M64 Segment Size(m64_segsize >> 2) and adds comment to explain the reason
for it.
Signed-off-by: Wei Yang <weiyang@linux.vnet.ibm.com>
Reviewed-by: Gavin Shan <gwshan@linux.vent.ibm.com>
Acked-by: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Michael Ellerman <mpe@ellerman.id.au>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions