aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/syscall-counts-by-pid.py
diff options
context:
space:
mode:
authorSuganath Prabu <[email protected]>2019-07-30 07:43:57 +0000
committerMartin K. Petersen <[email protected]>2019-07-30 16:46:06 +0000
commitdf9a606184bfdb5ae3ca9d226184e9489f5c24f7 (patch)
tree02a6dfc7230096d05565df8e7eea5dae557eae7a /tools/perf/scripts/python/syscall-counts-by-pid.py
parentscsi: hpsa: remove printing internal cdb on tag collision (diff)
downloadkernel-df9a606184bfdb5ae3ca9d226184e9489f5c24f7.tar.gz
kernel-df9a606184bfdb5ae3ca9d226184e9489f5c24f7.zip
scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA
Although SAS3 & SAS3.5 IT HBA controllers support 64-bit DMA addressing, as per hardware design, if DMA-able range contains all 64-bits set (0xFFFFFFFF-FFFFFFFF) then it results in a firmware fault. E.g. SGE's start address is 0xFFFFFFFF-FFFF000 and data length is 0x1000 bytes. when HBA tries to DMA the data at 0xFFFFFFFF-FFFFFFFF location then HBA will fault the firmware. Driver will set 63-bit DMA mask to ensure the above address will not be used. Cc: <[email protected]> # 5.1.20+ Signed-off-by: Suganath Prabu <[email protected]> Reviewed-by: Christoph Hellwig <[email protected]> Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions