Re: [PATCH V3 0/2] improve -overcommit cpu-pm=on|off

04.06.2024 03:02, Zide Chen wrote: Currently, if running "-overcommit cpu-pm=on" on hosts that don't have MWAIT support, the MWAIT/MONITOR feature is advertised to the guest and executing MWAIT/MONITOR on the guest triggers #UD. Typically #UD takes priority over VM-Exit interception checks and K

Re: [PATCH V3 0/2] improve -overcommit cpu-pm=on|off

On 6/5/2024 6:49 AM, Igor Mammedov wrote: > On Mon, 3 Jun 2024 17:02:20 -0700 > Zide Chen wrote: > >> Currently, if running "-overcommit cpu-pm=on" on hosts that don't >> have MWAIT support, the MWAIT/MONITOR feature is advertised to the >> guest and executing MWAIT/MONITOR on the guest trigg

Re: [PATCH V3 0/2] improve -overcommit cpu-pm=on|off

On Mon, 3 Jun 2024 17:02:20 -0700 Zide Chen wrote: > Currently, if running "-overcommit cpu-pm=on" on hosts that don't > have MWAIT support, the MWAIT/MONITOR feature is advertised to the > guest and executing MWAIT/MONITOR on the guest triggers #UD. > > Typically #UD takes priority over VM-Exi

[PATCH V3 0/2] improve -overcommit cpu-pm=on|off

Currently, if running "-overcommit cpu-pm=on" on hosts that don't have MWAIT support, the MWAIT/MONITOR feature is advertised to the guest and executing MWAIT/MONITOR on the guest triggers #UD. Typically #UD takes priority over VM-Exit interception checks and KVM doesn't emulate MONITOR/MWAIT. Thi