summary refs log tree commit diff
path: root/Cargo.lock
diff options
context:
space:
mode:
authorZach Reizner <zachr@google.com>2018-02-22 22:05:55 -0800
committerchrome-bot <chrome-bot@chromium.org>2018-03-07 16:54:45 -0800
commita5358e8ffd53d04750dc2c3376abc3fb5df92659 (patch)
tree9a69ba015ec288d6853317060dc3b453b4f955be /Cargo.lock
parent5b6b192e34311924388715f1981e9ffca7c4b53c (diff)
downloadcrosvm-a5358e8ffd53d04750dc2c3376abc3fb5df92659.tar
crosvm-a5358e8ffd53d04750dc2c3376abc3fb5df92659.tar.gz
crosvm-a5358e8ffd53d04750dc2c3376abc3fb5df92659.tar.bz2
crosvm-a5358e8ffd53d04750dc2c3376abc3fb5df92659.tar.lz
crosvm-a5358e8ffd53d04750dc2c3376abc3fb5df92659.tar.xz
crosvm-a5358e8ffd53d04750dc2c3376abc3fb5df92659.tar.zst
crosvm-a5358e8ffd53d04750dc2c3376abc3fb5df92659.zip
sys_util: add PollContext interface for using epoll
A common cause of silent 100% CPU usage on otherwise idle VMs is because
some poll loop is waiting on sockets that were hung up on. An unrelated
issue is that using the Poller interface requires dynamic allocation on
every poll call for dynamically sized poll lists.

The PollContext struct detects and warns about the first problem at runtime
and solves the latter problem.

TEST=cargo test -p sys_util
BUG=chromium:816692

Change-Id: I42a9c961db07191d25bcba77c5136f5729400ec9
Reviewed-on: https://chromium-review.googlesource.com/933870
Commit-Ready: Zach Reizner <zachr@chromium.org>
Tested-by: Zach Reizner <zachr@chromium.org>
Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
Diffstat (limited to 'Cargo.lock')
0 files changed, 0 insertions, 0 deletions