commit | 8831cf556082dab9d7c3e7acff7f43c2556b9f02 | [log] [tgz] |
---|---|---|
author | Idan Raiter <idanr@google.com> | Tue Apr 11 23:40:57 2023 +0000 |
committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Thu Apr 27 18:52:14 2023 +0000 |
tree | 2c7c96afec4b6158e4c7b8439cef994baeeb60aa | |
parent | 1661dfca89bcce7c90ef9fa6c6d3600277860ac6 [diff] |
audio: Windows: Fix realtime priority not being set Both single and multi process did not have realtime priority, due to us dropping the multimedia trick handle in set_audio_thread_priority where we should be holding it until the thread is finished. BUG=b:276698085 TEST=Process explorer -> properties -> threads -> base priority increases from 8 to 24 Change-Id: Ia9199f4816e087046b8718e85c60abc9479ec0f3 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4416757 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Idan Raiter <idanr@google.com>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the ChromeOS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on ChromeOS devices.