From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH RFC 0/3] Add guest cpu_entitlement reporting Date: Mon, 27 Aug 2012 13:31:28 -0700 Message-ID: <503BD920.20603@redhat.com> References: <20120823231346.11681.1502.stgit@lambeau> <503BC298.3080306@redhat.com> <1346098984.8623.23.camel@lambeau> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org, peterz@infradead.org, mtosatti@redhat.com, glommer@parallels.com, mingo@redhat.com To: mjw@linux.vnet.ibm.com Return-path: In-Reply-To: <1346098984.8623.23.camel@lambeau> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On 08/27/2012 01:23 PM, Michael Wolf wrote: > > > > How would a guest know what its entitlement is? > > > > > > Currently the Admin/management tool setting up the guests will put it on > the qemu commandline. From this it is passed via an ioctl to the host. > The guest will get the value from the host via a hypercall. > > In the future the host could try and do some of it automatically in some > cases. Seems to me it's a meaningless value for the guest. Suppose it is migrated to a host that is more powerful, and as a result its relative entitlement is reduced. The value needs to be adjusted. This is best taken care of from the host side. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.