All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: xen-devel@lists.xensource.com, pranavkumar@linaro.org
Cc: ian.campbell@citrix.com,
	Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: [ARM APM Mustang-X. Xen 4.5-rc1 and staging] Booting issues, last meesage: (XEN) P2M: 3 levels with order-1 root, VTCR 0x80033558
Date: Mon, 3 Nov 2014 13:06:13 -0500	[thread overview]
Message-ID: <20141103180613.GA5379@laptop.dumpdata.com> (raw)

Hey,

I've been following: http://wiki.xen.org/wiki/Xen_ARM_with_Virtualization_Extensions/APMXGeneMustang#Preparing_all_the_Images
with a couple of changes:

1) The latest Linux tree in https://github.com/AppliedMicro/ENGLinuxLatest
looks to have already Xen support in the default config. So used that instead
of 3.15.


2). The 'run xen_run' does not execute properly, but if I run each
 operation by itself it does get me to boot Xen.


However I am not sure if the reason I am getting stuck is because I should be
using 3.15-rc8 instead of the latest? Or perhaps there is another issue?

And here is the serial console


Mustang# run xen_dtb xen_dom0 xen_load;
Using eth0 device
TFTP from server 192.168.105.1; our IP address is 192.168.105.51
Filename 'lab/tst051/apm-mustang-xen.dtb's: 0x4003000000
Loading: *\b##
	 2.1 MiB/s
done
Bytes transferred = 15716 (3d64 hex)
Using eth0 device
TFTP from server 192.168.105.1; our IP address i\b#################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ####################
	 4.2 MiB/s
done
Bytes transferred = 7925472 (78eee0 hex)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt ND
Mustang# run xen_dtb
Using eth0 device
TFTP from server 192.168.105.1; our IP address is 192.168.105.51
Filename 'lab/tst051/apm-mustang-xen.dtb'.
Load address: 0x4003000000
Loading: *\b##
	 2.1 MiB/s
done
Bytes transferred = 15716 (3d64 hex)
Mustang# run xen_dom0
Using eth0 device
TFTP from server 192.168.105.1; our IP address is 192.168.105.51
Filename 'lab/tst051/Image'.
Load address: 0x400200000
Loading: *\b#################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 #################################################################
	 ####################
	 4.1 MiB/s
done
Bytes transferred = 7925472 (78eee0 hex)
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
libfdt fdt_path_offset() returned FDT_ERR_NOTFOUND
Mustang# run xen_load
Using eth0 device
TFTP from server 192.168.105.1; our IP address is 192.168.105.51
Filename 'lab/tst051/uXen'.
Load address: 0x4000080000
Loading: *\b####################################################
	 4.1 MiB/s
done
Bytes transferred = 755600 (b8790 hex)
Mustang# fdt print /chosen
chosen {
};
Mustang# run xen_boot
## Booting kernel from Legacy Image at 4000080000 ...
   Image Name:   Xen
   Image Type:   ARM Linux Kernel Image (uncompree:    755536 Bytes = 737.8 KiB
   Load Address: 00200000
   Entry Point:  00200000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 4003000000
   Booting using the fdt blob at 0x0000004003000000
   Loading Kernel Image ..OK
OK
   reserving fdt memory region: addr=4003000000 size=4000
   Loading Device Tree to 0000004000ff9000, end 0000004000fff
Starting kernel ...

L3C: 8MB
- UART enabled -
- CPU 00000000 booting -
- Current EL 00000008 -
- Xen starting at EL2 -RAM: 0000004000000000 - 00000043ffffffff
(XEN) 
(XEN) MODULE[0]: 0000004000ff9000 - 0000004001000000 Device Tree  
(XEN)  RESVD[0]: 0000004003000000 - 0000004003004000
(XEN)  RESVD[1]: 0000004000000000 - 0000004000010000
(XEN) 
(XEN) Command line: <NULL>
(XEN) Placing Xen at 0x00000043ffe00000-0x0000004400000000
(XEN) Update BOOTMOD_XEN from 0000004000200000-000000400030ad81 => 00000043ffe00000-00000043fff0ad81
(XEN) Domain heap initialised
(XEN) No console
(XEN) Bad console= option 'dtuart'
 Xen 4.5.0-rc
(XEN) Xen version 4.5.0-rc ((XEN) 64-bit Execution:
(XEN)   Processor Features: 0000000000000122 0000000000000000
(XEN)     Exception Levels: EL3:No EL2:64 EL1:64+32 EL0:64+32
(XEN)     Extensions: FloatingPoint AdvancedSIMD
(XEN)   Debug Features: 0000000010303106 0000000000000000
(XEN)   Auxiliary Features: 0000000000000000 0000000000000000
(XEN)   Memory Model Features: 0000000000000123 0000000000000000
(XEN)   ISA Features:  0000000000000000 0000000000000000
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00000131:00111001
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN)     Extensions: GenericTimer
(XEN)   Debug Features: 03010006
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 00100105 40000000 01260000 02102111
(XEN)  ISA Features: 02101110 13112111 21232042 01112131 00010142 00000001
(XEN) Platform: APM X-GENE STORM
(XEN) Generic Timer IRQ: phys=29 hyp=31 virt=30
(XEN) Using generic timer at 50000 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=0000000078090000
(XEN)         gic_cpu_addr=00000000780a0000
(XEN)         gic_hyp_addr=00000000780c0000
(XEN)         gic_vcpu_addr=00000000780e0000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 256 lines, 8 cpus, secure (IID 0200143b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) I/O virtualisation disabled
(XEN) Allocated console ring of 64 KiB.
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 1 booted.
(XEN) Bringing up CPU2
- CPU 00000100 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 2 booted.
(XEN) Bringing up CPU3
- CPU 00000101 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 3 booted.
(XEN) Bringing up CPU4
- CPU 00000200 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 4 booted.
(XEN) Bringing up CPU5
- CPU 00000201 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 5 booted.
(XEN) Bringing up CPU6
- CPU 00000300 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 6 booted.
(XEN) Bringing up CPU7
- CPU 00000301 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) CPU 7 booted.
(XEN) Brought up 8 CPUs
(XEN) P2M: 40-bit IPA with 42-bit PA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80033558

             reply	other threads:[~2014-11-03 18:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-03 18:06 Konrad Rzeszutek Wilk [this message]
2014-11-04  9:53 ` [ARM APM Mustang-X. Xen 4.5-rc1 and staging] Booting issues, last meesage: (XEN) P2M: 3 levels with order-1 root, VTCR 0x80033558 Ian Campbell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141103180613.GA5379@laptop.dumpdata.com \
    --to=konrad.wilk@oracle.com \
    --cc=ian.campbell@citrix.com \
    --cc=pranavkumar@linaro.org \
    --cc=stefano.stabellini@eu.citrix.com \
    --cc=xen-devel@lists.xensource.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.