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-devel

Re: [Xen-devel] Xen & Transmeta (from xen-users)

To: "Carl Holtje ;021;vcsg6;" <cwh0803@xxxxxxxxxx>
Subject: Re: [Xen-devel] Xen & Transmeta (from xen-users)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Thu, 2 Jun 2005 22:13:10 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 02 Jun 2005 21:15:58 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.GSO.4.58.0506021705140.1617@xxxxxxxxxxxxxxxx>
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: <Pine.GSO.4.58.0505241113400.16688@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0505240925480.9339@xxxxxxxxxxxxxxx> <Pine.GSO.4.58.0505241128360.16688@xxxxxxxxxxxxxxxx> <Pine.LNX.4.58.0505240931540.9339@xxxxxxxxxxxxxxx> <4293878E.9090903@xxxxxxx> <Pine.GSO.4.58.0505251429370.20392@xxxxxxxxxxxxxxxx> <ecd2cfedbbd92a7bf208569b1e5fbeb1@xxxxxxxxxxxx> <Pine.GSO.4.58.0505261651450.20484@xxxxxxxxxxxxxxxx> <cd23d293fb9a3a92f4811bc17bfcca22@xxxxxxxxxxxx> <Pine.GSO.4.58.0505311542020.26084@xxxxxxxxxxxxxxxx> <6897e54f155e86bc8e55e2f33e69f51d@xxxxxxxxxxxx> <Pine.GSO.4.58.0506010917490.28466@xxxxxxxxxxxxxxxx> <6959b40101aa41470b346b8b0bf6a9c0@xxxxxxxxxxxx> <Pine.GSO.4.58.0506011002110.28494@xxxxxxxxxxxxxxxx> <e91e65ec0e06ea3b248ad080827bbd3e@xxxxxxxxxxxx> <Pine.GSO.4.58.0506011337300.28494@xxxxxxxxxxxxxxxx> <f1e475a2e1547827b98784be417baf1a@xxxxxxxxxxxx> <Pine.GSO.4.58.0506021705140.1617@xxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 2 Jun 2005, at 22:09, Carl Holtje ;021;vcsg6; wrote:

Ok.. so I've 'upgraded' to using the xen-unstable tree... and walked into
a bunch more trouble..

I'm totally lost looking at the assembler for
xen/arch/x86/string.c#memset, but that seems to be where my latest
"unknown interrupt" message is coming from (originating from
xen/arch/x86/mm.c#init_frametable)... how do I go about fixing
this?

I moved the init_trap() call in setup.c before this, but don't get
anything.. must be too early?

Thanks again... your help is definitely appreciated!

Let's take a step back: does the CPU have all the capabilities that Xen expects? If you run 'cat /proc/cpuinfo' on native Linux, do you see all the following flags: fpu, pse, tsc, cx8, pge? Those are the ones I'm pretty sure you'll run into trouble if you lack. If you have all those then we should press on and find the bugs. :-)

 -- Keir


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