[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <4FC65B950200007800086F5B@nat28.tlf.novell.com>
Date: Wed, 30 May 2012 16:40:37 +0100
From: "Jan Beulich" <JBeulich@...e.com>
To: "Borislav Petkov" <bp@...en8.de>
Cc: "Andre Przywara" <andre.przywara@....com>,
"Jacob Shin" <Jacob.Shin@....com>, <mingo@...e.hu>,
<jeremy@...p.org>, <tglx@...utronix.de>,
<xen-devel@...ts.xensource.com>,
"Konrad Rzeszutek Wilk" <konrad.wilk@...cle.com>,
<linux-kernel@...r.kernel.org>, "H. Peter Anvin" <hpa@...or.com>
Subject: Re: [Xen-devel] [PATCH] x86/amd: fix crash as Xen Dom0 on AMD
Trinity systems
>>> On 30.05.12 at 17:12, Borislav Petkov <bp@...en8.de> 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.
Jan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists