hypervisor: whpx: fix segment limits
It seems that WHPX also wants its segment Limit value to be in bytes
(unaffected by the Granularity flag), similar to KVM.
This also fixes a compilation failure (using "limit" rather than
"limit_bytes").
Tested with a 32-bit bzImage kernel on Windows 10 host.
Fixes: 2fc3047b9b07 ("hypervisor: x86_64: clarify Segment limit units")
Change-Id: Ifa013b3687a5febd4d36b3a830c9c6995cc2bdb9
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5743006
Reviewed-by: Noah Gold <nkgold@google.com>
Auto-Submit: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Noah Gold <nkgold@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.