Hi, Sounds like a good idea, firstly Valentine has a good point I also think there is something wrong with the I/O port access (if not then something else in the I/O) so I changed debug_console.phys_start points from 0x3f8 to 0x3e8 in my configs/myboard.c and then make again to obtain a new myboard.cell file as I am using ttyS2 (I checked this in my /boot/EFI/BOOT/grub.cfg) and it's standard address is 0x3e8 but is that it?, I think I may have to change something else in myboard.c but I am unsure of what to change if any.
I turned CPU 1 offline and tried enabling jailhouse and I get an Invalid argument error for JAILHOUSE_ENABLE obviously due to the return of -EINVAL from jailhouse_cmd_enable() function from driver/main.c due to the if conditions set but still no hypervisor output, I just see the printf(); messages I manually created, I then read about the article contributed by valentine on understanding the jailhouse hypervisor: https://lwn.net/Articles/578295/ that explains about the role of the functions and how calls are made. I realize that my program is not entering the entry(); or init_early(); function in hypervisor/setup.c file as this is the file which seems to be printing out the hypervisor output , may be the system is crashing before that ? , may be the information about the IO in configs/myboard.c still incorrect (my suspect) , Any suggestions? Regards, Swaraj Dube. -----Original Message----- From: Jan Kiszka [mailto:jan.kis...@siemens.com] Sent: Wednesday, July 13, 2016 11:15 PM To: Dube, Swaraj <swaraj.d...@intel.com>; Valentine Sinitsyn <valentine.sinit...@gmail.com>; Jailhouse <jailhouse-dev@googlegroups.com> Subject: Re: ioctl function not completing and hypervisor output On 2016-07-13 18:07, Dube, Swaraj wrote: > Hi, > > Thanks for the reply, I think what you are referring to is the COM right , I > read about it, COM1-4 having I/O port addresses 0x3f8 , 0x2f8 , 0x3e8 and > 0x2e8 respectively . Currently debug_console.phys_start in my > configs/myboard.c points to the address 0x3f8 which should be of standard > COM1 whereas I am using COM5 so I'll try finding the address of COM5, hope I > am getting it right, kindly correct me if I am getting it wrong. If you want to debug the UART output of Jailhouse without crashing your system every time: Take one of the configured cores offline (echo 0 > /sys/devices/system/cpu/cpu1/online) before calling jailhouse enable. That will make the hypervisor fail gracefully with -EINVAL, but you will see messages of it trying to enable the remaining CPUs - provided we do not crash even earlier in the setup. Jan -- Siemens AG, Corporate Technology, CT RDA ITP 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.