Re: [Xen-ia64-devel] [Patch][RFC] allocate all memory to dom0

On Thu, Oct 05, 2006 at 04:00:20PM +0900, Akio Takebe wrote:
> Hi,
> 
> Also in the case of current Xen-ia64-unstable(cset:11721),
> this panic is occured by specified dom0_mem=4G.
> (without my patch)
> 
> I think the following error message is hint of this bug.
> (XEN) Warning: UC to WB for mpaddr=f9ff0000
> 
> I checked the arch/ia64/xen/mm.c
> Why changing pteval2 from UC to WB is OK?
> If pteval2 is WB and pteval is UC, should pteval2 be changed to UC?
> 

Because it's RAM. not I/O.
>From your log
> (XEN) dom mem: type= 7, attr=0x0000000000000008, range=
> [0x0000000080000000-0x00000000fe000000) (2016MB)
Probably ioremap hypercall failed.
Please check it by adding debug message assign_domain_same_page().
I suppose it should complain somehow.


The warning message is the result of Linux tries to use the addresses
for I/O which is RAM.
Then the next question is why/how Linux decided to use the addresses
to map I/O.
iomem_resource manages those regions so that such a overlap
shouldn't happen.
Your long doesn't tell anything about those.
Could you check Linux /proc/iomem?

-- 
yamahata

_______________________________________________
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: [Xen-ia64-devel] [PATCH] xencomm_privcmd_sched_op, Tristan Gingold

Next by Date:

Re: [Xen-ia64-devel] [PATCH] xencomm_privcmd_sched_op, Doi . Tsunehisa

Previous by Thread:

Re: [Xen-ia64-devel] [Patch][RFC] allocate all memory to dom0, Tristan Gingold

Next by Thread:

Re: [Xen-ia64-devel] [Patch][RFC] allocate all memory to dom0, Isaku Yamahata

Indexes:

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