summaryrefslogtreecommitdiffstats
path: root/contrib/llvm/tools/lldb/source/Host/common/HostThread.cpp
diff options
context:
space:
mode:
authorbryanv <bryanv@FreeBSD.org>2015-01-27 05:34:46 +0000
committerbryanv <bryanv@FreeBSD.org>2015-01-27 05:34:46 +0000
commit24b29c5c11104c8a5215774fe9d7a33438938df5 (patch)
tree9186ace5e9c12d735ce3c9bdaa63cde3dd569f9c /contrib/llvm/tools/lldb/source/Host/common/HostThread.cpp
parent8827f4c641460df2abec40e96b64c08a617b8322 (diff)
downloadFreeBSD-src-24b29c5c11104c8a5215774fe9d7a33438938df5.zip
FreeBSD-src-24b29c5c11104c8a5215774fe9d7a33438938df5.tar.gz
Rework vtblk dump handling of in flight requests
Previously, the driver resets the device and abandon the requests that are caught in flight when the dump was initiated. This was problematic if the system is resumed after the dump is completed. While that is probably not the typical action, it is simple to rework the driver to very likely have the device usable after the dump without making it more likely for the dump to fail. The in flight requests are simply queued for completion once the dump is finished. Requested by: markj MFC after: 1 month
Diffstat (limited to 'contrib/llvm/tools/lldb/source/Host/common/HostThread.cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud