Return-Path: Message-ID: <4FC6363F.3040208@zytor.com> Date: Wed, 30 May 2012 08:01:19 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 To: Borislav Petkov , Andre Przywara , 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> <4FC631D3.9080907@zytor.com> <20120530145523.GA15635@x1.osrc.amd.com> <4FC6358F.2010405@zytor.com> <20120530150007.GB15438@x1.osrc.amd.com> In-Reply-To: <20120530150007.GB15438@x1.osrc.amd.com> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: On 05/30/2012 08:00 AM, Borislav Petkov wrote: > On Wed, May 30, 2012 at 07:58:23AM -0700, H. Peter Anvin wrote: >> If so, then fix the description to match reality and we can take the patch. > > Andre, would you please do that? > Ah, but now we get: >> I'm not following: If the AMD variants (putting a special value into >> %edi) can be freely replaced by the non-AMD variants, why did >> the AMD special ones get used in the first place? > Older CPUs (K8) needed the AMD variants, starting with family 10h we > can use the normal versions. So no, not correct. -hpa