Re: About MONITOR/MWAIT in i386 CPU model

On 11/14/2019 6:47 AM, Eduardo Habkost wrote: On Wed, Nov 13, 2019 at 04:42:25PM +0800, Tao Xu wrote: Hi Eduardo， After kvm use "-overcommit cpu-pm=on" to expose MONITOR/MWAIT (commit id 6f131f13e68d648a8e4f083c667ab1acd88ce4cd), the MONITOR/MWAIT feature in CPU model (phenom core2duo coreduo n

Re: About MONITOR/MWAIT in i386 CPU model

On Wed, Nov 13, 2019 at 04:42:25PM +0800, Tao Xu wrote: > Hi Eduardo， > > After kvm use "-overcommit cpu-pm=on" to expose MONITOR/MWAIT > (commit id 6f131f13e68d648a8e4f083c667ab1acd88ce4cd), the MONITOR/MWAIT > feature in CPU model (phenom core2duo coreduo n270 Opteron_G3 EPYC Snowridge > Denvert

About MONITOR/MWAIT in i386 CPU model

Hi Eduardo， After kvm use "-overcommit cpu-pm=on" to expose MONITOR/MWAIT (commit id 6f131f13e68d648a8e4f083c667ab1acd88ce4cd), the MONITOR/MWAIT feature in CPU model (phenom core2duo coreduo n270 Opteron_G3 EPYC Snowridge Denverton) may be unused. For example, when we boot a guest with Denver