Re: [Xen-devel] Problems running Xen 4.4 on OMAP5432 evm

["Kapania, Ashish" <akapania@xxxxxx>]

Hi Ian, Julien,

Thanks for your response.

I set "debug=y" to make earlyprintk work.

I added a few earlyprintk stmts in setup_pagetable() to narrow
down the problem. The last print msg I get is just before
flush_xen_text_tlb(). I donât get the prints after that call.

After the above exercise, I decided to check if the A15's
mode somehow got changed from Hypervisor Mode to some other mode.
I read the CPSR using inline assembly and passed it to the printk
call just before flush_xen_text_tlb(). I found that the print
message is no longer printed when I added the CPSR argument.
So, if I try to add an argument to printk before tlb flush,
the message is not printed but if I remove the argument it
gets printed. It does not look like the prints are being
buffered so I am a bit confused by this behavior.

0xfee000000 address should be in RAM. The RAM address range
is 0x80000000 to 0xFFFFFFFF.

I will try building using the development branch to see if that
helps.

Best,
Ashish

-----Original Message-----
From: Ian Campbell [mailto:Ian.Campbell@xxxxxxxxxx] 
Sent: Wednesday, April 16, 2014 3:43 AM
To: Kapania, Ashish
Cc: xen-devel@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] Problems running Xen 4.4 on OMAP5432 evm

On Wed, 2014-04-16 at 00:23 +0000, Kapania, Ashish wrote:
> Hi,
> 
> I am trying to run Xen (+ Linux dom0) on OMAP5432 evm and have been 
> having trouble just booting xen itself. The xen wiki does not have 
> build instructions for OMAP5432 but the source code seems to have 
> support for it so I am assuming that board is supported. I am using 
> xen RELEASE-4.4.0 git tag to build a xen image. Here's my build command-line:
> 
> make dist-xen XEN_TARGET_ARCH=arm32 CROSS_COMPILE=arm-linux-gnueabihf- 
> CONFIG_EARLY_PRINTK=omap5432

Worth trying with "debug=y" on this too (will need a complete clean to take 
full affect)

> When I boot xen, I see the A15 hangs in setup_pagetables() function in 
> arch/arm/mm.c file.

Can you say exactly where?

> MODULE[1]: 0000000083ff6000 - 0000000083ffd000
>  RESVD[0]: 00000000825f0000 - 00000000825f7000
>  RESVD[1]: 0000000083ff6000 - 0000000083ffd000
> 
> Command line: dom0_mem=256M console=dtuart dtuart=serial2 
> earlyprintk=xen Placing Xen at 0x00000000fee00000-0x00000000ff000000

At this point Xen will be relocating itself. I'm not sure what has gone wrong 
though. I presume 0xfee000000 is actually in RAM?

> Any ideas on what I might be doing wrong ? Maybe I am missing some 
> patch that is required to run xen on omap5432 ?

I can't think of any relevant patches which aren't in 4.4.0, but it would 
certainly be good to try the development branch to be sure (if that works then 
we can figure out which patch needs backporting).

Otherwise I'm afraid the issue will need some more debugging.

Ian.

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel