Re: [Xen-ia64-devel] Picking the P2M address range

[Isaku Yamahata <yamahata@xxxxxxxxxxxxx>]

On Fri, Jun 08, 2007 at 10:08:38AM +0200, Jes Sorensen wrote:
> Isaku Yamahata wrote:
> > On Thu, Jun 07, 2007 at 06:01:17PM +0200, Jes Sorensen wrote:
> >> Hi,
> >>
> >> When dom0 boots it prints out a couple of lines like these:
> >>
> >> Xen p2m: assign p2m table of [0x0000003000000000, 0x0000003024000000)
> >> Xen p2m: to [0x000001b040000000, 0x000001b043ffc000) (65536 KBytes)
> >>
> >> I am trying to figure out where the addresses in the first line
> >> originate from. They are obviously picked by Xen and provided to dom0
> >> somehow, but how and where?
> > 
> > I'm not sure I understand your question fully.
> > It comes from memory descriptor which xen creates.
> > I.e. it is calculated based on ia64_boot_param->efi_memmap.
> > 
> > dom_fw_init() creates it in xen.
> > Presumably you have heavily modified those code and
> > real memory map which boot loader(elilo?) creates is passed thourgh to dom0.
> 
> I see, so the addresses are calculated by dom0, not by Xen? Yes they
> match my memory map, but because I have a hole in that space in the
> physical map I see evtchn_set_pending() (in Xen) trying to scribble into
> non existing memory which causes me an MCA :-(

Hmm, I'm not sure why evtchn_set_pending() is involved.
You can disable p2m exposure by setting
xen_ia64_p2m_expose to 0 in
linux-2.6-xen-sparse/arch/ia64/xen/hypervisor.c.
Then you may be able to go further. Later you can get back to this issue.

-- 
yamahata

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