From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH] Added call parameter to track whether invocation originated with guest or elsewhere Date: Wed, 17 Oct 2012 11:09:18 -0300 Message-ID: <20121017140918.GA4940@amt.cnet> References: <1350439833.8785.27.camel@WillAuldHomeLinux> <507E89F5.4000301@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: will.auld@intel.com, Will Auld , kvm@vger.kernel.org, xiantao.zhang@intel.com, jinsong.liu@intel.com To: Avi Kivity Return-path: Received: from mx1.redhat.com ([209.132.183.28]:43613 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756240Ab2JQOJ2 (ORCPT ); Wed, 17 Oct 2012 10:09:28 -0400 Content-Disposition: inline In-Reply-To: <507E89F5.4000301@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Oct 17, 2012 at 12:35:33PM +0200, Avi Kivity wrote: > On 10/17/2012 04:10 AM, Will Auld wrote: > > Signed-off-by: Will Auld > > --- > > > > Resending to full list > > > > Marcelo, > > > > This patch is what I believe you ask for as foundational for later > > patches to address IA32_TSC_ADJUST. > > > > Please write a changelog to reflect the motivation. > > All those bool parameters scattered all over the place aren't very > pretty. Usually we solve this with helpers that embed the parameter > name (kvm_set_msr() vs. kvm_set_msr_host()) but there are too many > functions for this to work here. > > Marcelo, any ideas? Its easier to read kvm_x86_ops->kvm_set_msr() kvm_x86_ops->kvm_set_msr_host() then kvm_x86_ops->kvm_set_msr(,false) kvm_x86_ops->kvm_set_msr(,true) So you're right.