Re: Jailhouse zynqMP
El lunes, 23 de abril de 2018, 16:12:18 (UTC+2), J. Kiszka escribió: > On 2018-04-23 15:48, iallende wrote: > > El miércoles, 18 de abril de 2018, 16:05:13 (UTC+2), iallende escribió: > >> El miércoles, 18 de abril de 2018, 8:38:43 (UTC+2), J. Kiszka escribió: > El lunes, 16 de abril de 2018, 14:45:45 (UTC+2), J. Kiszka escribió: > > On 2018-04-16 14:21, iallende wrote: > >> El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: > >>> On 2018-04-12 15:15, iallende wrote: > It still does not work. I have the following: > > root@xilinx-zcu102-2017_4:~# modprobe jailhouse > [ 20.762034] jailhouse: loading out-of-tree module taints kernel. > root@xilinx-zcu102-2017_4:~# cd /cells/ > root@xilinx-zcu102-2017_4:/cells# jailhouse enable > zynqmp-zcu102.cell > > Initializing Jailhouse hypervisor v0.8 on CPU 2 > Code location: 0xc0200060 > Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 > Activating hypervisor > [ 29.825496] The Jailhouse is opening. > root@xilinx-zcu102-2017_4:/cells# > root@xilinx-zcu102-2017_4:/cells# > root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux > zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i > rootfs.cpio -c "console=ttyPS0,115200" > [ 65.192135] Read fail divider address: fd1a0060 > [ 65.198616] Read fail divider address: fd1a0060 > [ 65.205473] CPU2: shutdown > [ 65.210069] psci: CPU2 killed. > [ 65.248402] CPU3: shutdown > [ 65.252999] psci: CPU3 killed. > Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" > Shared memory connection established: "ZynqMP-linux-demo" <--> > "ZynqMP-ZCU102" > Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" > Created cell "ZynqMP-linux-demo" > Page pool usage after cell creation: mem 59/993, remap 69/131072 > [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" > Cell "ZynqMP-linux-demo" can be loaded > Started cell "ZynqMP-linux-demo" > root@xilinx-zcu102-2017_4:/cells# jailhouse cell list > ID NameState Assigned CPUs > Failed CPUs > 0 ZynqMP-ZCU102 running 0-1 > > 1 ZynqMP-linux-demo running 2-3 > > However, the UART does not show anything. I have tried with a > different Linux image and the same problem. I generate the images > with Petalinux. > > >>> > >>> Try debugging the non-root boot by using the Jailhouse console for the > >>> cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see > >>> Documentation/debug-output.md). Check if the UART is detected by the > >>> guest. Maybe the kernel is not configured as needed. > >>> > >>> Jan > >>> -- > >>> Siemens AG, Corporate Technology, CT RDA IOT SES-DE > >>> Corporate Competence Center Embedded Linux > >> > >> I have applied the patches for JAILHOUSE_DBCON and I added > >> JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the > >> cell like this: > >> jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d > >> inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" > >> > >> However, the booting does not appear. To see the debug output I have > >> to do "cat /dev/jailhouse", no? > >> > > > > Rather "jailhouse console". If that only lists output of the hypervisor > > itself, the guest does not start up. You then have some other issue. Is > > there anything you modified, compared to upstream Jailhouse > > configurations? Try reducing that to zero first. > > > > I can look up the setup on our ZCU102 to give you exact references to a > > known-to-work setup. Definitely working was vanilla Jailhouse v0.8 (I > > tested that prior to the release). I've also attached a reference config > > for the Linux inmate kernel. > > > > I hope we can eventually handle such setup questions via the > > jailhouse-image project, but right now that's not yet there. > > > > Jan > > > > -- > > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > > Corporate Competence Center Embedded Linux > > I did
Re: Jailhouse zynqMP
On 2018-04-23 15:48, iallende wrote: > El miércoles, 18 de abril de 2018, 16:05:13 (UTC+2), iallende escribió: >> El miércoles, 18 de abril de 2018, 8:38:43 (UTC+2), J. Kiszka escribió: El lunes, 16 de abril de 2018, 14:45:45 (UTC+2), J. Kiszka escribió: > On 2018-04-16 14:21, iallende wrote: >> El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: >>> On 2018-04-12 15:15, iallende wrote: It still does not work. I have the following: root@xilinx-zcu102-2017_4:~# modprobe jailhouse [ 20.762034] jailhouse: loading out-of-tree module taints kernel. root@xilinx-zcu102-2017_4:~# cd /cells/ root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell Initializing Jailhouse hypervisor v0.8 on CPU 2 Code location: 0xc0200060 Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 Activating hypervisor [ 29.825496] The Jailhouse is opening. root@xilinx-zcu102-2017_4:/cells# root@xilinx-zcu102-2017_4:/cells# root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "console=ttyPS0,115200" [ 65.192135] Read fail divider address: fd1a0060 [ 65.198616] Read fail divider address: fd1a0060 [ 65.205473] CPU2: shutdown [ 65.210069] psci: CPU2 killed. [ 65.248402] CPU3: shutdown [ 65.252999] psci: CPU3 killed. Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" Shared memory connection established: "ZynqMP-linux-demo" <--> "ZynqMP-ZCU102" Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" Created cell "ZynqMP-linux-demo" Page pool usage after cell creation: mem 59/993, remap 69/131072 [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" Cell "ZynqMP-linux-demo" can be loaded Started cell "ZynqMP-linux-demo" root@xilinx-zcu102-2017_4:/cells# jailhouse cell list ID NameState Assigned CPUs Failed CPUs 0 ZynqMP-ZCU102 running 0-1 1 ZynqMP-linux-demo running 2-3 However, the UART does not show anything. I have tried with a different Linux image and the same problem. I generate the images with Petalinux. >>> >>> Try debugging the non-root boot by using the Jailhouse console for the >>> cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see >>> Documentation/debug-output.md). Check if the UART is detected by the >>> guest. Maybe the kernel is not configured as needed. >>> >>> Jan >>> -- >>> Siemens AG, Corporate Technology, CT RDA IOT SES-DE >>> Corporate Competence Center Embedded Linux >> >> I have applied the patches for JAILHOUSE_DBCON and I added >> JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the >> cell like this: >> jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d >> inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" >> >> However, the booting does not appear. To see the debug output I have to >> do "cat /dev/jailhouse", no? >> > > Rather "jailhouse console". If that only lists output of the hypervisor > itself, the guest does not start up. You then have some other issue. Is > there anything you modified, compared to upstream Jailhouse > configurations? Try reducing that to zero first. > > I can look up the setup on our ZCU102 to give you exact references to a > known-to-work setup. Definitely working was vanilla Jailhouse v0.8 (I > tested that prior to the release). I've also attached a reference config > for the Linux inmate kernel. > > I hope we can eventually handle such setup questions via the > jailhouse-image project, but right now that's not yet there. > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux I did both images with Petalinux 2017.4 and its default bsp. The Kernel version is 4.9. How do you build your images? Yocto with meta-xilinx layer? >>> >>> No Yocto. Custom kernel config, mainline kernel, built via Linaro >>> cross-toolchain, standard distro image. It's
Re: Jailhouse zynqMP
El miércoles, 18 de abril de 2018, 16:05:13 (UTC+2), iallende escribió: > El miércoles, 18 de abril de 2018, 8:38:43 (UTC+2), J. Kiszka escribió: > > > El lunes, 16 de abril de 2018, 14:45:45 (UTC+2), J. Kiszka escribió: > > >> On 2018-04-16 14:21, iallende wrote: > > >>> El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: > > On 2018-04-12 15:15, iallende wrote: > > > It still does not work. I have the following: > > > > > > root@xilinx-zcu102-2017_4:~# modprobe jailhouse > > > [ 20.762034] jailhouse: loading out-of-tree module taints kernel. > > > root@xilinx-zcu102-2017_4:~# cd /cells/ > > > root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell > > > > > > Initializing Jailhouse hypervisor v0.8 on CPU 2 > > > Code location: 0xc0200060 > > > Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 > > > Activating hypervisor > > > [ 29.825496] The Jailhouse is opening. > > > root@xilinx-zcu102-2017_4:/cells# > > > root@xilinx-zcu102-2017_4:/cells# > > > root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux > > > zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i > > > rootfs.cpio -c "console=ttyPS0,115200" > > > [ 65.192135] Read fail divider address: fd1a0060 > > > [ 65.198616] Read fail divider address: fd1a0060 > > > [ 65.205473] CPU2: shutdown > > > [ 65.210069] psci: CPU2 killed. > > > [ 65.248402] CPU3: shutdown > > > [ 65.252999] psci: CPU3 killed. > > > Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" > > > Shared memory connection established: "ZynqMP-linux-demo" <--> > > > "ZynqMP-ZCU102" > > > Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" > > > Created cell "ZynqMP-linux-demo" > > > Page pool usage after cell creation: mem 59/993, remap 69/131072 > > > [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" > > > Cell "ZynqMP-linux-demo" can be loaded > > > Started cell "ZynqMP-linux-demo" > > > root@xilinx-zcu102-2017_4:/cells# jailhouse cell list > > > ID NameState Assigned CPUs > > > Failed CPUs > > > 0 ZynqMP-ZCU102 running 0-1 > > > > > > 1 ZynqMP-linux-demo running 2-3 > > > > > > However, the UART does not show anything. I have tried with a > > > different Linux image and the same problem. I generate the images > > > with Petalinux. > > > > > > > Try debugging the non-root boot by using the Jailhouse console for the > > cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see > > Documentation/debug-output.md). Check if the UART is detected by the > > guest. Maybe the kernel is not configured as needed. > > > > Jan > > -- > > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > > Corporate Competence Center Embedded Linux > > >>> > > >>> I have applied the patches for JAILHOUSE_DBCON and I added > > >>> JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the > > >>> cell like this: > > >>> jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d > > >>> inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" > > >>> > > >>> However, the booting does not appear. To see the debug output I have to > > >>> do "cat /dev/jailhouse", no? > > >>> > > >> > > >> Rather "jailhouse console". If that only lists output of the hypervisor > > >> itself, the guest does not start up. You then have some other issue. Is > > >> there anything you modified, compared to upstream Jailhouse > > >> configurations? Try reducing that to zero first. > > >> > > >> I can look up the setup on our ZCU102 to give you exact references to a > > >> known-to-work setup. Definitely working was vanilla Jailhouse v0.8 (I > > >> tested that prior to the release). I've also attached a reference config > > >> for the Linux inmate kernel. > > >> > > >> I hope we can eventually handle such setup questions via the > > >> jailhouse-image project, but right now that's not yet there. > > >> > > >> Jan > > >> > > >> -- > > >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE > > >> Corporate Competence Center Embedded Linux > > > > > > I did both images with Petalinux 2017.4 and its default bsp. The Kernel > > > version is 4.9. How do you build your images? Yocto with meta-xilinx > > > layer? > > > > No Yocto. Custom kernel config, mainline kernel, built via
Re: Jailhouse zynqMP
El miércoles, 18 de abril de 2018, 8:38:43 (UTC+2), J. Kiszka escribió: > > El lunes, 16 de abril de 2018, 14:45:45 (UTC+2), J. Kiszka escribió: > >> On 2018-04-16 14:21, iallende wrote: > >>> El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: > On 2018-04-12 15:15, iallende wrote: > > It still does not work. I have the following: > > > > root@xilinx-zcu102-2017_4:~# modprobe jailhouse > > [ 20.762034] jailhouse: loading out-of-tree module taints kernel. > > root@xilinx-zcu102-2017_4:~# cd /cells/ > > root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell > > > > Initializing Jailhouse hypervisor v0.8 on CPU 2 > > Code location: 0xc0200060 > > Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 > > Activating hypervisor > > [ 29.825496] The Jailhouse is opening. > > root@xilinx-zcu102-2017_4:/cells# > > root@xilinx-zcu102-2017_4:/cells# > > root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux > > zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i > > rootfs.cpio -c "console=ttyPS0,115200" > > [ 65.192135] Read fail divider address: fd1a0060 > > [ 65.198616] Read fail divider address: fd1a0060 > > [ 65.205473] CPU2: shutdown > > [ 65.210069] psci: CPU2 killed. > > [ 65.248402] CPU3: shutdown > > [ 65.252999] psci: CPU3 killed. > > Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" > > Shared memory connection established: "ZynqMP-linux-demo" <--> > > "ZynqMP-ZCU102" > > Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" > > Created cell "ZynqMP-linux-demo" > > Page pool usage after cell creation: mem 59/993, remap 69/131072 > > [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" > > Cell "ZynqMP-linux-demo" can be loaded > > Started cell "ZynqMP-linux-demo" > > root@xilinx-zcu102-2017_4:/cells# jailhouse cell list > > ID NameState Assigned CPUs > > Failed CPUs > > 0 ZynqMP-ZCU102 running 0-1 > > > > 1 ZynqMP-linux-demo running 2-3 > > > > However, the UART does not show anything. I have tried with a different > > Linux image and the same problem. I generate the images with Petalinux. > > > > Try debugging the non-root boot by using the Jailhouse console for the > cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see > Documentation/debug-output.md). Check if the UART is detected by the > guest. Maybe the kernel is not configured as needed. > > Jan > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux > >>> > >>> I have applied the patches for JAILHOUSE_DBCON and I added > >>> JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the > >>> cell like this: > >>> jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d > >>> inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" > >>> > >>> However, the booting does not appear. To see the debug output I have to > >>> do "cat /dev/jailhouse", no? > >>> > >> > >> Rather "jailhouse console". If that only lists output of the hypervisor > >> itself, the guest does not start up. You then have some other issue. Is > >> there anything you modified, compared to upstream Jailhouse > >> configurations? Try reducing that to zero first. > >> > >> I can look up the setup on our ZCU102 to give you exact references to a > >> known-to-work setup. Definitely working was vanilla Jailhouse v0.8 (I > >> tested that prior to the release). I've also attached a reference config > >> for the Linux inmate kernel. > >> > >> I hope we can eventually handle such setup questions via the > >> jailhouse-image project, but right now that's not yet there. > >> > >> Jan > >> > >> -- > >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE > >> Corporate Competence Center Embedded Linux > > > > I did both images with Petalinux 2017.4 and its default bsp. The Kernel > > version is 4.9. How do you build your images? Yocto with meta-xilinx layer? > > No Yocto. Custom kernel config, mainline kernel, built via Linaro > cross-toolchain, standard distro image. It's basically the manual form > of https://github.com/siemens/jailhouse-images. > > > > > I have tried running non-root cell with a new image built with Yocto and > > meta-xilinx and the same has happened. > > > > Sorry for such amount
Re: Jailhouse zynqMP
On 2018-04-17 15:51, allende.ima...@gmail.com wrote: > El lunes, 16 de abril de 2018, 14:45:45 (UTC+2), J. Kiszka escribió: >> On 2018-04-16 14:21, iallende wrote: >>> El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: On 2018-04-12 15:15, iallende wrote: > It still does not work. I have the following: > > root@xilinx-zcu102-2017_4:~# modprobe jailhouse > [ 20.762034] jailhouse: loading out-of-tree module taints kernel. > root@xilinx-zcu102-2017_4:~# cd /cells/ > root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell > > Initializing Jailhouse hypervisor v0.8 on CPU 2 > Code location: 0xc0200060 > Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 > Activating hypervisor > [ 29.825496] The Jailhouse is opening. > root@xilinx-zcu102-2017_4:/cells# > root@xilinx-zcu102-2017_4:/cells# > root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux > zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i > rootfs.cpio -c "console=ttyPS0,115200" > [ 65.192135] Read fail divider address: fd1a0060 > [ 65.198616] Read fail divider address: fd1a0060 > [ 65.205473] CPU2: shutdown > [ 65.210069] psci: CPU2 killed. > [ 65.248402] CPU3: shutdown > [ 65.252999] psci: CPU3 killed. > Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" > Shared memory connection established: "ZynqMP-linux-demo" <--> > "ZynqMP-ZCU102" > Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" > Created cell "ZynqMP-linux-demo" > Page pool usage after cell creation: mem 59/993, remap 69/131072 > [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" > Cell "ZynqMP-linux-demo" can be loaded > Started cell "ZynqMP-linux-demo" > root@xilinx-zcu102-2017_4:/cells# jailhouse cell list > ID NameState Assigned CPUs > Failed CPUs > 0 ZynqMP-ZCU102 running 0-1 > > 1 ZynqMP-linux-demo running 2-3 > > However, the UART does not show anything. I have tried with a different > Linux image and the same problem. I generate the images with Petalinux. > Try debugging the non-root boot by using the Jailhouse console for the cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see Documentation/debug-output.md). Check if the UART is detected by the guest. Maybe the kernel is not configured as needed. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux >>> >>> I have applied the patches for JAILHOUSE_DBCON and I added >>> JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the cell >>> like this: >>> jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d >>> inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" >>> >>> However, the booting does not appear. To see the debug output I have to do >>> "cat /dev/jailhouse", no? >>> >> >> Rather "jailhouse console". If that only lists output of the hypervisor >> itself, the guest does not start up. You then have some other issue. Is >> there anything you modified, compared to upstream Jailhouse >> configurations? Try reducing that to zero first. >> >> I can look up the setup on our ZCU102 to give you exact references to a >> known-to-work setup. Definitely working was vanilla Jailhouse v0.8 (I >> tested that prior to the release). I've also attached a reference config >> for the Linux inmate kernel. >> >> I hope we can eventually handle such setup questions via the >> jailhouse-image project, but right now that's not yet there. >> >> Jan >> >> -- >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE >> Corporate Competence Center Embedded Linux > > I did both images with Petalinux 2017.4 and its default bsp. The Kernel > version is 4.9. How do you build your images? Yocto with meta-xilinx layer? No Yocto. Custom kernel config, mainline kernel, built via Linaro cross-toolchain, standard distro image. It's basically the manual form of https://github.com/siemens/jailhouse-images. > > I have tried running non-root cell with a new image built with Yocto and > meta-xilinx and the same has happened. > > Sorry for such amount of doubts and not achieving it. Perhaps when if I > achieve it I can create a document for the respository as there is for the > Banana-pi and the Emtrion. > The board setup isn't trivial, and that's why I'm planning to encode
Re: Jailhouse zynqMP
El lunes, 16 de abril de 2018, 14:45:45 (UTC+2), J. Kiszka escribió: > On 2018-04-16 14:21, iallende wrote: > > El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: > >> On 2018-04-12 15:15, iallende wrote: > >>> It still does not work. I have the following: > >>> > >>> root@xilinx-zcu102-2017_4:~# modprobe jailhouse > >>> [ 20.762034] jailhouse: loading out-of-tree module taints kernel. > >>> root@xilinx-zcu102-2017_4:~# cd /cells/ > >>> root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell > >>> > >>> Initializing Jailhouse hypervisor v0.8 on CPU 2 > >>> Code location: 0xc0200060 > >>> Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 > >>> Activating hypervisor > >>> [ 29.825496] The Jailhouse is opening. > >>> root@xilinx-zcu102-2017_4:/cells# > >>> root@xilinx-zcu102-2017_4:/cells# > >>> root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux > >>> zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i > >>> rootfs.cpio -c "console=ttyPS0,115200" > >>> [ 65.192135] Read fail divider address: fd1a0060 > >>> [ 65.198616] Read fail divider address: fd1a0060 > >>> [ 65.205473] CPU2: shutdown > >>> [ 65.210069] psci: CPU2 killed. > >>> [ 65.248402] CPU3: shutdown > >>> [ 65.252999] psci: CPU3 killed. > >>> Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" > >>> Shared memory connection established: "ZynqMP-linux-demo" <--> > >>> "ZynqMP-ZCU102" > >>> Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" > >>> Created cell "ZynqMP-linux-demo" > >>> Page pool usage after cell creation: mem 59/993, remap 69/131072 > >>> [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" > >>> Cell "ZynqMP-linux-demo" can be loaded > >>> Started cell "ZynqMP-linux-demo" > >>> root@xilinx-zcu102-2017_4:/cells# jailhouse cell list > >>> ID NameState Assigned CPUs > >>> Failed CPUs > >>> 0 ZynqMP-ZCU102 running 0-1 > >>> > >>> 1 ZynqMP-linux-demo running 2-3 > >>> > >>> However, the UART does not show anything. I have tried with a different > >>> Linux image and the same problem. I generate the images with Petalinux. > >>> > >> > >> Try debugging the non-root boot by using the Jailhouse console for the > >> cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see > >> Documentation/debug-output.md). Check if the UART is detected by the > >> guest. Maybe the kernel is not configured as needed. > >> > >> Jan > >> -- > >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE > >> Corporate Competence Center Embedded Linux > > > > I have applied the patches for JAILHOUSE_DBCON and I added > > JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the cell > > like this: > > jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d > > inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" > > > > However, the booting does not appear. To see the debug output I have to do > > "cat /dev/jailhouse", no? > > > > Rather "jailhouse console". If that only lists output of the hypervisor > itself, the guest does not start up. You then have some other issue. Is > there anything you modified, compared to upstream Jailhouse > configurations? Try reducing that to zero first. > > I can look up the setup on our ZCU102 to give you exact references to a > known-to-work setup. Definitely working was vanilla Jailhouse v0.8 (I > tested that prior to the release). I've also attached a reference config > for the Linux inmate kernel. > > I hope we can eventually handle such setup questions via the > jailhouse-image project, but right now that's not yet there. > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux I did both images with Petalinux 2017.4 and its default bsp. The Kernel version is 4.9. How do you build your images? Yocto with meta-xilinx layer? I have tried running non-root cell with a new image built with Yocto and meta-xilinx and the same has happened. Sorry for such amount of doubts and not achieving it. Perhaps when if I achieve it I can create a document for the respository as there is for the Banana-pi and the Emtrion. -- 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.
Re: Jailhouse zynqMP
Hi, On 04/16/2018 02:21 PM, iallende wrote: > El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: >> On 2018-04-12 15:15, iallende wrote: >>> It still does not work. I have the following: >>> >>> root@xilinx-zcu102-2017_4:~# modprobe jailhouse >>> [ 20.762034] jailhouse: loading out-of-tree module taints kernel. >>> root@xilinx-zcu102-2017_4:~# cd /cells/ >>> root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell >>> >>> Initializing Jailhouse hypervisor v0.8 on CPU 2 >>> Code location: 0xc0200060 >>> Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 >>> Activating hypervisor >>> [ 29.825496] The Jailhouse is opening. >>> root@xilinx-zcu102-2017_4:/cells# >>> root@xilinx-zcu102-2017_4:/cells# >>> root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux >>> zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i >>> rootfs.cpio -c "console=ttyPS0,115200" >>> [ 65.192135] Read fail divider address: fd1a0060 >>> [ 65.198616] Read fail divider address: fd1a0060 >>> [ 65.205473] CPU2: shutdown >>> [ 65.210069] psci: CPU2 killed. >>> [ 65.248402] CPU3: shutdown >>> [ 65.252999] psci: CPU3 killed. >>> Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" >>> Shared memory connection established: "ZynqMP-linux-demo" <--> >>> "ZynqMP-ZCU102" >>> Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" >>> Created cell "ZynqMP-linux-demo" >>> Page pool usage after cell creation: mem 59/993, remap 69/131072 >>> [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" >>> Cell "ZynqMP-linux-demo" can be loaded >>> Started cell "ZynqMP-linux-demo" >>> root@xilinx-zcu102-2017_4:/cells# jailhouse cell list >>> ID NameState Assigned CPUs >>> Failed CPUs >>> 0 ZynqMP-ZCU102 running 0-1 >>> >>> 1 ZynqMP-linux-demo running 2-3 >>> >>> However, the UART does not show anything. I have tried with a different >>> Linux image and the same problem. I generate the images with Petalinux. >>> >> >> Try debugging the non-root boot by using the Jailhouse console for the >> cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see >> Documentation/debug-output.md). Check if the UART is detected by the >> guest. Maybe the kernel is not configured as needed. >> >> Jan >> -- >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE >> Corporate Competence Center Embedded Linux > > I have applied the patches for JAILHOUSE_DBCON and I added > JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the cell > like this: > jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d > inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" The con-type is an argument for Jailhouse demo inmates, but not for Linux itself. For example, you can load the uart-demo or gic-demo to see if the dbcon is working by jailhouse cell load foo gic-demo.bin -s "con-type=JAILHOUSE" -a 0x1000 Then you should see the output by either bei cat'ting /dev/jailhouse, or simply by using 'jailhouse console'. For Linux, you have to tell your kernel to use jailhouse0 as console output, e.g., by specifying the stdout-path in your device tree. Never tried this on ARM, but you could also try to jailhouse cell linux ... -c "console=jailhouse0" Admittedly, documentation is poor at the moment. > > However, the booting does not appear. To see the debug output I have to do > "cat /dev/jailhouse", no? see above. 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.
Re: Jailhouse zynqMP
On 2018-04-16 14:21, iallende wrote: > El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: >> On 2018-04-12 15:15, iallende wrote: >>> It still does not work. I have the following: >>> >>> root@xilinx-zcu102-2017_4:~# modprobe jailhouse >>> [ 20.762034] jailhouse: loading out-of-tree module taints kernel. >>> root@xilinx-zcu102-2017_4:~# cd /cells/ >>> root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell >>> >>> Initializing Jailhouse hypervisor v0.8 on CPU 2 >>> Code location: 0xc0200060 >>> Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 >>> Activating hypervisor >>> [ 29.825496] The Jailhouse is opening. >>> root@xilinx-zcu102-2017_4:/cells# >>> root@xilinx-zcu102-2017_4:/cells# >>> root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux >>> zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i >>> rootfs.cpio -c "console=ttyPS0,115200" >>> [ 65.192135] Read fail divider address: fd1a0060 >>> [ 65.198616] Read fail divider address: fd1a0060 >>> [ 65.205473] CPU2: shutdown >>> [ 65.210069] psci: CPU2 killed. >>> [ 65.248402] CPU3: shutdown >>> [ 65.252999] psci: CPU3 killed. >>> Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" >>> Shared memory connection established: "ZynqMP-linux-demo" <--> >>> "ZynqMP-ZCU102" >>> Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" >>> Created cell "ZynqMP-linux-demo" >>> Page pool usage after cell creation: mem 59/993, remap 69/131072 >>> [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" >>> Cell "ZynqMP-linux-demo" can be loaded >>> Started cell "ZynqMP-linux-demo" >>> root@xilinx-zcu102-2017_4:/cells# jailhouse cell list >>> ID NameState Assigned CPUs >>> Failed CPUs >>> 0 ZynqMP-ZCU102 running 0-1 >>> >>> 1 ZynqMP-linux-demo running 2-3 >>> >>> However, the UART does not show anything. I have tried with a different >>> Linux image and the same problem. I generate the images with Petalinux. >>> >> >> Try debugging the non-root boot by using the Jailhouse console for the >> cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see >> Documentation/debug-output.md). Check if the UART is detected by the >> guest. Maybe the kernel is not configured as needed. >> >> Jan >> -- >> Siemens AG, Corporate Technology, CT RDA IOT SES-DE >> Corporate Competence Center Embedded Linux > > I have applied the patches for JAILHOUSE_DBCON and I added > JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the cell > like this: > jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d > inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" > > However, the booting does not appear. To see the debug output I have to do > "cat /dev/jailhouse", no? > Rather "jailhouse console". If that only lists output of the hypervisor itself, the guest does not start up. You then have some other issue. Is there anything you modified, compared to upstream Jailhouse configurations? Try reducing that to zero first. I can look up the setup on our ZCU102 to give you exact references to a known-to-work setup. Definitely working was vanilla Jailhouse v0.8 (I tested that prior to the release). I've also attached a reference config for the Linux inmate kernel. I hope we can eventually handle such setup questions via the jailhouse-image project, but right now that's not yet there. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -- 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. .config.xz Description: application/xz
Re: Jailhouse zynqMP
El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió: > On 2018-04-12 15:15, iallende wrote: > > It still does not work. I have the following: > > > > root@xilinx-zcu102-2017_4:~# modprobe jailhouse > > [ 20.762034] jailhouse: loading out-of-tree module taints kernel. > > root@xilinx-zcu102-2017_4:~# cd /cells/ > > root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell > > > > Initializing Jailhouse hypervisor v0.8 on CPU 2 > > Code location: 0xc0200060 > > Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 > > Activating hypervisor > > [ 29.825496] The Jailhouse is opening. > > root@xilinx-zcu102-2017_4:/cells# > > root@xilinx-zcu102-2017_4:/cells# > > root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux > > zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i > > rootfs.cpio -c "console=ttyPS0,115200" > > [ 65.192135] Read fail divider address: fd1a0060 > > [ 65.198616] Read fail divider address: fd1a0060 > > [ 65.205473] CPU2: shutdown > > [ 65.210069] psci: CPU2 killed. > > [ 65.248402] CPU3: shutdown > > [ 65.252999] psci: CPU3 killed. > > Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" > > Shared memory connection established: "ZynqMP-linux-demo" <--> > > "ZynqMP-ZCU102" > > Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" > > Created cell "ZynqMP-linux-demo" > > Page pool usage after cell creation: mem 59/993, remap 69/131072 > > [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" > > Cell "ZynqMP-linux-demo" can be loaded > > Started cell "ZynqMP-linux-demo" > > root@xilinx-zcu102-2017_4:/cells# jailhouse cell list > > ID NameState Assigned CPUs > > Failed CPUs > > 0 ZynqMP-ZCU102 running 0-1 > > > > 1 ZynqMP-linux-demo running 2-3 > > > > However, the UART does not show anything. I have tried with a different > > Linux image and the same problem. I generate the images with Petalinux. > > > > Try debugging the non-root boot by using the Jailhouse console for the > cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see > Documentation/debug-output.md). Check if the UART is detected by the > guest. Maybe the kernel is not configured as needed. > > Jan > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE > Corporate Competence Center Embedded Linux I have applied the patches for JAILHOUSE_DBCON and I added JAILHOUSE_CELL_DEBUG_CONSOLE to zynqmp-zcu102-linux-demo.c. I load the cell like this: jailhouse cell linux zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i rootfs.cpio -c "con-type=jailhouse" However, the booting does not appear. To see the debug output I have to do "cat /dev/jailhouse", no? -- 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.
Re: Jailhouse zynqMP
On 2018-04-12 15:15, iallende wrote: > It still does not work. I have the following: > > root@xilinx-zcu102-2017_4:~# modprobe jailhouse > [ 20.762034] jailhouse: loading out-of-tree module taints kernel. > root@xilinx-zcu102-2017_4:~# cd /cells/ > root@xilinx-zcu102-2017_4:/cells# jailhouse enable zynqmp-zcu102.cell > > Initializing Jailhouse hypervisor v0.8 on CPU 2 > Code location: 0xc0200060 > Page pool usage after early setup: mem 33/993, 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/993, remap 69/131072 > Activating hypervisor > [ 29.825496] The Jailhouse is opening. > root@xilinx-zcu102-2017_4:/cells# > root@xilinx-zcu102-2017_4:/cells# > root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux > zynqmp-zcu102-linux-demo.cell Image -d inmate-zynqmp-zcu102.dtb -i > rootfs.cpio -c "console=ttyPS0,115200" > [ 65.192135] Read fail divider address: fd1a0060 > [ 65.198616] Read fail divider address: fd1a0060 > [ 65.205473] CPU2: shutdown > [ 65.210069] psci: CPU2 killed. > [ 65.248402] CPU3: shutdown > [ 65.252999] psci: CPU3 killed. > Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo" > Shared memory connection established: "ZynqMP-linux-demo" <--> "ZynqMP-ZCU102" > Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo" > Created cell "ZynqMP-linux-demo" > Page pool usage after cell creation: mem 59/993, remap 69/131072 > [ 65.299294] Created Jailhouse cell "ZynqMP-linux-demo" > Cell "ZynqMP-linux-demo" can be loaded > Started cell "ZynqMP-linux-demo" > root@xilinx-zcu102-2017_4:/cells# jailhouse cell list > ID NameState Assigned CPUs > Failed CPUs > 0 ZynqMP-ZCU102 running 0-1 > > 1 ZynqMP-linux-demo running 2-3 > > However, the UART does not show anything. I have tried with a different Linux > image and the same problem. I generate the images with Petalinux. > Try debugging the non-root boot by using the Jailhouse console for the cell (con-type=JAILHOUSE, cell flag JAILHOUSE_CELL_DEBUG_CONSOLE, see Documentation/debug-output.md). Check if the UART is detected by the guest. Maybe the kernel is not configured as needed. Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux -- 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.
Re: Jailhouse zynqMP
El jueves, 12 de abril de 2018, 9:20:03 (UTC+2), J. Kiszka escribió:
> On 2018-04-11 14:32, iallende wrote:
> > El martes, 10 de abril de 2018, 16:44:45 (UTC+2), J. Kiszka escribió:
> >> On 2018-04-10 15:12, Ralf Ramsauer wrote:
> >>> 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: 0xc0200050
> >> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> >> sp: ffc87b927ab0 esr: 17 1 000
> >> x0: c214 x1: fd1a0060 x2:
> > 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: x4: x5:
> >> x6: x7: x8: ff8008d27ee0
> >> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> >> x12: x13: 0f93 x14: 0001
> >> x15: x16: ff8008193240 x17: 004128f0
> >> x18: 00040900 x19: ffc87b927b28 x20: 0001
> >> x21: 4784b740 x22: 4784b740 x23: fffa
> >> x24: 000f4240 x25: 000f4240 x26: 000f4240
> >> x27: x28: x29: ffc87b927ac0
> >>
> >> 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
Re: Jailhouse zynqMP
On 2018-04-11 14:32, iallende wrote:
> El martes, 10 de abril de 2018, 16:44:45 (UTC+2), J. Kiszka escribió:
>> On 2018-04-10 15:12, Ralf Ramsauer wrote:
>>> 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: 0xc0200050
>> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
>> sp: ffc87b927ab0 esr: 17 1 000
>> x0: c214 x1: fd1a0060 x2:
> 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: x4: x5:
>> x6: x7: x8: ff8008d27ee0
>> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
>> x12: x13: 0f93 x14: 0001
>> x15: x16: ff8008193240 x17: 004128f0
>> x18: 00040900 x19: ffc87b927b28 x20: 0001
>> x21: 4784b740 x22: 4784b740 x23: fffa
>> x24: 000f4240 x25: 000f4240 x26: 000f4240
>> x27: x28: x29: ffc87b927ac0
>>
>> 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?
>
Re: Jailhouse zynqMP
El martes, 10 de abril de 2018, 16:44:45 (UTC+2), J. Kiszka escribió:
> On 2018-04-10 15:12, Ralf Ramsauer wrote:
> > 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: 0xc0200050
> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> sp: ffc87b927ab0 esr: 17 1 000
> x0: c214 x1: fd1a0060 x2:
> >>> 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: x4: x5:
> x6: x7: x8: ff8008d27ee0
> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> x12: x13: 0f93 x14: 0001
> x15: x16: ff8008193240 x17: 004128f0
> x18: 00040900 x19: ffc87b927b28 x20: 0001
> x21: 4784b740 x22: 4784b740 x23: fffa
> x24: 000f4240 x25: 000f4240 x26: 000f4240
> x27: x28: x29: ffc87b927ac0
>
> 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]
> >>>
Re: Jailhouse zynqMP
On 2018-04-10 15:12, Ralf Ramsauer wrote:
> 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: 0xc0200050
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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
sp: ffc87b927ab0 esr: 17 1 000
x0: c214 x1: fd1a0060 x2:
>>> 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: x4: x5:
x6: x7: x8: ff8008d27ee0
x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
x12: x13: 0f93 x14: 0001
x15: x16: ff8008193240 x17: 004128f0
x18: 00040900 x19: ffc87b927b28 x20: 0001
x21: 4784b740 x22: 4784b740 x23: fffa
x24: 000f4240 x25: 000f4240 x26: 000f4240
x27: x28: x29: ffc87b927ac0
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 = 0xff01,
>>
Re: Jailhouse zynqMP
El martes, 10 de abril de 2018, 15:12:25 (UTC+2), Ralf Ramsauer escribió:
> 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: 0xc0200050
> >>> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> >>> sp: ffc87b927ab0 esr: 17 1 000
> >>> x0: c214 x1: fd1a0060 x2:
> >> 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: x4: x5:
> >>> x6: x7: x8: ff8008d27ee0
> >>> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> >>> x12: x13: 0f93 x14: 0001
> >>> x15: x16: ff8008193240 x17: 004128f0
> >>> x18: 00040900 x19: ffc87b927b28 x20: 0001
> >>> x21: 4784b740 x22: 4784b740 x23: fffa
> >>> x24: 000f4240 x25: 000f4240 x26: 000f4240
> >>> x27: x28: x29: ffc87b927ac0
> >>>
> >>> 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
Re: Jailhouse zynqMP
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: 0xc0200050
>>> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
>>> sp: ffc87b927ab0 esr: 17 1 000
>>> x0: c214 x1: fd1a0060 x2:
>> 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: x4: x5:
>>> x6: x7: x8: ff8008d27ee0
>>> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
>>> x12: x13: 0f93 x14: 0001
>>> x15: x16: ff8008193240 x17: 004128f0
>>> x18: 00040900 x19: ffc87b927b28 x20: 0001
>>> x21: 4784b740 x22: 4784b740 x23: fffa
>>> x24: 000f4240 x25: 000f4240 x26: 000f4240
>>> x27: x28: x29: ffc87b927ac0
>>>
>>> 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 = 0xff01,
> .virt_start = 0xff01,
> .size = 0x1000,
> .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE |
>JAILHOUSE_MEM_IO | JAILHOUSE_MEM_ROOTSHARED,
> },
Re: Jailhouse zynqMP
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: 0xc0200050
> > 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> > sp: ffc87b927ab0 esr: 17 1 000
> > x0: c214 x1: fd1a0060 x2:
> 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: x4: x5:
> > x6: x7: x8: ff8008d27ee0
> > x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> > x12: x13: 0f93 x14: 0001
> > x15: x16: ff8008193240 x17: 004128f0
> > x18: 00040900 x19: ffc87b927b28 x20: 0001
> > x21: 4784b740 x22: 4784b740 x23: fffa
> > x24: 000f4240 x25: 000f4240 x26: 000f4240
> > x27: x28: x29: ffc87b927ac0
> >
> > 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 = 0xff01,
.virt_start = 0xff01,
.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@ff01 {
compatible
Re: Jailhouse zynqMP
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: 0xc0200050
> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> sp: ffc87b927ab0 esr: 17 1 000
> x0: c214 x1: fd1a0060 x2:
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: x4: x5:
> x6: x7: x8: ff8008d27ee0
> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> x12: x13: 0f93 x14: 0001
> x15: x16: ff8008193240 x17: 004128f0
> x18: 00040900 x19: ffc87b927b28 x20: 0001
> x21: 4784b740 x22: 4784b740 x23: fffa
> x24: 000f4240 x25: 000f4240 x26: 000f4240
> x27: x28: x29: ffc87b927ac0
>
> 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
--
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.
Re: Jailhouse zynqMP
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: 0xc0200050
> >>> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> >>> sp: ffc87b927ab0 esr: 17 1 000
> >>> x0: c214 x1: fd1a0060 x2:
> >> 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: x4: x5:
> >>> x6: x7: x8: ff8008d27ee0
> >>> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> >>> x12: x13: 0f93 x14: 0001
> >>> x15: x16: ff8008193240 x17: 004128f0
> >>> x18: 00040900 x19: ffc87b927b28 x20: 0001
> >>> x21: 4784b740 x22: 4784b740 x23: fffa
> >>> x24: 000f4240 x25: 000f4240 x26: 000f4240
> >>> x27: x28: x29: ffc87b927ac0
> >>>
> >>> 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?
--
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.
Re: Jailhouse zynqMP
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: 0xc0200050
> >>> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> >>> sp: ffc87b927ab0 esr: 17 1 000
> >>> x0: c214 x1: fd1a0060 x2:
> >> 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: x4: x5:
> >>> x6: x7: x8: ff8008d27ee0
> >>> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> >>> x12: x13: 0f93 x14: 0001
> >>> x15: x16: ff8008193240 x17: 004128f0
> >>> x18: 00040900 x19: ffc87b927b28 x20: 0001
> >>> x21: 4784b740 x22: 4784b740 x23: fffa
> >>> x24: 000f4240 x25: 000f4240 x26: 000f4240
> >>> x27: x28: x29: ffc87b927ac0
> >>>
> >>> Parking CPU 2 (Cell: "ZynqMP-ZCU102")
> >>>
> >>>
> >>> Does anyone know why I have this problem? Am I missing any step?
> >>>
> >
I get a similar result with next:
root@xilinx-zcu102-2017_4:/cells# jailhouse cell linux
zynqmp-zcu102-linux-demo.cell Image -d system.dtb -i rootfs.cpio -c
"console=ttyS1,1152000"
[ 412.856498] CPU2: shutdown
[ 412.861054] psci: CPU2 killed.
[ 412.900346] CPU3: shutdown
[ 412.904853] psci: CPU3 killed.
Adding virtual PCI device 00:00.0 to cell "ZynqMP-linux-demo"
Shared memory connection established: "ZynqMP-linux-demo" <--> "ZynqMP-ZCU102"
Adding virtual PCI device 00:02.0 to cell "ZynqMP-linux-demo"
Created cell "ZynqMP-linux-demo"
Page pool usage after cell creation: mem 59/993, remap 69/131072
[ 412.951205] Created Jailhouse cell "ZynqMP-linux-demo"
Cell "ZynqMP-linux-demo" can be loaded
Started cell "ZynqMP-linux-demo"
Unhandled data write at 0xf9020004(4)
FATAL: unhandled trap (exception class 0x24)
Cell state before exception:
pc: ff800840e4a4 lr: ff800840e49c spsr: 6085 EL1
sp: ff8008ca3dc0 esr: 24 1 1800047
x0: 00f0 x1: x2: ff800800041c
x3: 0080 x4: a0a0a0a0 x5: ff8008000394
x6: x7: x8: ffc016808400
x9: x10: ffbf005a0220 x11: ff800840e238
x12: ff800840dc08 x13: x14:
x15: x16: 0002 x17: 0002
x18: x19: ff8008caa000 x20: ff8008020004
x21: x22: ff800800 x23: ff8008ca9ff8
x24: ffc017fcafb8 x25: 0root@xilinx-zcu102-2017_4:/cells# 000
x26: ffc017fcafb8
x27: x28: 000810e20018 x29: ff8008ca3dc0
--
You received this message
Re: Jailhouse zynqMP
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: 0xc0200050
> >>> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> >>> sp: ffc87b927ab0 esr: 17 1 000
> >>> x0: c214 x1: fd1a0060 x2:
> >> 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: x4: x5:
> >>> x6: x7: x8: ff8008d27ee0
> >>> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> >>> x12: x13: 0f93 x14: 0001
> >>> x15: x16: ff8008193240 x17: 004128f0
> >>> x18: 00040900 x19: ffc87b927b28 x20: 0001
> >>> x21: 4784b740 x22: 4784b740 x23: fffa
> >>> x24: 000f4240 x25: 000f4240 x26: 000f4240
> >>> x27: x28: x29: ffc87b927ac0
> >>>
> >>> Parking CPU 2 (Cell: "ZynqMP-ZCU102")
> >>>
> >>>
> >>> Does anyone know why I have this problem? Am I missing any step?
> >>>
> >
It works with jailhouse-next, however, how can we switch between consoles?
root@xilinx-zcu102-2017_4:/cells# jailhouse cell list
ID NameState Assigned CPUs Failed
CPUs
0 ZynqMP-ZCU102 running 0-1
1 ZynqMP-linux-demo running 2-3
--
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.
Re: Jailhouse zynqMP
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: 0xc0200050
>>> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
>>> sp: ffc87b927ab0 esr: 17 1 000
>>> x0: c214 x1: fd1a0060 x2:
>> 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: x4: x5:
>>> x6: x7: x8: ff8008d27ee0
>>> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
>>> x12: x13: 0f93 x14: 0001
>>> x15: x16: ff8008193240 x17: 004128f0
>>> x18: 00040900 x19: ffc87b927b28 x20: 0001
>>> x21: 4784b740 x22: 4784b740 x23: fffa
>>> x24: 000f4240 x25: 000f4240 x26: 000f4240
>>> x27: x28: x29: ffc87b927ac0
>>>
>>> Parking CPU 2 (Cell: "ZynqMP-ZCU102")
>>>
>>>
>>> Does anyone know why I have this problem? Am I missing any step?
>>>
>
--
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.
Re: Jailhouse zynqMP
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!
> > Code location: 0xc0200050
> > 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> > sp: ffc87b927ab0 esr: 17 1 000
> > x0: c214 x1: fd1a0060 x2:
> 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: x4: x5:
> > x6: x7: x8: ff8008d27ee0
> > x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> > x12: x13: 0f93 x14: 0001
> > x15: x16: ff8008193240 x17: 004128f0
> > x18: 00040900 x19: ffc87b927b28 x20: 0001
> > x21: 4784b740 x22: 4784b740 x23: fffa
> > x24: 000f4240 x25: 000f4240 x26: 000f4240
> > x27: x28: x29: ffc87b927ac0
> >
> > Parking CPU 2 (Cell: "ZynqMP-ZCU102")
> >
> >
> > Does anyone know why I have this problem? Am I missing any step?
> >
--
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.
Re: Jailhouse zynqMP
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.
> Code location: 0xc0200050
> 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: ff800808e390 lr: ff8008467504 spsr: 2145 EL1
> sp: ffc87b927ab0 esr: 17 1 000
> x0: c214 x1: fd1a0060 x2:
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: x4: x5:
> x6: x7: x8: ff8008d27ee0
> x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2
> x12: x13: 0f93 x14: 0001
> x15: x16: ff8008193240 x17: 004128f0
> x18: 00040900 x19: ffc87b927b28 x20: 0001
> x21: 4784b740 x22: 4784b740 x23: fffa
> x24: 000f4240 x25: 000f4240 x26: 000f4240
> x27: x28: x29: ffc87b927ac0
>
> Parking CPU 2 (Cell: "ZynqMP-ZCU102")
>
>
> Does anyone know why I have this problem? Am I missing any step?
>
--
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.
Jailhouse zynqMP
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 Code location: 0xc0200050 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) Cell state before exception: pc: ff800808e390 lr: ff8008467504 spsr: 2145 EL1 sp: ffc87b927ab0 esr: 17 1 000 x0: c214 x1: fd1a0060 x2: x3: x4: x5: x6: x7: x8: ff8008d27ee0 x9: ffc87aaa4b5c x10: ffc87b927b4c x11: ff8008c8ccb2 x12: x13: 0f93 x14: 0001 x15: x16: ff8008193240 x17: 004128f0 x18: 00040900 x19: ffc87b927b28 x20: 0001 x21: 4784b740 x22: 4784b740 x23: fffa x24: 000f4240 x25: 000f4240 x26: 000f4240 x27: x28: x29: ffc87b927ac0 Parking CPU 2 (Cell: "ZynqMP-ZCU102") Does anyone know why I have this problem? Am I missing any step? -- 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.
