On Wed, 29 Oct 2025 at 14:23, Bernhard Beschow <[email protected]> wrote: > > This series adds KVM support to the imx8mp-evk machine, allowing it to run > guests with KVM acceleration. Inspiration was taken from the virt machine. > This > required a device tree quirk for the guest clock to be kept in sync with the > host. Without this quirk the guest's clock would advance with factor <host > system counter> / 8Mhz. > > Testing done: > * Run `qemu-system-aarch64 -M imx8mp-evk -accel kvm -smp 4` under > `qemu-system-aarch64 -M virt,secure=on,virtualization=on,gic-version=4 \ > -cpu cortex-a72 -smp 4 -accel tcg` and `qemu-system-aarch64 -M imx8mp-evk \ > -accel tcg -smp 4". Observe that the `date` command reflects the host's > date. > > v2: > * Mention various tradeoffs in the board documentation (Peter) > * Accommodate for single-binary (Peter, Pierrick) by having CPU defaults > > Bernhard Beschow (2): > hw/arm/imx8mp-evk: Add KVM support > hw/arm/imx8mp-evk: Fix guest time in KVM mode
Thanks, I've applied this to target-arm.next. I tweaked the docs for the bit about security slightly to add a link to the security policy page: -* Unlike other machines with KVM support, the ``imx8mp-evk`` machine makes no - attempt to protect itself from malicious guests. If you don't trust your +* The ``imx8mp-evk`` machine is not included under the "virtualization use + case" of :doc:`QEMU's security policy </system/security>`. This means that + you should not trust that it can contain malicious guests, whether it is + run using TCG or KVM. If you don't trust your -- PMM
