On 21.05.21 08:21, Jiafei Pan wrote:
> 1. Use virt_addr to be same with phys_addr for memory
> 2. Loading inmate binary from start of virt_addr
> 3. Use 1M bytes memory in order to load Zephyr
> 4. Using CPU Core2 and Core3 to demo Zephyr SMP
> 

Could the Linux demo be enhanced to cater both use cases? If not, at 
least make sure that the common bits are actually common (see diff 
between both files).

BTW, we have a finding of "jailhouse config check" in the root cell 
config:

Reading configuration set:
  Root cell:     ls1046a (configs/arm64/ls1046a-rdb.cell)
Overlapping memory regions inside cell:

In cell 'ls1046a', region 9
  phys_start: 0x0000000080000000
  virt_start: 0x0000000080000000
  size:       0x0000000040000000
  flags:      JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | JAILHOUSE_MEM_EXECUTE
physically and virtually overlaps with region 12
  phys_start: 0x00000000bf900000
  virt_start: 0x00000000bf900000
  size:       0x0000000000100000
  flags:      JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | JAILHOUSE_MEM_EXECUTE

Overlapping memory regions with hypervisor: None
Missing PCI MMCONFIG interceptions: None
Missing resource interceptions for architecture x86: None

Jan

-- 
Siemens AG, T RDA IOT
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/6b72efce-b519-41d5-bc69-8d04e3eb9970%40siemens.com.

Reply via email to