This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: para virt cpuid?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: para virt cpuid?
From: Jan Schneider <timberwolf@xxxxxxxxxxxxxxx>
Date: Wed, 8 Jun 2005 06:07:26 +0000 (UTC)
Delivery-date: Wed, 08 Jun 2005 06:12:03 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D2820DE@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Loom/3.14 (http://gmane.org/)
Ian Pratt <m+Ian.Pratt <at> cl.cam.ac.uk> writes:
> For some cpu features it may be possible to take a trap the first time
> they are used, and hence 'taint' the domain with a marker that says it
> can only be migrated to hosts that support the feature. I haven't
> thought through how widely this technique would work, though. We
> probably need to go through and audit all the post Pentium Pro features
> and decide a) whther they're visable to user space b) whether a trap can
> be generated on first use.

That shouldn't be too important, because migrations between different cpu's 
exactly what will be done in production environments.
So a simple global check that source-xen-hostA has the same cpu-featureset as
target-xen-hostB should be enough.
Xen should than issue a warning that the migration-target is equipped with a
different cpu/cpu-feautureset.
A check hat tracks used features would be slightly overkill, also it could be an
additional error-source.
I think KISS would be the right way for this topic.
Of course thats an personal opininion out of a production environment ;).

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>