Hello,

No further questions in this message, just a quick wrap-up:
1) Console is now configured.
2) Dom0 kernel is coming up and showing messages.

Very many thanks for all your help!


= Details =

This message should conclude the issue.
Therefore, it summarizes my findings and mistakes, and gets
the actual device tree, and a log entering Dom0 attached.


1) Console is now configured:

It helps to take the exact same console, as the one U-Boot uses,
and to enable it. In case of the LAGER board, it is  "/serial@e6e60000",
configured via the following DT snippet:
----- 8< -----
scif0: serial@e6e60000 {
        status = "ok";
 };
 chosen {
        stdout-path = &scif0;
        xen,xen-bootargs = "console=dtuart dom0_mem=1G";
};
----- 8< -----


2) Dom0 kernel is coming up and showing messages:

> From: Julien Grall [mailto:julien.gr...@citrix.com]
> Sent: Wednesday, October 21, 2015 8:02 PM
> 
> To be sure, even the patch I attached on the previous mail doesn't help
> you to get the console?

The patch works. But now it is obsolete, and reverted.

My mistake was how I tried to configure the kernel:
Following the OMAP wiki [1], which I think is a little misleading,
I appended the CONFIG_XEN* and friends to .config, and called 'make',
leading to the CONFIG_XEN*-flags to be overwritten by defaults.
Once configured via menuconfig, Dom0 showed messages all right.

