aboutsummaryrefslogtreecommitdiffstats
path: root/tools/perf/scripts/python/failed-syscalls-by-pid.py
diff options
context:
space:
mode:
authorXuewei Zhang <[email protected]>2018-09-06 20:37:19 +0000
committerMartin K. Petersen <[email protected]>2018-09-17 06:57:10 +0000
commit83e32a5910772e1475d3640a429b7686695f04d1 (patch)
treebded4bee164404584632e082179544f243791a8f /tools/perf/scripts/python/failed-syscalls-by-pid.py
parentscsi: ibmvscsis: Ensure partition name is properly NUL terminated (diff)
downloadkernel-83e32a5910772e1475d3640a429b7686695f04d1.tar.gz
kernel-83e32a5910772e1475d3640a429b7686695f04d1.zip
scsi: sd: Contribute to randomness when running rotational device
Currently a scsi device won't contribute to kernel randomness when it uses blk-mq. Since we commonly use scsi on rotational device with blk-mq, it make sense to keep contributing to kernel randomness in these cases. This is especially important for virtual machines. commit b5b6e8c8d3b4 ("scsi: virtio_scsi: fix IO hang caused by automatic irq vector affinity") made all virtio-scsi device to use blk-mq, which does not contribute to randomness today. So for a virtual machine only having virtio-scsi disk (which is common), it will simple stop getting randomness from its disks in today's implementation. With this patch, if the above VM has rotational virtio-scsi device, then it can still benefit from the entropy generated from the disk. Reported-by: Xuewei Zhang <[email protected]> Signed-off-by: Xuewei Zhang <[email protected]> Reviewed-by: Ming Lei <[email protected]> Reviewed-by: Maciej Żenczykowski <[email protected]> Reviewed-by: Bart Van Assche <[email protected]> Signed-off-by: Martin K. Petersen <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/failed-syscalls-by-pid.py')
0 files changed, 0 insertions, 0 deletions