Re: [Xen-devel] XEN on R-CAR H3

On 13.03.19 14:41, Amit Tomer wrote: Hi, Hi Starting kernel ... - UART enabled - - CPU booting - - Current EL 0008 - - Xen starting at EL2 - - Zero BSS - - Setting up control registers - - Turning on paging - - Ready - (XEN) Checking for initrd in /chosen (XEN) Initrd 00

Re: [Xen-devel] XEN on R-CAR H3

Hi, > > Starting kernel ... > > - UART enabled - > - CPU booting - > - Current EL 0008 - > - Xen starting at EL2 - > - Zero BSS - > - Setting up control registers - > - Turning on paging - > - Ready - > (XEN) Checking for initrd in /chosen > (XEN) Initrd 7640-77a23

Re: [Xen-devel] XEN on R-CAR H3

On 05.03.19 20:10, Amit Tomer wrote: Hi, Have you tried to enable early_prink? Yes, this is how we compiled it. make dist-xen XEN_TARGET_ARCH=arm64 debug=y CROSS_COMPILE=aarch64-linux-gnu- CONFIG_EARLY_PRINTK_salvator=scif,0xe6e88000 -j16 No, "CONFIG_EARLY_PRINTK_salvator=scif,0xe6e88000" i

Re: [Xen-devel] XEN on R-CAR H3

Hi, > Have you tried to enable early_prink? Yes, this is how we compiled it. make dist-xen XEN_TARGET_ARCH=arm64 debug=y CROSS_COMPILE=aarch64-linux-gnu- CONFIG_EARLY_PRINTK_salvator=scif,0xe6e88000 -j16 > AFAIR, I tested that branch (ipmmu_v2) before submitting RFC patch > series [1] and it was

Re: [Xen-devel] XEN on R-CAR H3

On 05.03.19 18:50, Amit Tomer wrote: Hi, Hi, Amit The proper command is: mkimage -A arm64 -C none -T kernel -a 0x7808 -e 0x7808 -n "XEN" -d xen/xen xen-uImage Yeah but it didn't boot it up :( Have you tried to enable early_prink? AFAIR, I tested that branch (ipmmu_v2) before

Re: [Xen-devel] XEN on R-CAR H3

Hi, > The proper command is: > > mkimage -A arm64 -C none -T kernel -a 0x7808 -e 0x7808 -n "XEN" > -d xen/xen xen-uImage Yeah but it didn't boot it up :( [ 16.991035] => setenv ipaddr 10.105.2.28;setenv serverip 10.105.2.27;ping 10.105.2.27 [ 18.791456] ravb Waiting for PHY auto nego

Re: [Xen-devel] XEN on R-CAR H3

Hi, Amit BTW, we use mkimage tool to create Xen image to be loaded: mkimage -A arm64 -C none -T kernel -a 0x7808 -e 0x7808 -n "XEN" xen/xen xen-uImage I am sorry, I had missed "-d" key before xen image. The proper command is: mkimage -A arm64 -C none -T kernel -a 0x7808 -e

Re: [Xen-devel] XEN on R-CAR H3

