commit | 479efab2f5d658a72c5ea66d095f9bd3ae3fe76b | [log] [tgz] |
---|---|---|
author | Xiong Zhang <xiong.y.zhang@intel.corp-partner.google.com> | Thu Oct 28 23:39:10 2021 +0800 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Nov 05 19:35:09 2021 +0000 |
tree | befa7fbdd6f681223736a699dbdec9a96f7414ec | |
parent | 7a976d3a8aa685567f1c00efb5f82a27f4942eb9 [diff] |
devices: Don't return bar info if memory/io is disabled get_bar_configuration() returnis bar's info, this ignores memory/io enable bit. Usually driver disable memory/io first, then wrtie 0xFFFFFFFF to probe bar's existence and size, finally write real address and enable memory/io. if get_bar_configuration is called after mmio/io disabled, current it may return invalid info. In order to filter these invalid info, this commit checks memory/io enable bit, only return info at memory/io enabled. BUG=b:174705996 TEST=carto test -p devices Change-Id: Ib8bf1a7f7f959025117f319f8f6c5a9e5efea2e2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3252779 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
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 Chrome OS 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 Chrome OS devices.