Return-Path: Message-ID: <4FC63996.9040706@zytor.com> Date: Wed, 30 May 2012 08:15:34 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 To: Jan Beulich CC: Andre Przywara , mingo@elte.hu, jeremy@goop.org, tglx@linutronix.de, xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk , linux-kernel@vger.kernel.org, stable@vger.kernel.org#3.4+ Subject: Re: [Xen-devel] [PATCH] x86/amd: fix crash as Xen Dom0 on AMD Trinity systems References: <1338383402-3838-1-git-send-email-andre.przywara@amd.com> <20120530143937.GF3207@phenom.dumpdata.com> <4FC633A7.1050406@zytor.com> <4FC6540E0200007800086EF7@nat28.tlf.novell.com> In-Reply-To: <4FC6540E0200007800086EF7@nat28.tlf.novell.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:08 AM, Jan Beulich wrote: > > Xen does trap and emulate (possibly just ignore) both instructions. > Then why the fsck is there paravirt_crap on this? -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf.