From: Keir Fraser Subject: Re: Re: [PATCH] xen: mask XSAVE in cpuid since we don'tallow guests to use it Date: Mon, 09 Mar 2009 11:45:00 +0000 Message-ID: References: <49B50C06.76E4.0078.0@novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <49B50C06.76E4.0078.0@novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , Jeremy Fitzhardinge Cc: Boris Derzhavets , Xen-devel , "Marc - A. Dahlhaus [ Administration | Westermann GmbH ]" List-Id: xen-devel@lists.xenproject.org On 09/03/2009 11:31, "Jan Beulich" wrote: >> Thanks, the whole problem stems from blacklisting rather than whitelisting >> feature bits. I might try and do a more comprehensive job for xen-unstable >> at least. This is good for 3.3. > > I'm not sure whitelisting will be much better than blacklisting - while now > any feature requiring not-yet-implemented support in Xen must be turned > off explicitly, this would just turn over to requiring explicitly un-hiding > any > new feature not requiring Xen's intervention. A real solution to this issue > would require some assistance from the hardware vendors I'd think. Well, it makes the difference between working but without the new feature, versus quite possibly simply not working at all (and failing in rare and subtle ways, perhaps). Isn't one obviously better than the other? -- Keir