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

Isaku Yamahata wrote:
> On Fri, Jun 08, 2007 at 10:08:38AM +0200, Jes Sorensen wrote:
>> 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.

Hello Isaku,

Just to let you know that this turned out to be a red herring and not
the real cause of the problem I was seeing. Instead it was because I
let dom0 write to the global MMR registers which is what we use on
Altix to purge tlbs .... not good :-(

Thanks for the tip.

Cheers,
Jes

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

<Prev in Thread]

Current Thread

[Next in Thread>

Previous by Date:

Re: [PATCH] add paddr_t definition to compile gnttab.c (was Re: [Xen-ia64-devel] [RFC] gnttab unmap_and_replace), Jes Sorensen

Next by Date:

[Xen-ia64-devel] [patch] base NR_DYNIRQS on CONFIG_NR_CPUS, Jes Sorensen

Previous by Thread:

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

Next by Thread:

[Xen-ia64-devel] [RFC] Extended I/O port space support, Alex Williamson

Indexes:

[Date] [Thread] [Top] [All Lists]