> If so, the simplest way to investigate requires the serial driver in Xen
> to be functional (IIRC it's not the case right now). If you got it, you
> can type CTRL-a tree times and access to the Xen console.

This great tool works now.
 
> If you have Xen built with debug=y, from the log you sent it seems to be
> the case, you can use the asm instruction "hvc" to get Xen printing
> useful information:
>     - hvc 0xffff will dump the state of the vCPU
>     - hvc 0xfffd will print the program counter

Nice to know.  Couldn't find it on the wiki, though.

I'll update the LAGER board wiki [2] with my findings.

Some questions remain, but I'll come back on these later,
when I'm more clear about them, and probably via [xen-users].
I'll try my best to abide by the etiquette next time.

Max Ferger

[1] 
http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/OMAP5432_uEVM#2.2_Build_Linux_Dom0_kernel
[2] http://wiki.xenproject.org/wiki/Xen_ARM_with_Virtualization_Extensions/Lager




Leopold KOSTAL GmbH & Co. KG - Sitz Lüdenscheid, Registergericht Iserlohn HRA 
2854, phG Kostal Verwaltungsgesellschaft mbH, Registergericht Iserlohn HRB 4061 
- USt-Id-Nr./Vat No.: DE 125800885
Post- und Werksanschrift: An der Bellmerei 10, D-58513 Lüdenscheid * Telefon: 
+49 2351 16-0 * Telefax: +49 2351 16-2400 Bellmerei
Geschäftsführung: Dipl.-Oec. Andreas Kostal (Vorsitzender), Dipl.-Kfm. Helmut 
Kostal, Dipl.-Ing. Marwin Kinzl, Dr.-Ing. Ludger Laufenberg, Dipl.-Kfm. Ulrich 
Zimmermann

LAGER SPI_LOADER V0.28 2014.09.29
DEVICE S25FL512


U-Boot 2014.10-00441-gf7ca1f7-dirty (Oct 19 2015 - 12:32:17)

CPU: Renesas Electronics R8A7790 rev 2.0
Board: Lager
I2C:   ready
DRAM:  2 GiB
SF: Detected S25FL512S_256K with page size 512 Bytes, erase size 256 KiB, total 
64 MiB
In:    serial
Out:   serial
Err:   serial
Net:   sh_eth
Hit any key to stop autoboot:  0
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'r8a7790-lager-xen.dtb'.
Load address: 0x70f00000
Loading: #########
         395.5 KiB/s
done
Bytes transferred = 44621 (ae4d hex)
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'dom0-zImage'.
Load address: 0x72000000
Loading: #################################################################
         #################################################################
         #################################################################
         #################################################################
         ############################################
         603.5 KiB/s
done
Bytes transferred = 1553064 (17b2a8 hex)
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'xenpolicy'.
Load address: 0x74000000
Loading: ##
         41 KiB/s
done
Bytes transferred = 9561 (2559 hex)
chosen {
        bootargs = "ignore_loglevel rw root=/dev/nfs ip=dhcp";
        stdout-path = "/serial@e6e60000";
        xen,xen-bootargs = "console=dtuart dom0_mem=1G";
        xen,dom0-bootargs = "console=hvc0 earlyprintk=xen debug ignore_loglevel 
vmalloc=384M video=HDMI-A-1:1920x1080-32@60 
ip=192.168.0.5:192.168.0.15:192.168.0.15:255.255.255.0:lager:eth0::: 
root=/dev/nfs rw nfsroot=192.168.0.15:/nfsroot rootdelay clk_ignore_unused";
        modules {
                #address-cells = <0x00000001>;
                #size-cells = <0x00000001>;
                module@0x72000000 {
                        reg = <0x72000000 0x0017b2a8>;
                        compatible = "multiboot,kernel", "multiboot,module";
                };
                module@0x74000000 {
                        reg = <0x74000000 0x00002559>;
                        compatible = "xen,xsm-policy", "multiboot,module";
                };
        };
};
sh_eth:1 is connected to sh_eth.  Reconnecting to sh_eth
sh_eth Waiting for PHY auto negotiation to complete... done
sh_eth: 100Base/Half
Using sh_eth device
TFTP from server 192.168.0.15; our IP address is 192.168.0.5
Filename 'xen-uImage'.
Load address: 0x70007fc0
Loading: #################################################################
         #################################################################
         #####################################
         615.2 KiB/s
done
Bytes transferred = 852948 (d03d4 hex)
## Booting kernel from Legacy Image at 70007fc0 ...
   Image Name:   XEN4.6-LAGER
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    852884 Bytes = 832.9 KiB
   Load Address: 90000000
   Entry Point:  90000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 70f00000
   Booting using the fdt blob at 0x70f00000
   Loading Kernel Image ... OK
   reserving fdt memory region: addr=70f00000 size=b000
   Loading Device Tree to 407f2000, end 407fffff ... OK

Starting kernel ...

- UART enabled -
- CPU 00000000 booting -
- Xen starting in Hyp mode -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000040000000 - 000000007fffffff
(XEN) RAM: 0000000140000000 - 00000001ffffffff
(XEN)
(XEN) MODULE[0]: 00000000407f2000 - 00000000407fd000 Device Tree
(XEN) MODULE[1]: 0000000072000000 - 000000007217b2a8 Kernel
(XEN) MODULE[2]: 0000000074000000 - 0000000074002559 XSM
(XEN)  RESVD[0]: 0000000070f00000 - 0000000070f0b000
(XEN)  RESVD[1]: 000000007ff9a000 - 000000007ff9a120
(XEN)  RESVD[2]: 00000000407f2000 - 00000000407fd000
(XEN)
(XEN) Command line: console=dtuart dom0_mem=1G
(XEN) Placing Xen at 0x000000007fc00000-0x000000007fe00000
(XEN) Update BOOTMOD_XEN from 0000000090000000-000000009011b701 => 
000000007fc00000-000000007fd1b701
(XEN) Xen heap: 00000001f8000000-0000000200000000 (32768 pages)
(XEN) Dom heap: 1015808 pages
(XEN) Domain heap initialised
(XEN) Platform: Renesas R-Car Gen2
(XEN) Taking dtuart configuration from /chosen/stdout-path
(XEN) Looking for dtuart at "/serial@e6e60000", options ""
 __  __            _  _    __    ___
 \ \/ /___ _ __   | || |  / /_  / _ \
  \  // _ \ '_ \  | || |_| '_ \| | | |
  /  \  __/ | | | |__   _| (_) | |_| |
 /_/\_\___|_| |_|    |_|(_)___(_)___/

(XEN) Xen version 4.6.0 (aen@) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 
4.8.2-16ubuntu4) 4.8.2) debug=y Thu Oct 22 13:31:12 CEST 2015
(XEN) Latest ChangeSet: Mon Oct 5 15:33:39 2015 +0100 git:b24ad7b
(XEN) Processor: 413fc0f2: "ARM Limited", variant: 0x3, part 0xc0f, rev 0x2
(XEN) 32-bit Execution:
(XEN)   Processor Features: 00001131:00011011
(XEN)     Instruction Sets: AArch32 A32 Thumb Thumb-2 ThumbEE Jazelle
(XEN)     Extensions: GenericTimer Security
(XEN)   Debug Features: 02010555
(XEN)   Auxiliary Features: 00000000
(XEN)   Memory Model Features: 10201105 40000000 01240000 02102211
(XEN)  ISA Features: 02101110 13112111 21232041 11112131 10011142 00000000
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 10000 KHz
(XEN) GICv2 initialization:
(XEN)         gic_dist_addr=00000000f1001000
(XEN)         gic_cpu_addr=00000000f1002000
(XEN)         gic_hyp_addr=00000000f1004000
(XEN)         gic_vcpu_addr=00000000f1006000
(XEN)         gic_maintenance_irq=25
(XEN) GICv2: 416 lines, 8 cpus, secure (IID 0200043b).
(XEN) XSM Framework v1.0.0 initialized
(XEN) xsm: Policy len = 0x0000000000002559 start at 0x0000000074000000
(XEN) Flask: 64 avtab hash slots, 236 rules.
(XEN) Flask: 64 avtab hash slots, 236 rules.
(XEN) Flask:  3 users, 3 roles, 36 types, 2 bools
(XEN) Flask:  12 classes, 236 rules
(XEN) Flask:  Starting in permissive mode.
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 64 KiB.
(XEN) VFP implementer 0x41 architecture 4 part 0x30 variant 0xf rev 0x0
(XEN) Bringing up CPU1
(XEN) CPU1 never came online
(XEN) Failed to bring up CPU 1 (error -5)
(XEN) Bringing up CPU2
(XEN) CPU2 never came online
(XEN) Failed to bring up CPU 2 (error -5)
(XEN) Bringing up CPU3
(XEN) CPU3 never came online
(XEN) Failed to bring up CPU 3 (error -5)
(XEN) Bringing up CPU4
(XEN) CPU4 never came online
(XEN) Failed to bring up CPU 4 (error -5)
(XEN) Bringing up CPU5
(XEN) CPU5 never came online
(XEN) Failed to bring up CPU 5 (error -5)
(XEN) Bringing up CPU6
(XEN) CPU6 never came online
(XEN) Failed to bring up CPU 6 (error -5)
(XEN) Bringing up CPU7
(XEN) CPU7 never came online
(XEN) Failed to bring up CPU 7 (error -5)
(XEN) Brought up 1 CPUs
(XEN) P2M: 40-bit IPA
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80003558
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 0000000072000000
(XEN) Allocating 1:1 mappings totalling 1024MB for dom0:
(XEN) BANK[0] 0x00000048000000-0x00000070000000 (640MB)
(XEN) BANK[1] 0x000001d8000000-0x000001f0000000 (384MB)
(XEN) Grant table range: 0x0000007fc00000-0x0000007fc72000
(XEN) Loading zImage from 0000000072000000 to 000000004fe00000-000000004ff7b2a8
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x0000000050000000-0x000000005000a947
(XEN) Scrubbing Free RAM on 1 nodes using 1 CPUs
(XEN) ................................done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: All
(XEN) Guest Loglevel: All
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch input to 
Xen)
(XEN) Freed 268kB init memory.
Booting Linux on physical CPU 0x0
Linux version 4.3.0-rc6kostal-xen4.6-00108-gce1fad2-dirty 
(aen@aen-virtual-machine) (gcc version 4.8.2 (Ubuntu/Linaro 4.8.2-16ubuntu4) ) 
#7 Thu Oct 22 16:23:21 CEST 2015
CPU: ARMv7 Processor [413fc0f2] revision 2 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, PIPT instruction cache
Machine model: Lager
Ignoring memory block 0x1d8000000 - 0x1f0000000
debug: ignoring loglevel setting.
Truncating RAM at 0x48000000-0x70000000 to -0x6f000000
Consider using a HIGHMEM enabled kernel.
Memory policy: Data cache writeback
On node 0 totalpages: 159744
free_area_init_node: node 0, pgdat c02e7c08, node_mem_map e6b1b000
  Normal zone: 1248 pages used for memmap
  Normal zone: 0 pages reserved
  Normal zone: 159744 pages, LIFO batch:31
