I made some progress.

I successful applied the device tree overlay and BL31 firmware.
Now, the hypervisor did see the reserved memory and starts loading with a 
mainline 5.9 PREEMPT_RT patched kernel.
(I did add the extra EXPORT_SYMBOLS for this to work.)
Not yet tested with any additional cell. 

Thank you guys for the hints on the device tree fix.

I also tried the jailhouse-image repository, that works fine too.

I would like to ask an additional question:

Why is it necessary to load a custom BL31 firmware instead of the in EEPROM 
one?
Is it for the PSCI CPU on/offlining?


---
Yang

2020年12月7日月曜日 16:17:44 UTC+9 Chung-Fan Yang:

>
>
> 2020年12月7日月曜日 15:14:50 UTC+9 [email protected]:
>
>> On 07.12.20 02:29, Chung-Fan Yang wrote: 
>> > Thanks you for the suggestion of using an approved image. 
>> > I will try it out. 
>> > 
>> > However, I really like to know the root cause and get the current 
>> Debian 
>> > setup working. 
>>
>> [1] officially supports the RPi4 on buster (despite the pain that 
>> brings, hope 5.10 improves the situation at bit). You should derive from 
>> that, specifically the DT overlay-based memory reservation which was 
>> fixed not so long ago. 
>>
>
> Thank you.
> I see the commit now.
> So basically I have to include an additional dtbo the the boot process, am 
> I right?
> Will it work only on the device-tree from rpi-firmware or also the in 
> kernel-tree one?
> I am currently using the in-tree device tree from  kernel 5.9 without any 
> overlay.
>
> By the way, by pain, what do you mean?
>
> ---
> Yang
>  
>
>>
>> For the kernel, I didn't do a rebase of your patch series yet. [2] is 
>> the latest upstream based queue. 
>>
>> Jan 
>>
>> [1] https://github.com/siemens/jailhouse-images 
>> [2] 
>>
>> http://git.kiszka.org/?p=linux.git;a=shortlog;h=refs/heads/queues/jailhouse 
>>
>> > 
>> > Yang 
>> > 
>> > 
>> > 2020年12月7日月曜日 5:01:26 UTC+9 [email protected]: 
>> > 
>> > Check our GSoC project on Automotive Grade Linux: 
>> > 
>> https://git.automotivelinux.org/AGL/meta-agl-devel/tree/meta-agl-jailhouse 
>> > <
>> https://git.automotivelinux.org/AGL/meta-agl-devel/tree/meta-agl-jailhouse> 
>>
>> > 
>> > It can build for PI. 
>> > 
>> > An it can serve as inspiration for the values needed. 
>> > 
>> >   
>> > 
>> > 
>> > js 
>> > 
>> > Chung-Fan Yang <[email protected]> schrieb am So., 6. Dez. 2020, 
>> 17:34: 
>> > 
>> > Hi, 
>> > 
>> > I am working to get jailhouse work with my R-Pi4. 
>> > 
>> > I have been using a 64bit Debian buster rootfs with 
>> > a custom compiled 5.9 preempt-rt kernel. 
>> > 
>> > I have successful reserved >736M for jailhouse and inserted the 
>> > jailhouse.ko, but when I do jailhouse enable I got the following 
>> > error on uart. 
>> > 
>> > Any suggestions are appreciated. 
>> > 
>> > Initializing Jailhouse hypervisor v0.12 (223-g097bed0f) on CPU 1 
>> > Code location: 0x0000ffffc0200800 
>> > Page pool usage after early setup: mem 39/994, remap 0/131072 
>> > Initializing processors: 
>> >  CPU 1... 
>> > FATAL: Unhandled HYP exception: synchronous abort from EL2 
>> >  pc: 0000ffffc0203864   lr: 0000ffffc0203850 spsr: 200003c9     EL2 
>> >  sp: 0000ffffc0222e40  elr: 0000ffffc0203864  esr: 00 1 0000000 
>> >  x0: 0000000084000000   x1: 0000000000000000   x2: 0000000080003580 
>> >  x3: 0000000000000014   x4: 0000000000000002   x5: 0000000000000001 
>> >  x6: 0000000000000029   x7: 0000ffffc0219ec0   x8: 000000000000002a 
>> >  x9: 0000000000000000  x10: 0000000000000000  x11: 0000000000000001 
>> > x12: 0000000000000015  x13: 0000000000000001  x14: 0000ffffc0219000 
>> > x15: 0000ffffc0015040  x16: 0000ffffc020da50  x17: ffffaf45951e7518 
>> > x18: 0000000000000001  x19: 0000ffffc0222000  x20: 0000ffffc0219000 
>> > x21: 0000ffffc0200000  x22: 0000ffffc0219000  x23: 0000000000000001 
>> > x24: 0000000000000001  x25: 0000ffffc0222000  x26: 0000ffffc0223000 
>> > x27: 0000ffffc020f000  x28: 0000ffffc0218000  x29: 0000ffffc0222e40 
>> > 
>> > Hypervisor stack before exception Stopping CPU 1 (Cell: 
>> > "Raspberry-Pi4") 
>> > 
>> > PS. I did noticed there is a similar post, but it has no solution. 
>> > 
>> > -- 
>> > You received this message because you are subscribed to the 
>> > Google Groups "Jailhouse" group. 
>> > To unsubscribe from this group and stop receiving emails from 
>> > it, send an email to [email protected]. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/jailhouse-dev/f0e8ee0a-e874-428e-a97c-91524477c7e1n%40googlegroups.com
>>  
>> > <
>> https://groups.google.com/d/msgid/jailhouse-dev/f0e8ee0a-e874-428e-a97c-91524477c7e1n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>  
>>
>> > 
>> > -- 
>> > You received this message because you are subscribed to the Google 
>> > Groups "Jailhouse" group. 
>> > To unsubscribe from this group and stop receiving emails from it, send 
>> > an email to [email protected] 
>> > <mailto:[email protected]>. 
>> > To view this discussion on the web visit 
>> > 
>> https://groups.google.com/d/msgid/jailhouse-dev/126f7b0c-2fa6-4329-bb95-bddead90c9f7n%40googlegroups.com
>>  
>> > <
>> https://groups.google.com/d/msgid/jailhouse-dev/126f7b0c-2fa6-4329-bb95-bddead90c9f7n%40googlegroups.com?utm_medium=email&utm_source=footer>.
>>  
>>
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/0031a2f2-07ed-453e-924a-8b9756af8ff9n%40googlegroups.com.

Reply via email to