From: Amit Tomer <amittomer25@gmail.com>
To: Oleksandr <olekstysh@gmail.com>
Cc: xen-devel@lists.xenproject.org,
Julien Grall <julien.grall@arm.com>,
andrii_chepurnyi@epam.com
Subject: Re: XEN on R-CAR H3
Date: Wed, 13 Mar 2019 18:11:32 +0530 [thread overview]
Message-ID: <CABHD4K-nPagtuTc+D2AeUrN_gcoNYpLxb5N4S3Rpoew3ZCpxVw@mail.gmail.com> (raw)
In-Reply-To: <0f34ecdc-5ae2-2fcb-90bd-65458b97f681@gmail.com>
Hi,
>
> Starting kernel ...
>
> - UART enabled -
> - CPU 00000000 booting -
> - Current EL 00000008 -
> - Xen starting at EL2 -
> - Zero BSS -
> - Setting up control registers -
> - Turning on paging -
> - Ready -
> (XEN) Checking for initrd in /chosen
> (XEN) Initrd 0000000076000040-0000000077a230f7
> (XEN) RAM: 0000000048000000 - 00000000bfffffff
> (XEN) RAM: 0000000500000000 - 000000057fffffff
> (XEN) RAM: 0000000600000000 - 000000067fffffff
> (XEN) RAM: 0000000700000000 - 000000077fffffff
> (XEN)
> (XEN) MODULE[0]: 0000000048000000 - 0000000048014080 Device Tree
> (XEN) MODULE[1]: 0000000076000040 - 0000000077a230f7 Ramdisk
> (XEN) MODULE[2]: 000000007a000000 - 000000007c000000 Kernel
> (XEN) MODULE[3]: 000000007c000000 - 000000007c010000 XSM
> (XEN) RESVD[0]: 0000000048000000 - 0000000048014000
> (XEN) RESVD[1]: 0000000076000040 - 0000000077a230f7
> (XEN)
> (XEN) Command line: dom0_mem=256M console=dtuart dtuart=serial0
> dom0_max_vcpus=4 bootscrub=0 loglvl=all
> (XEN) Placing Xen at 0x000000077fe00000-0x0000000780000000
> (XEN) Update BOOTMOD_XEN from 0000000078080000-00000000781b2d81 =>
> 000000077fe00000-000000077ff32d81
> (XEN) Domain heap initialised
> (XEN) Booting using Device Tree
> (XEN) Platform: Generic System
> (XEN) Looking for dtuart at "serial0", options ""
> (XEN) Unable to initialize dtuart: -9
> (XEN) Bad console= option 'dtuart'
> *Xen 4.9.1-pre*
> (XEN) Xen version 4.9.1-pre (otyshchenko@) (aarch64-poky-linux-gcc (GCC)
> 7.3.0) debug=y Tue Mar 5 20:57:55 EET 2019
> (XEN) Latest ChangeSet: Mon May 8 13:45:21 2017 +0300 git:a438317-dirty
> (XEN) Processor: 411fd073: "ARM Limited", variant: 0x1, part 0xd07, rev 0x3
> (XEN) 64-bit Execution:
> (XEN) Processor Features: 0000000000002222 0000000000000000
> (XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
> (XEN) Extensions: FloatingPoint AdvancedSIMD
> (XEN) Debug Features: 0000000010305106 0000000000000000
> (XEN) Auxiliary Features: 0000000000000000 0000000000000000
> (XEN) Memory Model Features: 0000000000001124 0000000000000000
> (XEN) ISA Features: 0000000000011120 0000000000000000
> (XEN) 32-bit Execution:
> (XEN) Processor Features: 00000131:00011011
> (XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
> (XEN) Extensions: GenericTimer Security
> (XEN) Debug Features: 03010066
> (XEN) Auxiliary Features: 00000000
> (XEN) Memory Model Features: 10201105 40000000 01260000 02102211
> (XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
> (XEN) Using PSCI-1.0 for SMP bringup
> (XEN) SMP: Allowing 8 CPUs
> (XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 8333 KHz
> (XEN) GICv2 initialization:
> (XEN) gic_dist_addr=00000000f1010000
> (XEN) gic_cpu_addr=00000000f1020000
> (XEN) gic_hyp_addr=00000000f1040000
> (XEN) gic_vcpu_addr=00000000f1060000
> (XEN) gic_maintenance_irq=25
> (XEN) GICv2: Adjusting CPU interface base to 0xf102f000
> (XEN) GICv2: 512 lines, 8 cpus, secure (IID 0200043b).
> (XEN) XSM Framework v1.0.0 initialized
> (XEN) xsm: Policy len = 0x0000000000010000 start at 0x000000007c000000
> (XEN) Flask: 128 avtab hash slots, 280 rules.
> (XEN) Flask: 128 avtab hash slots, 280 rules.
> (XEN) Flask: 4 users, 3 roles, 38 types, 2 bools
> (XEN) Flask: 12 classes, 280 rules
> (XEN) Flask: Starting in enforcing mode.
> (XEN) Using scheduler: SMP Credit Scheduler (credit)
> (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 00000002 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 00000003 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 00000100 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 00000101 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 00000102 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 00000103 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 40-bit PA and 8-bit VMID
> (XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
> (XEN) ipmmu: /soc/mmu@e67b0000: registered root IPMMU
> (XEN) ipmmu: /soc/mmu@e67b0000: disable sharing P2M table between the
> CPU and IPMMU
> (XEN) ipmmu: /soc/mmu@febd0000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@febd0000: found master device /soc/video@e6ef0000
> (XEN) ipmmu: /soc/mmu@febd0000: found master device /soc/video@e6ef1000
> (XEN) ipmmu: /soc/mmu@febd0000: found master device /soc/video@e6ef2000
> (XEN) ipmmu: /soc/mmu@febd0000: found master device /soc/video@e6ef3000
> (XEN) ipmmu: /soc/mmu@febd0000: found master device /soc/fcp@fea27000
> (XEN) ipmmu: /soc/mmu@febd0000: found master device /soc/fcp@fea2f000
> (XEN) ipmmu: /soc/mmu@febe0000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@febe0000: found master device /soc/video@e6ef4000
> (XEN) ipmmu: /soc/mmu@febe0000: found master device /soc/video@e6ef5000
> (XEN) ipmmu: /soc/mmu@febe0000: found master device /soc/video@e6ef6000
> (XEN) ipmmu: /soc/mmu@febe0000: found master device /soc/video@e6ef7000
> (XEN) ipmmu: /soc/mmu@febe0000: found master device /soc/fcp@fea37000
> (XEN) ipmmu: /soc/mmu@febe0000: found master device /soc/hdmi@fead0000
> (XEN) ipmmu: /soc/mmu@febe0000: found master device /soc/hdmi@feae0000
> (XEN) ipmmu: /soc/mmu@fe990000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@fe990000: found master device /soc/vspm@fe960000
> (XEN) ipmmu: /soc/mmu@fe990000: found master device /soc/vspm@fe9a0000
> (XEN) ipmmu: /soc/mmu@fe990000: found master device /soc/fdpm@fe940000
> (XEN) ipmmu: /soc/mmu@fe980000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@fe980000: found master device /soc/vspm@fe920000
> (XEN) ipmmu: /soc/mmu@fe980000: found master device /soc/vspm@fe9b0000
> (XEN) ipmmu: /soc/mmu@fe980000: found master device /soc/fdpm@fe944000
> (XEN) ipmmu: /soc/mmu@fe6b0000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@fe6b0000: found master device /soc/imr-lx4@fe880000
> (XEN) ipmmu: /soc/mmu@fe6b0000: found master device /soc/imr-lx4@fe890000
> (XEN) ipmmu: /soc/mmu@fe6b0000: found master device /soc/vcp4@fe90f000
> (XEN) ipmmu: /soc/mmu@fe6f0000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@fe6f0000: found master device /soc/imr-lx4@fe860000
> (XEN) ipmmu: /soc/mmu@fe6f0000: found master device /soc/imr-lx4@fe870000
> (XEN) ipmmu: /soc/mmu@fd800000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@fd800000: found master device /soc/gsx_domd
> (XEN) ipmmu: /soc/mmu@fd800000: found master device /soc/gsx_domu
> (XEN) ipmmu: /soc/mmu@fd950000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@fd960000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@fd970000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@e6570000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee000000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee020000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device
> /soc/dma-controller@e65a0000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device
> /soc/dma-controller@e65b0000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device
> /soc/dma-controller@e6460000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device
> /soc/dma-controller@e6470000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee080100
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee0a0100
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee0c0100
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee0e0100
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee080000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee0a0000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee0c0000
> (XEN) ipmmu: /soc/mmu@e6570000: found master device /soc/usb@ee0e0000
> (XEN) ipmmu: /soc/mmu@ec670000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@ec670000: found master device
> /soc/dma-controller@ec700000
> (XEN) ipmmu: /soc/mmu@ec670000: found master device
> /soc/dma-controller@ec720000
> (XEN) ipmmu: /soc/mmu@e6740000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@e6740000: found master device
> /soc/dma-controller@e6700000
> (XEN) ipmmu: /soc/mmu@e6740000: found master device /soc/ethernet@e6800000
> (XEN) ipmmu: /soc/mmu@e7740000: registered cache IPMMU
> (XEN) ipmmu: /soc/mmu@e7740000: found master device
> /soc/dma-controller@e7300000
> (XEN) ipmmu: /soc/mmu@e7740000: found master device
> /soc/dma-controller@e7310000
> (XEN) ipmmu: /soc/mmu@e7740000: found master device /soc/sd@ee100000
> (XEN) ipmmu: /soc/mmu@e7740000: found master device /soc/sd@ee140000
We booted 4.9(non debug build) based on ipmmu_v2 but don't see ipmuu
related logs in
boot logs(is it because its non debug build):
[ 62.259664] Starting kernel ...
[ 62.262930]
- UART enabled -
- CPU 00000000 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Zero BSS -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Checking for initrd in /chosen
(XEN) RAM: 0000000048000000 - 000000007fffffff
(XEN) RAM: 0000000500000000 - 000000053fffffff
(XEN) RAM: 0000000600000000 - 000000063fffffff
(XEN) RAM: 0000000700000000 - 000000073fffffff
(XEN)
(XEN) MODULE[0]: 000000007d70f000 - 000000007d722000 Device Tree
(XEN) MODULE[1]: 000000007a000000 - 000000007b800000 Kernel
(XEN) RESVD[0]: 000000004a000000 - 000000004a013000
(XEN) RESVD[1]: 000000007d70f000 - 000000007d722000
(XEN)
(XEN) Command line: console=dtuart dom0_mem=512M
(XEN) Placing Xen at 0x000000073fe00000-0x0000000740000000
(XEN) Update BOOTMOD_XEN from 0000000048000000-0000000048108d81 =>
000000073fe00000-000000073ff08d81
(XEN) Domain heap initialised
(XEN) Booting using Device Tree
(XEN) Taking dtuart configuration from /chosen/stdout-path
(XEN) Looking for dtuart at "serial0", options "115200n8"
(XEN) WARNING: UART configuration is not supported
Xen 4.9.1-pre
(XEN) Xen version 4.9.1-pre (atomar@) (aarch64-linux-gnu-gcc (Linaro
GCC 7.3-2018.05) 7.3.1 20180425 [linaro-7.3-2018.05 revision
d29120a424ecfbc167ef90065c0eeb7f91977701]) debug=n Wed Mar 13
13:49:41 I9
(XEN) Latest ChangeSet: Mon May 8 13:45:21 2017 +0300 git:a438317-dirty
(XEN) Processor: 411fd073: "ARM Limited", variant: 0x1, part 0xd07, rev 0x3
(XEN) 64-bit Execution:
(XEN) Processor Features: 0000000000002222 0000000000000000
(XEN) Exception Levels: EL3:64+32 EL2:64+32 EL1:64+32 EL0:64+32
(XEN) Extensions: FloatingPoint AdvancedSIMD
(XEN) Debug Features: 0000000010305106 0000000000000000
(XEN) Auxiliary Features: 0000000000000000 0000000000000000
(XEN) Memory Model Features: 0000000000001124 0000000000000000
(XEN) ISA Features: 0000000000011120 0000000000000000
(XEN) 32-bit Execution:
(XEN) Processor Features: 00000131:00011011
(XEN) Instruction Sets: AArch32 A32 Thumb Thumb-2 Jazelle
(XEN) Extensions: GenericTimer Security
(XEN) Debug Features: 03010066
(XEN) Auxiliary Features: 00000000
(XEN) Memory Model Features: 10201105 40000000 01260000 02102211
(XEN) ISA Features: 02101110 13112111 21232042 01112131 00011142 00011121
(XEN) Generic Timer IRQ: phys=30 hyp=26 virt=27 Freq: 8333 KHz
(XEN) GICv2 initialization:
(XEN) gic_dist_addr=00000000f1010000
(XEN) gic_cpu_addr=00000000f1020000
(XEN) gic_hyp_addr=00000000f1040000
(XEN) gic_vcpu_addr=00000000f1060000
(XEN) gic_maintenance_irq=25
(XEN) GICv2: Adjusting CPU interface base to 0xf102f000
(XEN) GICv2: 512 lines, 8 cpus, secure (IID 0200043b).
(XEN) Using scheduler: SMP Credit Scheduler (credit)
(XEN) Allocated console ring of 16 KiB.
(XEN) Bringing up CPU1
- CPU 00000001 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Bringing up CPU2
- CPU 00000002 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Bringing up CPU3
- CPU 00000003 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Bringing up CPU4
- CPU 00000100 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Bringing up CPU5
- CPU 00000101 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Bringing up CPU6
- CPU 00000102 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Bringing up CPU7
- CPU 00000103 booting -
- Current EL 00000008 -
- Xen starting at EL2 -
- Setting up control registers -
- Turning on paging -
- Ready -
(XEN) Brought up 8 CPUs
(XEN) P2M: 40-bit IPA with 40-bit PA and 8-bit VMID
(XEN) P2M: 3 levels with order-1 root, VTCR 0x80023558
(XEN) I/O virtualisation disabled
(XEN) *** LOADING DOMAIN 0 ***
(XEN) Loading kernel from boot module @ 000000007a000000
(XEN) Allocating 1:1 mappings totalling 512MB for dom0:
(XEN) BANK[0] 0x00000050000000-0x00000070000000 (512MB)
(XEN) Grant table range: 0x0000073fe00000-0x0000073fe61000
(XEN) Loading zImage from 000000007a000000 to 0000000050080000-0000000051880000
(XEN) Allocating PPI 16 for event channel interrupt
(XEN) Loading dom0 DTB to 0x0000000058000000-0x0000000058010aed
(XEN) Scrubbing Free RAM on 1 nodes using 8 CPUs
(XEN) ....done.
(XEN) Initial low memory virq threshold set at 0x4000 pages.
(XEN) Std. Loglevel: Errors and warnings
(XEN) Guest Loglevel: Nothing (Rate-limited: Errors and warnings)
(XEN) *** Serial input -> DOM0 (type 'CTRL-a' three times to switch
input to Xen)
(XEN) Freed 292kB init memory.
Also, this is what we try to get debug build:
#make dist-xen debug=y CONFIG_EARLY_PRINTK=scif,0xe6e88000
XEN_TARGET_ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j16
make -C xen install
make[1]: Entering directory '/scratch/work/xen_work/xen_4.9/xen/xen'
make -f Rules.mk _install
make[2]: Entering directory '/scratch/work/xen_work/xen_4.9/xen/xen'
Rules.mk:11: "You must use 'make menuconfig' to enable/disable debug now."
/scratch/work/xen_work/xen_4.9/xen/xen/arch/arm/Rules.mk:85: ***
CONFIG_EARLY_PRINTK enabled for non-debug build. Stop.
make[2]: Leaving directory '/scratch/work/xen_work/xen_4.9/xen/xen'
Makefile:45: recipe for target 'install' failed
make[1]: *** [install] Error 2
make[1]: Leaving directory '/scratch/work/xen_work/xen_4.9/xen/xen'
Makefile:122: recipe for target 'install-xen' failed
make: *** [install-xen] Error 2
Thanks
-Amit
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-03-13 12:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 14:41 XEN on R-CAR H3 Amit Tomer
2019-02-06 15:03 ` Oleksandr
2019-02-06 15:18 ` Amit Tomer
2019-02-08 18:21 ` Amit Tomer
2019-02-09 16:48 ` Oleksandr
2019-02-15 14:17 ` Amit Tomer
2019-02-15 19:51 ` Oleksandr
2019-02-18 12:53 ` Amit Tomer
2019-02-18 20:00 ` Oleksandr
2019-02-19 16:46 ` Amit Tomer
2019-02-20 18:13 ` Oleksandr
2019-02-20 18:31 ` Amit Tomer
2019-02-20 20:13 ` Julien Grall
2019-02-20 21:28 ` Oleksandr Tyshchenko
2019-02-21 10:11 ` Julien Grall
2019-02-21 19:28 ` Oleksandr
2019-02-25 14:43 ` Oleksandr
2019-02-25 23:23 ` Julien Grall
2019-02-26 18:09 ` Oleksandr
2019-02-21 18:20 ` Amit Tomer
2019-02-21 18:44 ` Oleksandr
2019-02-22 19:15 ` Oleksandr
2019-02-22 20:08 ` Amit Tomer
2019-02-23 13:05 ` Amit Tomer
2019-02-25 13:12 ` Oleksandr
2019-02-27 20:03 ` Oleksandr
2019-03-05 16:50 ` Amit Tomer
2019-03-05 18:07 ` Oleksandr
2019-03-05 18:10 ` Amit Tomer
2019-03-05 19:40 ` Oleksandr
2019-03-13 12:41 ` Amit Tomer [this message]
2019-03-15 18:50 ` Oleksandr
2019-02-21 18:15 ` Amit Tomer
2019-02-27 11:00 ` Julien Grall
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=CABHD4K-nPagtuTc+D2AeUrN_gcoNYpLxb5N4S3Rpoew3ZCpxVw@mail.gmail.com \
--to=amittomer25@gmail.com \
--cc=andrii_chepurnyi@epam.com \
--cc=julien.grall@arm.com \
--cc=olekstysh@gmail.com \
--cc=xen-devel@lists.xenproject.org \
/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.