From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755588Ab0IFSsC (ORCPT ); Mon, 6 Sep 2010 14:48:02 -0400 Received: from mx1.redhat.com ([209.132.183.28]:38170 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753745Ab0IFSr6 (ORCPT ); Mon, 6 Sep 2010 14:47:58 -0400 Message-ID: <4C853747.9020401@redhat.com> Date: Mon, 06 Sep 2010 21:47:35 +0300 From: Avi Kivity User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.8) Gecko/20100806 Fedora/3.1.2-1.fc13 Thunderbird/3.1.2 MIME-Version: 1.0 To: Andre Przywara CC: hpa@zytor.com, tglx@linutronix.de, mingo@elte.hu, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Subject: Re: [PATCH 3/4] x86: Fix allowed CPUID bits for KVM guests References: <1283778860-26843-1-git-send-email-andre.przywara@amd.com> <1283778860-26843-4-git-send-email-andre.przywara@amd.com> In-Reply-To: <1283778860-26843-4-git-send-email-andre.przywara@amd.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 09/06/2010 04:14 PM, Andre Przywara wrote: > The AMD extensions to AVX (FMA4, XOP) work on the same YMM register set > as AVX, so they are safe for guests to use, as long as AVX itself > is allowed. Add F16C and AES on the way for the same reasons. Acked-by: Avi Kivity -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.