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] Confused about start of day setup

To: Goswin von Brederlow <brederlo@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Confused about start of day setup
From: Goswin von Brederlow <brederlo@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Date: Tue, 25 Sep 2007 02:52:17 +0200
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Mon, 24 Sep 2007 17:53:02 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <87ejgn7hdm.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx> (Goswin von Brederlow's message of "Tue, 25 Sep 2007 01:50:29 +0200")
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: <C31DAA05.DF59%Keir.Fraser@xxxxxxxxxxxx> <87fy13yk6v.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx> <87ejgn7hdm.fsf@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Gnus/5.110006 (No Gnus v0.6) XEmacs/21.4.19 (linux)
Goswin von Brederlow <brederlo@xxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:

> Goswin von Brederlow <brederlo@xxxxxxxxxxxxxxxxxxxxxxxxxxx> writes:
> It seems that my stack ends up in the middle of the
> phys_to_machine_mapping for some reason. I don't know if that is
> already broken in Mini-OS or if I broke something though.
> MfG
>         Goswin

And once more I answere myself. I thought it was the stack being wrong
because the return value of a function was stored in the
phys_to_machine_mapping. But actualy it the variable this value gets
saved in that is there.

What decides where the phys_to_machine_mapping frames ends up?

As it is I get it at [0x121000 - 0x127000], which happens to be
overlapping with my bss section:

objdump -t moose.elf | grep bss | sort

000000000011d520 g     O .bss   0000000000004000 irqstack
0000000000121520 g     O .bss   0000000000000018 __cacheline_aligned
0000000000121540 g     O .bss   0000000000000020 xen_features
0000000000121560 g     O .bss   0000000000000008 HYPERVISOR_shared_info
0000000000121568 g     O .bss   0000000000000008 phys_to_machine_mapping

And those addresses correspond directly to the pages that are later
corrupt in the mapping.


Xen-devel mailing list