psci: probing for conduit method from DT.
psci: PSCIv0.2 detected in firmware.
psci: Using standard PSCI v0.2 function IDs
psci: Trusted OS migration not required
Xen 4.6 support found
CPU: All CPU(s) started in SVC mode.
pcpu-alloc: s0 r0 d32768 u32768 alloc=1*32768
pcpu-alloc: [0] 0
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 158496
Kernel command line: console=hvc0 earlyprintk=xen debug ignore_loglevel 
vmalloc=384M video=HDMI-A-1:1920x1080-32@60 
ip=192.168.0.5:192.168.0.15:192.168.0.15:255.255.255.0:lager:eth0::: 
root=/dev/nfs rw nfsroot=192.168.0.15:/nfsroot rootdelay clk_ignore_unused
PID hash table entries: 4096 (order: 2, 16384 bytes)
Dentry cache hash table entries: 131072 (order: 7, 524288 bytes)
Inode-cache hash table entries: 65536 (order: 6, 262144 bytes)
Memory: 629812K/638976K available (2309K kernel code, 72K rwdata, 444K rodata, 
116K init, 192K bss, 9164K reserved, 0K cma-reserved)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xe7800000 - 0xff000000   ( 376 MB)
    lowmem  : 0xc0000000 - 0xe7000000   ( 624 MB)
      .text : 0xc0008000 - 0xc02b8694   (2754 kB)
      .init : 0xc02b9000 - 0xc02d6000   ( 116 kB)
      .data : 0xc02d6000 - 0xc02e83e0   (  73 kB)
       .bss : 0xc02e83e0 - 0xc0318764   ( 193 kB)
SLUB: HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:16 nr_irqs:16 16
clocksource_of_init: no matching clocksources found
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 
21474836475000000ns
Console: colour dummy device 80x30
console [hvc0] enabled
Calibrating delay loop...

Attachment: r8a7790-lager-xen.dts
Description: r8a7790-lager-xen.dts

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

Reply via email to