From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54991) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zwuj3-0002ss-TE for qemu-devel@nongnu.org; Thu, 12 Nov 2015 11:27:58 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Zwuj0-0005fp-Mj for qemu-devel@nongnu.org; Thu, 12 Nov 2015 11:27:53 -0500 Received: from mx1.redhat.com ([209.132.183.28]:42562) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Zwuj0-0005fk-Hc for qemu-devel@nongnu.org; Thu, 12 Nov 2015 11:27:50 -0500 Received: from int-mx14.intmail.prod.int.phx2.redhat.com (int-mx14.intmail.prod.int.phx2.redhat.com [10.5.11.27]) by mx1.redhat.com (Postfix) with ESMTPS id 4E6AA80085 for ; Thu, 12 Nov 2015 16:27:50 +0000 (UTC) Date: Thu, 12 Nov 2015 14:27:48 -0200 From: Eduardo Habkost Message-ID: <20151112162748.GN4180@thinpad.lan.raisama.net> References: <56446FB8.8070701@redhat.com> <20151112152510.GM4180@thinpad.lan.raisama.net> <5644B72D.8080807@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <5644B72D.8080807@redhat.com> Subject: Re: [Qemu-devel] -cpu check, rdtscp and AMD KVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Paolo Bonzini Cc: qemu-devel On Thu, Nov 12, 2015 at 04:58:37PM +0100, Paolo Bonzini wrote: > On 12/11/2015 16:25, Eduardo Habkost wrote: > > On Thu, Nov 12, 2015 at 11:53:44AM +0100, Paolo Bonzini wrote: > >> Eduardo, > >> > >> running QEMU 2.5 on SVM causes a warning because rdtscp is not supported > >> by KVM. While I can fix it, that leaves a warning on all existing kernels. > > > > You mean when using Opteron_G2 or newer, right? qemu64 and kvm64 > > don't have rdtscp enabled. > > > >> What do you think is the best way forward? > > > > To simply remove rdtscp from all Opteron_G* models? > > Not sure this is the right thing to do... Real hardware has it, and > going forward KVM will provide it. Do you see any alternative? We need AMD CPU models that can run out of the box using today's kernels. As no existing VMs running Opteron_G* on AMD CPUs have rdtscp, I believe it makes sense to just define Opteron_G* without rdtscp. When we add SVM rdtscp support to KVM, we can add new "Opteron_G[2-5]-rdtscp" CPU models. -- Eduardo