From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 0/6 v2] Add support for RDTSCP in VMX Date: Wed, 23 Dec 2009 15:44:48 +0200 Message-ID: <4B321ED0.9070708@redhat.com> References: <1261126127-9603-1-git-send-email-sheng@linux.intel.com> <4B2DEE98.4070702@redhat.com> <20091222172617.GA9541@amt.cnet> <4B310F51.9090909@redhat.com> <20091223133740.GA13991@amt.cnet> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Glauber de Oliveira Costa , Sheng Yang , kvm@vger.kernel.org To: Marcelo Tosatti Return-path: Received: from mx1.redhat.com ([209.132.183.28]:34980 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753104AbZLWNov (ORCPT ); Wed, 23 Dec 2009 08:44:51 -0500 In-Reply-To: <20091223133740.GA13991@amt.cnet> Sender: kvm-owner@vger.kernel.org List-ID: On 12/23/2009 03:37 PM, Marcelo Tosatti wrote: > >> Should be automatic. After all, we expose all the MSR list, so qemu can >> read it and save everything there. >> > Hum, thinking a bit more about this (and reading Glauber's previous attempt) its not > entirely clear that using the list provided by KVM_GET_MSR_INDEX_LIST to automatically save/restore > is a good thing: > > - The MSR must be saved in QEMU's CPUState representation, and its > likely that it won't exist prior to the addition there. > > - What about savevm/loadvm versioning? Currently the QEMU migration > protocol is unable to deal with a new kernel that supports, for example, > MSR_TSC_AUX vs a kernel that does not (in case MSRs were automatically > saved), with the same qemu-kvm version. > You're right. Well, qemu knows about cpuid.rdtscp, so we can add it to vmstate if it is enabled. We should probably whitelist flags in qemu in the same way we whitelist them in kvm. -- error compiling committee.c: too many arguments to function