On 19.10.18 11:19, Jan Kiszka wrote:
On 19.10.18 09:42, minskey guo wrote:


to get a bzImage for non-root cell.  Now, the COM1 has output now during booting non-root-cell linux , but I run into another issue:

      1.797742] RAPL PMU: API unit is 2^-32 Joules, 5 fixed counters, 655360 ms ovfl timer
[    1.805696] RAPL PMU: hw unit of domain pp0-core 2^-14 Joules
[    1.811470] RAPL PMU: hw unit of domain package 2^-14 Joules
[    1.817155] RAPL PMU: hw unit of domain dram 2^-14 Joules
[    1.822574] RAPL PMU: hw unit of domain pp1-gpu 2^-14 Joules
[    1.828254] RAPL PMU: hw unit of domain psys 2^-14 Joules
[    1.833679] clocksource: tsc: mask: 0xffffffffffffffff max_cycles: 0x2717868ea45, max_idle_s
[    1.843722] clocksource: Switched to clocksource tsc
FATAL: Invalid PIO read, port: 87 size: 1

That's a legacy resources, and that indicates your kernel lacks Jailhouse
awareness (CONFIG_JAILHOUSE_GUEST). There kernel will also report during boot if
it detected (and is aware of) Jailhouse.

My kconfig has CONFIG_JAILHOUSE_GUEST.  Just realized that 87 is hex, so it is DMA page register port.   Currently, I set pio_bitmap[] for that port to 1 in both root and non-root cell. What else should I do ?


You should not (have to) hand this over. I thought to remember it was disabled by one of the platform hooks in x86 that we have for Jailhouse, but maybe it was some driver that should rather be turned off.

Try deriving your config from the one we using in jailhouse-images.

Actually, we have the issue in jailhouse-image as well. Will send out a patch these days, but the trick to resolve it is simple: disable CONFIG_ISA_DMA_API (requires CONFIG_EXPERT). The issue started with 4.18

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.

Reply via email to