WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-ia64-devel

Re: [Xen-ia64-devel] Xen is now runnnig at Bull

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, "Xu, Anthony" <anthony.xu@xxxxxxxxx>, <xen-ia64-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-ia64-devel] Xen is now runnnig at Bull
From: Tristan Gingold <Tristan.Gingold@xxxxxxxx>
Date: Thu, 8 Sep 2005 11:25:09 +0200
Delivery-date: Thu, 08 Sep 2005 08:20:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <571ACEFD467F7749BC50E0A98C17CDD807D51850@pdsmsx403>
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: <571ACEFD467F7749BC50E0A98C17CDD807D51850@pdsmsx403>
Sender: xen-ia64-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.5
Le Jeudi 08 Septembre 2005 03:21, Tian, Kevin a écrit :
> From: Tristan Gingold [mailto:Tristan.Gingold@xxxxxxxx]
>
> >What is the hg command to know the changeset ?  I used 'hg revert xxx'
> and
> >'hg log' still displays the 'hg pull' changeset.
> Hg history: show all the changesets
> Hg heads: show current head of the hg tree
Neither seems ok for me.
I tried:

$ hg clone xen-ia64-unstable-Intel.hg try-intel
$ cd try-intel/
$ hg log | head -40
changeset:   6466:bbca8e1b94e319cfc1868ca10b5a8a50128fb9d9
tag:         tip
user:        fred@xxxxxxxxxxxxxxxxxxxxx
date:        Sun Sep  4 22:04:56 2005
summary:     Put Elilo patch and readme into xen/arch/ia64/tools/elilo


changeset:   6465:915bcdfafe7f57f68cf98aabaf876464ac0f1807
user:        fred@xxxxxxxxxxxxxxxxxxxxx
date:        Sun Sep  4 21:52:53 2005
summary:     merge elilo module support from Rev6461 baesd diff to Rev6464

$ hg revert -r 6464
$ hg heads | head
changeset:   6466:bbca8e1b94e319cfc1868ca10b5a8a50128fb9d9
tag:         tip
user:        fred@xxxxxxxxxxxxxxxxxxxxx
date:        Sun Sep  4 22:04:56 2005
summary:     Put Elilo patch and readme into xen/arch/ia64/tools/elilo

$ hg history | head
changeset:   6466:bbca8e1b94e319cfc1868ca10b5a8a50128fb9d9
tag:         tip
user:        fred@xxxxxxxxxxxxxxxxxxxxx
date:        Sun Sep  4 22:04:56 2005
summary:     Put Elilo patch and readme into xen/arch/ia64/tools/elilo


changeset:   6465:915bcdfafe7f57f68cf98aabaf876464ac0f1807
user:        fred@xxxxxxxxxxxxxxxxxxxxx
date:        Sun Sep  4 21:52:53 2005

How can I know I reverted to 6464 ?


[...]
> I think normally elilo will place parameters, initrd, etc. in higher end
> of physical memory, and it's unlikely to map all memories by one TR.
Correct.
> Actually the alt dtlb miss fault is wanted for Xen to access all the
> physical memories.
Correct.
> BTW, can you check whether 0x617ef90010 is legal
> address in a memory bank on your box?
Yes it is (I checked with the ITP).

Thanks.
Tristan.


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