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


Re: [Xen-ia64-devel] [patch] make Xen assign meta-physical memory in spa

To: Jes Sorensen <jes@xxxxxxx>
Subject: Re: [Xen-ia64-devel] [patch] make Xen assign meta-physical memory in spaces that match real hardware
From: Tristan Gingold <tgingold@xxxxxxx>
Date: Fri, 29 Dec 2006 15:00:53 +0100
Cc: Isaku Yamahata <yamahata@xxxxxxxxxxxxx>, xen-ia64-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 29 Dec 2006 05:57:10 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <4594E20B.7060305@xxxxxxx>
List-help: <mailto:xen-ia64-devel-request@lists.xensource.com?subject=help>
List-id: Discussion of the ia64 port of Xen <xen-ia64-devel.lists.xensource.com>
List-post: <mailto:xen-ia64-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-ia64-devel>, <mailto:xen-ia64-devel-request@lists.xensource.com?subject=unsubscribe>
References: <458A9D5D.9000606@xxxxxxx> <20061222022213.GC9022%yamahata@xxxxxxxxxxxxx> <4593F669.4060302@xxxxxxx> <20061228202523.GA2505@saphi> <4594E20B.7060305@xxxxxxx>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, Dec 29, 2006 at 10:38:19AM +0100, Jes Sorensen wrote:
> Tristan Gingold wrote:
> > On Thu, Dec 28, 2006 at 05:52:57PM +0100, Jes Sorensen wrote:
> > [...]
> >> With these patches applied I am seeing PAL warnings about unimplemented
> >> PAL call 42 and then a cachable vs uncacheable access in xenmisc.c.
> >> Anyone else seeing this?
> > Yes, PAL call 42 has never been implemented.  A dummy implementation should 
> > be
> > rather easy, but it's difficult to return an accurate value because of
> > vcpu migration.
> Hi Tristan,
> Nice to see you're still popping up here :)
> One thing I would like to see on the longer term is a feature allowing
> a cpumask to be set for a vcpu so it is only schduled within cpus on a
> specific physical node. That way this call would start making sense.
I think this feature already exist.  The Xen scheduler has a bitmask
(initialized with all 1).  Vcpus can only be scheduled on cpu whose bit is set.

This feature could be used for NUMA, although it may requires additionnal tools.


Xen-ia64-devel mailing list