Le Lundi 24 Juillet 2006 14:22, Akio Takebe a 馗rit :
Hi, all
I'm debugging Xwindow system of dom0.
[...]
At the results, I could startx, but not completely.
I found X run while using 100% CPU with top command.
The following messages were shown at that time.
(XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (= 0x2000)
(XEN) lookup_domain_mpa: d 0xf4288080 id 0 current
0xf426 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=
0x2000)
(XEN) lookup_domain_mpa: d 0xf4288080 id 0 current
0xf426 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=
0x2000)
(XEN) lookup_domain_mpa: d 0xf4288080 id 0 current
0xf426 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=
0x2000)
(XEN) lookup_domain_mpa: d 0xf4288080 id 0 current
0xf426 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=
0x2000)
(XEN) lookup_domain_mpa: d 0xf4288080 id 0 current
0xf426 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=
0x2000)
(XEN) lookup_domain_mpa: d 0xf4288080 id 0 current
0xf426 id 0 (XEN) lookup_domain_mpa: bad mpa 0xfbfd0738 (=
0x2000)
(XEN) lookup_domain_mpa: d 0xf4288080 id 0 current
0xf426 id 0
I think this 0xf4288080 is I/O page to be used by X.
(this 0xf4288080 is also not shown in memmap of Tiger4)
The I/O page seem to be not allocated.
How/When should xen allocate this page?
Hi,
you are misreading the message.
The bad mpa is 0xfbfd0738!
0xf4288080 is the address of struct domain, which is a valid virtual
address.
Hi,
Thanks, I understand this messages.
I overlooked the following comment.
unsigned long lookup_domain_mpa(struct domain *d, unsigned long mpaddr)
{
[snip...]
//XXX This is a work around until the emulation memory access to a region
//where memory or device are attached is implemented.
return pte_val(pfn_pte(0, __pgprot(__DIRTY_BITS | _PAGE_PL_2 |
_PAGE_AR_RWX)));
}
Hmmm... I'll continue to debug this issue.
Best Regards,
Akio Takebe
___
Xen-ia64-devel mailing list
Xen-ia64-devel@lists.xensource.com
http://lists.xensource.com/xen-ia64-devel
