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-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 08:59:38 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 02 Jun 2005 07:55:51 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.GSO.4.58.0506011337300.28494@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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 1 Jun 2005, at 18:50, Carl Holtje ;021;vcsg6; wrote:

Ok.. so this may be a horribly basic question, but what does 'working
properly' look like -- I mean, how do I know if what I have is right or

Try calling show_page_walk(header), where header is the virtual address returned by set_fixmap. You should see valid non-zero entries at both levels of the pagetable.

How do I go about verifying the functionality of set_fixmap and the
subsequent set_pte_phys calls?

It would appear that it locates the header high in the memory space (as it should according to fixmap.h documentation), but there's nothing there for the subsequent call where it tries to map the table (at least this is how
I understand it -- am I close?)

Yes, that's the problem. The mapping hasn't happened, or has happened at the wrong place in the pagetables, or something like that.

 -- Keir

Xen-devel mailing list