From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:51386) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwpVq-00071u-0H for qemu-devel@nongnu.org; Thu, 12 Nov 2015 05:53:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZwpVk-0003tU-HK for qemu-devel@nongnu.org; Thu, 12 Nov 2015 05:53:53 -0500 Received: from mx1.redhat.com ([209.132.183.28]:39012) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZwpVk-0003tQ-DT for qemu-devel@nongnu.org; Thu, 12 Nov 2015 05:53:48 -0500 Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) by mx1.redhat.com (Postfix) with ESMTPS id 17135C0E6E27 for ; Thu, 12 Nov 2015 10:53:48 +0000 (UTC) From: Paolo Bonzini Message-ID: <56446FB8.8070701@redhat.com> Date: Thu, 12 Nov 2015 11:53:44 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: [Qemu-devel] -cpu check, rdtscp and AMD KVM List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Eduardo Habkost , qemu-devel 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 kernel= s. What do you think is the best way forward? Paolo