From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH] i386: wire up MSR_IA32_MISC_ENABLE Date: Tue, 04 Oct 2011 19:08:19 +0200 Message-ID: <4E8B3D83.8050903@redhat.com> References: <1317738395-6488-1-git-send-email-avi@redhat.com> <4E8B2EB8.80408@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: Marcelo Tosatti , kvm@vger.kernel.org, qemu-devel@nongnu.org To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:53393 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754644Ab1JDRIX (ORCPT ); Tue, 4 Oct 2011 13:08:23 -0400 In-Reply-To: <4E8B2EB8.80408@web.de> Sender: kvm-owner@vger.kernel.org List-ID: On 10/04/2011 06:05 PM, Jan Kiszka wrote: > On 2011-10-04 16:26, Avi Kivity wrote: > > It's needed for its default value - bit 0 specifies that "rep movs" is > > good enough for memcpy, and Linux may use a slower memcpu if it is not set, > > depending on cpu family/model. > > > > Signed-off-by: Avi Kivity > > --- > > target-i386/cpu.h | 5 +++++ > > target-i386/helper.c | 1 + > > target-i386/kvm.c | 15 +++++++++++++++ > > target-i386/machine.c | 21 +++++++++++++++++++++ > > target-i386/op_helper.c | 6 ++++++ > > 5 files changed, 48 insertions(+), 0 deletions(-) > > > > diff --git a/target-i386/cpu.h b/target-i386/cpu.h > > index ae36489..5416809 100644 > > --- a/target-i386/cpu.h > > +++ b/target-i386/cpu.h > > @@ -299,6 +299,10 @@ > > > > #define MSR_IA32_PERF_STATUS 0x198 > > > > +#define MSR_IA32_MISC_ENABLE 0x1a0 > > I smell tabs... Oops. Cut'n'paste flew underneath the emacs radar. > > + > > +static const VMStateDescription vmstate_msr_ia32_misc_enable = { > > + .name = "cpu/msr_ia32_misc_enable", > > + .version_id = 1, > > + .minimum_version_id = 1, > > + .minimum_version_id_old = 1, > > + .fields = (VMStateField []) { > > + VMSTATE_UINT64(msr_ia32_misc_enable, CPUState), > > + VMSTATE_END_OF_LIST() > > + } > > +}; > > + > > We are about to bump the CPU_SAVE_VERSION for the sake of APIC deadline > timer, so you can jump on that train and avoid this subsection. Must we do that? Considering that no guest will use the deadline timer, it seems to be an excellent candidates for subsections. > > diff --git a/target-i386/op_helper.c b/target-i386/op_helper.c > > index 3bb5a91..c89e4a4 100644 > > --- a/target-i386/op_helper.c > > +++ b/target-i386/op_helper.c > > @@ -3280,6 +3280,9 @@ void helper_wrmsr(void) > > case MSR_TSC_AUX: > > env->tsc_aux = val; > > break; > > + case MSR_IA32_MISC_ENABLE: > > + env->msr_ia32_misc_enable = val; > > + break; > > This MSR is Intel-specific, isn't it? Then I guess it should be limited > to Intel CPU types. It's an "architectural MSR" that is only available on some Intel models. Either we do a full cpuid qualification of accessible MSRs (and bits within MSRs), or not. Qualifying just by vendor ID is pointless. -- error compiling committee.c: too many arguments to function From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:48090) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB8Zj-0004ly-92 for qemu-devel@nongnu.org; Tue, 04 Oct 2011 13:14:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RB8Zi-0003zX-6d for qemu-devel@nongnu.org; Tue, 04 Oct 2011 13:14:39 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38640) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RB8Tf-000337-9t for qemu-devel@nongnu.org; Tue, 04 Oct 2011 13:08:23 -0400 Message-ID: <4E8B3D83.8050903@redhat.com> Date: Tue, 04 Oct 2011 19:08:19 +0200 From: Avi Kivity MIME-Version: 1.0 References: <1317738395-6488-1-git-send-email-avi@redhat.com> <4E8B2EB8.80408@web.de> In-Reply-To: <4E8B2EB8.80408@web.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH] i386: wire up MSR_IA32_MISC_ENABLE List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Marcelo Tosatti , qemu-devel@nongnu.org, kvm@vger.kernel.org On 10/04/2011 06:05 PM, Jan Kiszka wrote: > On 2011-10-04 16:26, Avi Kivity wrote: > > It's needed for its default value - bit 0 specifies that "rep movs" is > > good enough for memcpy, and Linux may use a slower memcpu if it is not set, > > depending on cpu family/model. > > > > Signed-off-by: Avi Kivity > > --- > > target-i386/cpu.h | 5 +++++ > > target-i386/helper.c | 1 + > > target-i386/kvm.c | 15 +++++++++++++++ > > target-i386/machine.c | 21 +++++++++++++++++++++ > > target-i386/op_helper.c | 6 ++++++ > > 5 files changed, 48 insertions(+), 0 deletions(-) > > > > diff --git a/target-i386/cpu.h b/target-i386/cpu.h > > index ae36489..5416809 100644 > > --- a/target-i386/cpu.h > > +++ b/target-i386/cpu.h > > @@ -299,6 +299,10 @@ > > > > #define MSR_IA32_PERF_STATUS 0x198 > > > > +#define MSR_IA32_MISC_ENABLE 0x1a0 > > I smell tabs... Oops. Cut'n'paste flew underneath the emacs radar. > > + > > +static const VMStateDescription vmstate_msr_ia32_misc_enable = { > > + .name = "cpu/msr_ia32_misc_enable", > > + .version_id = 1, > > + .minimum_version_id = 1, > > + .minimum_version_id_old = 1, > > + .fields = (VMStateField []) { > > + VMSTATE_UINT64(msr_ia32_misc_enable, CPUState), > > + VMSTATE_END_OF_LIST() > > + } > > +}; > > + > > We are about to bump the CPU_SAVE_VERSION for the sake of APIC deadline > timer, so you can jump on that train and avoid this subsection. Must we do that? Considering that no guest will use the deadline timer, it seems to be an excellent candidates for subsections. > > diff --git a/target-i386/op_helper.c b/target-i386/op_helper.c > > index 3bb5a91..c89e4a4 100644 > > --- a/target-i386/op_helper.c > > +++ b/target-i386/op_helper.c > > @@ -3280,6 +3280,9 @@ void helper_wrmsr(void) > > case MSR_TSC_AUX: > > env->tsc_aux = val; > > break; > > + case MSR_IA32_MISC_ENABLE: > > + env->msr_ia32_misc_enable = val; > > + break; > > This MSR is Intel-specific, isn't it? Then I guess it should be limited > to Intel CPU types. It's an "architectural MSR" that is only available on some Intel models. Either we do a full cpuid qualification of accessible MSRs (and bits within MSRs), or not. Qualifying just by vendor ID is pointless. -- error compiling committee.c: too many arguments to function