From: "H. Peter Anvin" Subject: Re: [Xen-devel] [PATCH] x86/amd: fix crash as Xen Dom0 on AMD Trinity systems Date: Wed, 30 May 2012 08:45:57 -0700 Message-ID: <4FC640B5.2080601@zytor.com> References: <1338383402-3838-1-git-send-email-andre.przywara@amd.com> <4FC63DAF0200007800086DC5@nat28.tlf.novell.com> <4FC62888.9010407@amd.com> <4FC649790200007800086E51@nat28.tlf.novell.com> <4FC631F0.9080109@zytor.com> <20120530144929.GH3207@phenom.dumpdata.com> <20120530151235.GB15635@x1.osrc.amd.com> <4FC65B950200007800086F5B@nat28.tlf.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4FC65B950200007800086F5B@nat28.tlf.novell.com> Sender: linux-kernel-owner@vger.kernel.org To: Jan Beulich Cc: Borislav Petkov , Andre Przywara , Jacob Shin , mingo@elte.hu, jeremy@goop.org, tglx@linutronix.de, xen-devel@lists.xensource.com, Konrad Rzeszutek Wilk , linux-kernel@vger.kernel.org List-Id: xen-devel@lists.xenproject.org On 05/30/2012 08:40 AM, Jan Beulich wrote: >>>> On 30.05.12 at 17:12, Borislav Petkov wrote: >> This current case should be a perfect example for why xen shouldn't be >> sprinkling code all over the place. > > Which means you're denying the benefits of para-virtualization > (at the base system level; perhaps it's less of a problem for you > when it comes to pv device drivers, which are generally > standalone entities) as that's what distinguishes Xen from all > other virtualization solutions Linux supports. > And it also denies the just atrocious cost of Xen grabbing random kernel internals and turning them into ABIs that we have to work around from that point on. This is particularly obnoxious because the cost is largely not borne by the Xen community but by the general Linux development. -hpa