Takaya Saeki cb6e74a094 cros_async: add a command-line option to switch Executor backend ... Currently Executor internally decides which backend to use, such as FdExecutor vs URingExecutor on Linux. This makes it hard to test both FdExecutor and URingExecutor. In addition, we came across the uring instability issue (b:238965061), thus we need a way to explicitly switch the polling backend to mitigate the issue. This commit adds a command-line option to explicitly configure the Executor's polling backend. BUG=b:239154263 TEST=confirmed crosvm --async-executor correcly switchs the Executor for `crosvm --async-executor epoll (or uring) device gpu --socket /tmp/gpu.sock` command. Used additional debug log to tell which executor is running, which is not commited Change-Id: Ib310d9edc8ab6005f1b7f210b03668b9a45fa73f Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3811014 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Takaya Saeki <takayas@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com>		2022-09-29 05:12:12 +00:00
..
src	cros_async: add a command-line option to switch Executor backend	2022-09-29 05:12:12 +00:00
Cargo.toml	cros_async: upstream Windows support.	2022-04-19 22:19:05 +00:00