From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753242Ab2E3XdR (ORCPT ); Wed, 30 May 2012 19:33:17 -0400 Received: from terminus.zytor.com ([198.137.202.10]:44545 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751935Ab2E3XdQ (ORCPT ); Wed, 30 May 2012 19:33:16 -0400 Message-ID: <4FC6ADE5.6080003@zytor.com> Date: Wed, 30 May 2012 16:31:49 -0700 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: Andre Przywara CC: mingo@elte.hu, tglx@linutronix.de, konrad.wilk@oracle.com, jeremy@goop.org, linux-kernel@vger.kernel.org, xen-devel@lists.xensource.com, stable@vger.kernel.org.#.3.4+ Subject: Re: [PATCH] x86/amd: fix crash as Xen Dom0 on AMD Trinity systems References: <1338383402-3838-1-git-send-email-andre.przywara@amd.com> In-Reply-To: <1338383402-3838-1-git-send-email-andre.przywara@amd.com> X-Enigmail-Version: 1.4.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 05/30/2012 06:10 AM, Andre Przywara wrote: > Because we are behind a family check before tweaking the topology > bit, we can use the standard rd/wrmsr variants for the CPUID feature > register. > This fixes a crash when using the kernel as a Xen Dom0 on affected > Trinity systems. The wrmsrl_amd_safe is not properly paravirtualized > yet (this will be fixed in another patch). > > Signed-off-by: Andre Przywara > Cc: stable@vger.kernel.org # 3.4+ With Konrad's patch, this is no longer relevant, correct? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.