[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] address space reorganization


  • To: Jacob Gorm Hansen <jacobg@xxxxxxx>
  • From: Kip Macy <kip.macy@xxxxxxxxx>
  • Date: Wed, 13 Apr 2005 20:14:19 -0700
  • Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
  • Delivery-date: Thu, 14 Apr 2005 03:15:45 +0000
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ivlERJ+Ke/zwvJrlromO1aU+N9G6w48EwCtRaZjdI9kypveEv4WRpLNQZHwbDoTtmwriUgPR+nYlAQiZ6uHOcF2VYepOyyKHbBFhRbzJDycdcYUJCYlQp1WhpqnwgQjWpQzjM9QwPbxPCINoi+JcR/vxR6G5EUZujsDFJWmqMoQ=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

> > That works OK for the kernel, but you might have user space apps that
> > have adapted their behviour based on what the've found in /proc/cpuinfo.
> 
> A compromise then would be to lie to userspace and still recalibrate the
> kernel.

If you're saying what I think you are - I don't think people who have
customized their apps for SSE2 would like that.

You'll either have to have xend propagate a bitmask of the cpuid
capabilities so that xfrd won't migrate it or you tell users that "the
behaviour is undefined" if they use migration in a heterogeneous
cluster.

      -Kip

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.