From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51476) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fTp9k-0003aT-VD for qemu-devel@nongnu.org; Fri, 15 Jun 2018 09:52:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fTp9g-0003SS-VY for qemu-devel@nongnu.org; Fri, 15 Jun 2018 09:52:49 -0400 Received: from mx1.redhat.com ([209.132.183.28]:48380) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1fTp9g-0003Pr-PQ for qemu-devel@nongnu.org; Fri, 15 Jun 2018 09:52:44 -0400 Date: Fri, 15 Jun 2018 16:52:28 +0300 From: "Michael S. Tsirkin" Message-ID: <20180615164645-mutt-send-email-mst@kernel.org> References: <20180612184616.90838-1-mst@redhat.com> <20180614081800.GH6355@redhat.com> <2219a7fd-b496-6653-b79a-c20136727f98@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <2219a7fd-b496-6653-b79a-c20136727f98@redhat.com> Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v2 0/2] kvm: x86 CPU power management List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: Daniel =?iso-8859-1?Q?P=2E_Berrang=E9?= , Eduardo Habkost , kvm@vger.kernel.org, Marcelo Tosatti , qemu-devel@nongnu.org, Richard Henderson On Thu, Jun 14, 2018 at 05:40:41PM +0200, Paolo Bonzini wrote: > On 14/06/2018 10:18, Daniel P. Berrang=E9 wrote: > > I don't think > > the -realtime flag should ever have been introduced, and we certainly > > shouldn't add more stuff under it. > >=20 > > "-realtime" is referring to a very specific use case, while the > > properties listed under it are all general purpose features. Real > > time guests just happen to be one possible use case, but it is > > valid to use them for non-real time guests. > >=20 > > IOW, I think we should just have this as an option under -cpu or > > some other *functionally* named option, not a option named after > > a specific usage scenario. >=20 > "-cpu" is certainly wrong for KVM_CAP_X86_DISABLE_EXITS. "-cpu" is a > device option, while this is about host behavior. "-realtime"'s name i= s > awful, but I still think it's the best place for this option. Maybe we > could call it "-realtime power-mgmt=3D{host|guest}". I don't feel it's a good name. The new flag allows guest to put CPU into a low power state without host knowing about it. This will affect other guests on the same host CPU. It doesn't however limit power management to guest only, things like speedstep remain under host control. > A separate issue is whether the same flag should control both > KVM_CAP_X86_DISABLE_EXITS and the monitor/mwait CPUID leaf. Eduardo, > what do you think? >=20 > Paolo It's just for -cpu host.