From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eduardo Habkost Subject: Re: [PATCH v2 1/2] kvm: support -realtime cpu-pm=on|off Date: Wed, 13 Jun 2018 17:35:52 -0300 Message-ID: <20180613203552.GO7451@localhost.localdomain> References: <20180612184616.90838-1-mst@redhat.com> <20180612184616.90838-2-mst@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paolo Bonzini , Marcelo Tosatti , qemu-devel@nongnu.org, kvm@vger.kernel.org, Richard Henderson To: "Michael S. Tsirkin" Return-path: Content-Disposition: inline In-Reply-To: <20180612184616.90838-2-mst@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel2=m.gmane.org@nongnu.org Sender: "Qemu-devel" List-Id: kvm.vger.kernel.org On Tue, Jun 12, 2018 at 09:47:11PM +0300, Michael S. Tsirkin wrote: > With this flag, kvm allows guest to control host CPU power state. This > increases latency for other processes using same host CPU in an > unpredictable way, but if decreases idle entry/exit times for the > running VCPU. > > Follow-up patches will expose this capability to guest > (using mwait leaf). > > Based on a patch by Wanpeng Li . > > Signed-off-by: Michael S. Tsirkin The interface makes sense to me, but: > +extern bool enable_cpu_pm; Why do we need a global variable if initialization code can call qemu_opt_get_bool() directly? -- Eduardo