aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/call-graph-from-postgresql.py
diff options
context:
space:
mode:
authorAmit Shah <[email protected]>2014-07-10 15:42:35 +0530
committerHerbert Xu <[email protected]>2014-07-14 20:48:17 +0800
commite052dbf554610e2104c5a7518c4d8374bed701bb (patch)
treeb765a30d4833a04b7576eae0364bcd2d725ac8d0 /tools/perf/scripts/python/call-graph-from-postgresql.py
parentd3cc7996473a7bdd33256029988ea690754e4e2a (diff)
hwrng: virtio - ensure reads happen after successful probe
The hwrng core asks for random data in the hwrng_register() call itself from commit d9e7972619. This doesn't play well with virtio -- the DRIVER_OK bit is only set by virtio core on a successful probe, and we're not yet out of our probe routine when this call is made. This causes the host to not acknowledge any requests we put in the virtqueue, and the insmod or kernel boot process just waits for data to arrive from the host, which never happens. CC: Kees Cook <[email protected]> CC: Jason Cooper <[email protected]> CC: Herbert Xu <[email protected]> CC: <[email protected]> # For v3.15+ Reviewed-by: Jason Cooper <[email protected]> Signed-off-by: Amit Shah <[email protected]> Signed-off-by: Herbert Xu <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions