aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/sctop.py
diff options
context:
space:
mode:
authorSantosh Shilimkar <[email protected]>2014-04-24 15:30:01 +0000
committerSantosh Shilimkar <[email protected]>2014-05-05 22:11:13 +0000
commit8febcaa2aac184d7e729acb75e9c4b80b04ad1b9 (patch)
treedc67484f4b629e5edfbac0850c2a18ac00a7fdf4 /tools/perf/scripts/python/sctop.py
parentLinux 3.15-rc1 (diff)
downloadkernel-8febcaa2aac184d7e729acb75e9c4b80b04ad1b9.tar.gz
kernel-8febcaa2aac184d7e729acb75e9c4b80b04ad1b9.zip
device: introduce per device dma_pfn_offset
On few architectures, there are few restrictions on DMAble area of system RAM. That also means that devices needs to know about this restrictions so that the dma_masks can be updated accordingly and dma address translation helpers can add/subtract the dma offset. In most of cases DMA addresses can be performed using offset value of Bus address space relatively to physical address space as following: PFN->DMA: __pfn_to_phys(pfn + [-]dma_pfn_offset) DMA->PFN: __phys_to_pfn(dma_addr) + [-]dma_pfn_offset So we introduce per device dma_pfn_offset which can be popullated by architecture init code while creating the devices. Cc: Greg Kroah-Hartman <[email protected]> Cc: Russell King <[email protected]> Cc: Arnd Bergmann <[email protected]> Cc: Olof Johansson <[email protected]> Cc: Grant Likely <[email protected]> Cc: Catalin Marinas <[email protected]> Cc: Linus Walleij <[email protected]> Reviewed-by: Rob Herring <[email protected]> Signed-off-by: Grygorii Strashko <[email protected]> Signed-off-by: Santosh Shilimkar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/sctop.py')
0 files changed, 0 insertions, 0 deletions