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.
MfG
 Goswin
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel