Hi,

On 04/10/2018 02:10 PM, iallende wrote:
> El martes, 10 de abril de 2018, 10:47:57 (UTC+2), Ralf Ramsauer  escribió:
>> Hi,
>>
>> On 04/10/2018 10:26 AM, iallende wrote:
>>> El jueves, 22 de marzo de 2018, 16:33:02 (UTC+1), Ralf Ramsauer  escribió:
>>>> On 03/22/2018 04:23 PM, iallende wrote:
>>>>> El miércoles, 21 de marzo de 2018, 15:25:02 (UTC+1), Ralf Ramsauer  
>>>>> escribió:
>>>>>> Hi,
>>>>>>
>>>>>> On 03/21/2018 02:54 PM, iallende wrote:
>>>>>>> Hi everyone,
>>>>>>>
>>>>>>> I am trying to run Jailhouse in the ZynqMP, with Linux PREEMPT RT in 
>>>>>>> another cell. However, I have some problems when I add the second Linux.
>>>>>>>
>>>>>>> root@xilinx-zcu102-2017_4:/# modprobe jailhouse
>>>>>>> [   52.445169] jailhouse: loading out-of-tree module taints kernel.
>>>>>>> root@xilinx-zcu102-2017_4:/# ls /dev/jailhouse ^C
>>>>>>> root@xilinx-zcu102-2017_4:/# jailhouse enable zynqmp-zcu102.cell 
>>>>>>>
>>>>>>> Initializing Jailhouse hypervisor v0.7 (0-g5c13b64) on CPU 2
>>>>>> Please checkout next and try again. This might already fix your issue.
>>>>> With v0.8 i get this WARNING and I can load the module:
>>>>> WARNING: "__hyp_stub_vectors" [/jailhouse/driver/jailhouse.ko] undefined!
>>>> Please switch to next, and not to v0.8. Compile your kernel with
>>>> CONFIG_KALLSYMS_ALL=y, or use this [1] patch.
>>>>
>>>>   Ralf
>>>>
>>>> [1]
>>>> http://git.kiszka.org/?p=linux.git;a=commit;h=2a681cb2213e3ea0f142fae7345fb80208a88a53
>>>>>>> Code location: 0x0000ffffc0200050
>>>>>>> Page pool usage after early setup: mem 33/996, remap 64/131072
>>>>>>> Initializing processors:
>>>>>>>  CPU 2... OK
>>>>>>>  CPU 0... OK
>>>>>>>  CPU 3... OK
>>>>>>>  CPU 1... OK
>>>>>>> Adding virtual PCI device 00:00.0 to cell "ZynqMP-ZCU102"
>>>>>>> Adding virtual PCI device 00:01.0 to cell "ZynqMP-ZCU102"
>>>>>>> Page pool usage after late setup: mem 42/996, remap 69/131072
>>>>>>> Activating hypervisor
>>>>>>> [   63.697232] jailhouse: CONFIG_OF_OVERLAY disabled
>>>>>>> [   63.704029] jailhouse: failed to add virtual host controller
>>>>>>> [   63.711610] The Jailhouse is opening.
>>>>>>>
>>>>>>> root@xilinx-zcu102-2017_4:/# jailhouse cell linux 
>>>>>>> zynqmp-zcu102-linux-demo.cell Image -d system.dtb -i rootfs.cpio 
>>>>>>>
>>>>>>> FATAL: unhandled trap (exception class 0x17)
>>>>>> Exception class 0x17 is a SMC64 call.
>>>>>>
>>>>>>> Cell state before exception:
>>>>>>>  pc: ffffff800808e390   lr: ffffff8008467504 spsr: 20000145     EL1
>>>>>>>  sp: ffffffc87b927ab0  esr: 17 1 0000000
>>>>>>>  x0: 00000000c2000014   x1: 00000000fd1a0060   x2: 0000000000000000
>>>>>> Furthermore, it's a SIP_64.
>>>>>>
>>>>>> Commit 2482c47bc2d05f ("arm64: ignore SIPs used for low-power modes") on
>>>>>> next will probably fix your issue.
>>>>>>
>>>>>>   Ralf
>>>>>>>  x3: 0000000000000000   x4: 0000000000000000   x5: 0000000000000000
>>>>>>>  x6: 0000000000000000   x7: 0000000000000000   x8: ffffff8008d27ee0
>>>>>>>  x9: ffffffc87aaa4b5c  x10: ffffffc87b927b4c  x11: ffffff8008c8ccb2
>>>>>>> x12: 0000000000000000  x13: 0000000000000f93  x14: 0000000000000001
>>>>>>> x15: 0000000000000000  x16: ffffff8008193240  x17: 00000000004128f0
>>>>>>> x18: 0000000000040900  x19: ffffffc87b927b28  x20: 0000000000000001
>>>>>>> x21: 000000004784b740  x22: 000000004784b740  x23: fffffffffffffffa
>>>>>>> x24: 00000000000f4240  x25: 00000000000f4240  x26: 00000000000f4240
>>>>>>> x27: 0000000000000000  x28: 0000000000000000  x29: ffffffc87b927ac0
>>>>>>>
>>>>>>> Parking CPU 2 (Cell: "ZynqMP-ZCU102")
>>>>>>>
>>>>>>>
>>>>>>> Does anyone know why I have this problem? Am I missing any step?
>>>>>>>
>>>>>
>>>
>>> Sorry Ralf, I did an error with the dtb. It works with the 
>>> inmate-zynqmp-zcu102.dtb. However, I do not achieve to see the non-root 
>>> linux console. I have tried with ttyS0 and ttyS1, but nothing appears. How 
>>> can I access to the second cell?
>>
>> Sorry for the late response! Ok -- so the other issues are solved and
>> the rest works now?
>>
>> Try to enable the JAILHOUSE_DBCON [1] in your kernel config and allow
>> your cell to use it by adding the .flag JAILHOUSE_CELL_DEBUG_CONSOLE to
>> your inmate's cell config (see Documentation/debug-output.md), and use
>> jailhouse0 as output path. Then you should at least see the kernel booting.
>>
>> Maybe this already gives you a clue what's going on. As far as I can
>> see, the upstream inmate configs look fine.
>>
>> Are other inmates that use the same inmate config able to use the UART?
>>
>>   Ralf
>>
>> [1]
>> http://git.kiszka.org/?p=linux.git;a=commit;h=222ae01c41444f5bb8a8c6def3b8bd94ebede24a
> 
> Hi,
> 
> Perhaps I am not understanding well. But, do I need to know all that to have 
> the console of the non-root cell?
> 
> The zynqmp-zcu102-linux-demo.cell has the UART defined:
> /* UART */ {
>   .phys_start = 0xff010000,
>   .virt_start = 0xff010000,
>   .size = 0x1000,
>   .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
>            JAILHOUSE_MEM_IO | JAILHOUSE_MEM_ROOTSHARED,
> },
> 
> The non-root cell DTB has the same UART defined:
> uart: serial@ff010000 {
>   compatible = "cdns,uart-r1p12", "xlnx,xuartps";
>   reg = <0x0 0xff010000 0x0 0x1000>;
>   interrupts = <GIC_SPI 22 IRQ_TYPE_LEVEL_HIGH>;
>   clocks = <&uartclk>, <&uartclk>;
>   clock-names = "uart_clk", "pclk";
> };
> 
> 
> It is not posible to see the linux booting through this UART?
> 

It is possible to see Linux booting from this console and you should.
But as you don't see anything, my next approach would be to switch to
the debug console to see what's going on. Maybe this gives you a pointer.

Jan, is ttyS0 the valid first UART on the ZynqMP or is it called otherwise?

  Ralf

-- 
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 jailhouse-dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to