From mboxrd@z Thu Jan 1 00:00:00 1970 From: Raghavendra K T Subject: Re: [PATCH RFC 1/2] kvm vcpu: Note down pause loop exit Date: Tue, 10 Jul 2012 16:52:22 +0530 Message-ID: <4FFC106E.4040407@linux.vnet.ibm.com> References: <20120709062012.24030.37154.sendpatchset@codeblue> <20120709062032.24030.10454.sendpatchset@codeblue> <4FFB5D8E.70402@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FFB5D8E.70402@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Archive: List-Post: To: Rik van Riel Cc: "H. Peter Anvin" , Thomas Gleixner , Avi Kivity , Ingo Molnar , Marcelo Tosatti , S390 , Carsten Otte , Christian Borntraeger , KVM , chegu vinod , "Andrew M. Theurer" , LKML , X86 , Gleb Natapov , linux390@de.ibm.com, Srivatsa Vaddagiri , Joerg Roedel List-ID: On 07/10/2012 04:09 AM, Rik van Riel wrote: > On 07/09/2012 02:20 AM, Raghavendra K T wrote: > >> @@ -484,6 +484,13 @@ struct kvm_vcpu_arch { >> u64 length; >> u64 status; >> } osvw; >> + >> + /* Pause loop exit optimization */ >> + struct { >> + bool pause_loop_exited; >> + bool dy_eligible; >> + } plo; > > I know kvm_vcpu_arch is traditionally not a well documented > structure, but it would be really nice if each variable inside > this sub-structure could get some documentation. Sure. Will document it. > > Also, do we really want to introduce another acronym here? > > Or would we be better off simply calling this struct .ple, > since that is a name people are already familiar with. Yes. it makes sense to have .ple.