Hi Amit, On 2/21/19 6:15 PM, Amit Tomer wrote: Hi, diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c index d9836779d1..08b9cd2c44 100644 --- a/xen/arch/arm/domain_build.c +++ b/xen/arch/arm/domain_build.c @@ -1805,6 +1805,8 @@ static void __init dtb_load(struct kernel_info

Re: [Xen-devel] XEN on R-CAR H3

Hi Oleksandr, Hi, Julien There is a question which worries me and likely other people as well. Which is "reserved memory area support in Xen". Some SoCs except application processors have some IPs (co-processors, dsps, codecs, whatever) which rely on a specific predefined memory regions,

Re: [Xen-devel] XEN on R-CAR H3

Hi Oleksandr, On 2/25/19 2:43 PM, Oleksandr wrote: Hi Julien While I know that Xen does not deal with reserved area yet, we should have been able to write in that region. We don't even reach that state as we can't get the associated page. It might be possible that the p2m entry is overwri

Re: [Xen-devel] XEN on R-CAR H3

Hi Julien While I know that Xen does not deal with reserved area yet, we should have been able to write in that region. We don't even reach that state as we can't get the associated page. It might be possible that the p2m entry is overwritten when going through the DT for mapping all the

Re: [Xen-devel] XEN on R-CAR H3

On 23.02.19 15:05, Amit Tomer wrote: Hello, Hi Did removing reserved-memory regions together with users work out well for you? Removing "reserved-memory" node along with "mmngr" worked well. Tested it with v3.15 BSP release. ok Also, just tried loading XEN from one of your branch[1

Re: [Xen-devel] XEN on R-CAR H3

Hello, > > Did removing reserved-memory regions together with users work out well > > for you? Removing "reserved-memory" node along with "mmngr" worked well. Tested it with v3.15 BSP release. Also, just tried loading XEN from one of your branch[1] but it stuck with this: [ 13.793305] host 10

Re: [Xen-devel] XEN on R-CAR H3

Hello, > Did removing reserved-memory regions together with users work out well > for you? Sorry, didn't get chance to work on this today. I would test it and let you know. Thanks -Amit ___ Xen-devel mailing list Xen-devel@lists.xenproject.org https:/

Re: [Xen-devel] XEN on R-CAR H3

Hi Amit Likely, it is because you left device nodes (mmngr,adsp,etc) which had links to reserved-memory regions ... Did removing reserved-memory regions together with users work out well for you? -- Regards, Oleksandr Tyshchenko ___ Xen-dev

Re: [Xen-devel] XEN on R-CAR H3

On 21.02.19 12:11, Julien Grall wrote: Hi Oleksandr, Hi, Julien, Amit On 20/02/2019 21:28, Oleksandr Tyshchenko wrote: ср, 20 февр. 2019 г., 22:14 Julien Grall mailto:julien.gr...@arm.com>>: If I am not mistaken, the diff between BSP's and mainline device trees is in reserved memory area.

Re: [Xen-devel] XEN on R-CAR H3

On 21.02.19 20:20, Amit Tomer wrote: Hi, Hi (1) https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/tree/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts?h=v4.14.75-ltsi/rcar-3.9.3.rc1 (2) https://elixir.bootlin.com/linux/v5.0-rc7/source/arch/arm64/boot/dts/renesas/r8a7

Re: [Xen-devel] XEN on R-CAR H3

Hi, > (1) > https://git.kernel.org/pub/scm/linux/kernel/git/horms/renesas-bsp.git/tree/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts?h=v4.14.75-ltsi/rcar-3.9.3.rc1 > > (2) > https://elixir.bootlin.com/linux/v5.0-rc7/source/arch/arm64/boot/dts/renesas/r8a7795-h3ulcb.dts Yeah, this is what I tho

Re: [Xen-devel] XEN on R-CAR H3

Hi, > diff --git a/xen/arch/arm/domain_build.c b/xen/arch/arm/domain_build.c > index d9836779d1..08b9cd2c44 100644 > --- a/xen/arch/arm/domain_build.c > +++ b/xen/arch/arm/domain_build.c > @@ -1805,6 +1805,8 @@ static void __init dtb_load(struct kernel_info *kinfo) > printk("Loading dom0 DTB

Re: [Xen-devel] XEN on R-CAR H3

Hi Oleksandr, On 20/02/2019 21:28, Oleksandr Tyshchenko wrote: > ср, 20 февр. 2019 г., 22:14 Julien Grall >: > If I am not mistaken, the diff between BSP's and mainline device trees is in > reserved memory area. BSP device tree (1) contains reserved memory regions,

Re: [Xen-devel] XEN on R-CAR H3

ср, 20 февр. 2019 г., 22:14 Julien Grall : > Hi Amit, Hi, Julien, Amit. Sorry for formatting, writing from my mobile. If I am not mistaken, the diff between BSP's and mainline device trees is in reserved memory area. BSP device tree (1) contains reserved memory regions, but the mainline one (2

Re: [Xen-devel] XEN on R-CAR H3

Hi Amit, Thank you for the report. On 2/19/19 4:46 PM, Amit Tomer wrote: > (XEN) CPU7 MIDR (0x410fd034) does not match boot CPU MIDR (0x411fd073), > (XEN) disable cpu (see big.LITTLE.txt under docs/). > (XEN) CPU7 never came online > (XEN) Failed to bring up CPU 7 (error -5) > (XEN) Brought up 4

Re: [Xen-devel] XEN on R-CAR H3

Hi, > We use earlier BSP version and we didn't face the similar issue. > > We have a plan to switch to recent BSP version (3.15). So, I will come > up with updates when we migrate. Thanks for this information, we have now built it for 3.9 but yet to test the images. Also, it would be great if you

Re: [Xen-devel] XEN on R-CAR H3

On 19.02.19 18:46, Amit Tomer wrote: Hi Hi [1] https://elinux.org/R-Car/Boards/Yocto-Gen3 We tried BSP release v3.15.0 from above link but see following message: [ 45.518865] => setenv xen_addr_r 0x4800;setenv fdt_addr_r 0x4a00;setenv kernel_addr_r 0x7a00 [ 52.430467]

Re: [Xen-devel] XEN on R-CAR H3

Hi > [1] https://elinux.org/R-Car/Boards/Yocto-Gen3 We tried BSP release v3.15.0 from above link but see following message: [ 45.518865] => setenv xen_addr_r 0x4800;setenv fdt_addr_r 0x4a00;setenv kernel_addr_r 0x7a00 [ 52.430467] => setenv fdt_high 0x;fdt addr $fdt_add

Re: [Xen-devel] XEN on R-CAR H3

On 18.02.19 14:53, Amit Tomer wrote: Hi Hi, I am wondering what Android version you are using. What is your use-case? We are trying with Android O 8.1 version. This is our development product https://github.com/xen-troops/meta-xt-prod-devel which in addition to Linux guest contains Android

Re: [Xen-devel] XEN on R-CAR H3

Hi, > I am wondering what Android version you are using. What is your use-case? We are trying with Android O 8.1 version. > This is our development product > https://github.com/xen-troops/meta-xt-prod-devel > which in addition to Linux guest contains Android P guest. > After making some changes i

Re: [Xen-devel] XEN on R-CAR H3

On 15.02.19 16:17, Amit Tomer wrote: Hi, Hi disk = [ 'phy:/dev/mmcblk1p1,xvda1' ] Thanks , this worked for us and we can now boot Linux guest in domU. Sounds great But now, while booting Android as domU guest , we don't get console login for domU and it stuck here: [ 10.597394]

Re: [Xen-devel] XEN on R-CAR H3

Hi, > disk = [ 'phy:/dev/mmcblk1p1,xvda1' ] Thanks , this worked for us and we can now boot Linux guest in domU. But now, while booting Android as domU guest , we don't get console login for domU and it stuck here: [ 10.597394] usbcore: registered new interface driver cdc_acm [ 10.597436] c

Re: [Xen-devel] XEN on R-CAR H3

On 08.02.19 20:21, Amit Tomer wrote: Hi, Hi Would try changes mentioned by you. We managed to boot XEN with dom0 kernel on H3. That's great. But we see following , when we try to domU guest: # xl create -c config.xl Parsing config from config.xl libxl: error: libxl_exec.c:118:libxl_rep

Re: [Xen-devel] XEN on R-CAR H3

Hi, > Would try changes mentioned by you. We managed to boot XEN with dom0 kernel on H3. But we see following , when we try to domU guest: # xl create -c config.xl Parsing config from config.xl libxl: error: libxl_exec.c:118:libxl_report_child_exitstatus: /etc/xen/scripts/block add [2417] exite

Re: [Xen-devel] XEN on R-CAR H3

Hi,Thanks for prompt reply. > Memory nodes got duplicated somehow. Likely U-Boot did something incorrect. > > Try to use single memory node in your device-tree instead of separated > by each bank nodes: > > memory@4800 { > device_type = "memory"; > /* first 128MB is reserved

Re: [Xen-devel] XEN on R-CAR H3

On 06.02.19 16:41, Amit Tomer wrote: HI, Hi Trying to boot XEN on R-CAR H3 starter Kit board. Linux image based on 5.0.0-rc5 and XEN image is 4.12 tftp 0x4800 xen;tftp 0x7a00 Image; tftp 4a00 r8a7795-h3ulcb.dtb setenv xen_addr_r 0x4800 setenv fdt_addr_r 4a00 setenv ker

[Xen-devel] XEN on R-CAR H3

HI, Trying to boot XEN on R-CAR H3 starter Kit board. Linux image based on 5.0.0-rc5 and XEN image is 4.12 tftp 0x4800 xen;tftp 0x7a00 Image; tftp 4a00 r8a7795-h3ulcb.dtb setenv xen_addr_r 0x4800 setenv fdt_addr_r 4a00 setenv kernel_addr_r 0x7a00 fdt addr $fdt_addr_r fdt