On 2018-02-13 08:19, bharat gohil wrote:
> Hi Jan,
>
> I tried your second method to bringdown core and check but result are same,
>
> #cat /proc/cpuinfo
> processor : 0
> BogoMIPS : 26.00
> Features : fp asimd evtstrm aes pmull sha1 sha2 crc32
> CPU implementer : 0x41
> CPU architecture: 8
> CPU variant : 0x0
> CPU part : 0xd04
> CPU revision : 1
>
> #jailhouse enable XXXXX.cell
>
> Initializing Jailhouse hypervisor v0.8 (9-g5eec601-dirty) on CPU 0
> Code location: 0x0000ffffc0200060
> Page pool usage after early setup: mem 57/16356, remap 16/131072
> Initializing processors:
> CPU 0... OK
> Adding virtual PCI device 00:00.0 to cell "XXXXX"
> Page pool usage after late setup: mem 62/16356, remap 21/131072
> Activating hypervisor
A lock-up, no more invalid access reports?
What is core 0? What are cores 1 and 2? What happens when you use those
cores only?
Make sure to analyze the issue systematically. We see a problem now that
has a non-obvious cause.
>
> Can you please explain your first opinion ?/
> You may filter out some uninteresting reports by adding "if (phys !=
> 0x7c017000)" as
> condition (that address is - in your build - the zero page where the
> hypervisor regions gets mapped to for the root cell).
>
diff --git a/hypervisor/paging.c b/hypervisor/paging.c
index b950a816..4149510f 100644
--- a/hypervisor/paging.c
+++ b/hypervisor/paging.c
@@ -286,6 +286,8 @@ int paging_create(const struct paging_structures
*pg_structs,
virt &= PAGE_MASK;
size = PAGE_ALIGN(size);
+ if (phys != 0x7c017000)
+ printk("%s: %p phys %lx size %lx virt %lx flags %lx\n",
__func__, pg_structs, phys, size, virt, flags);
while (size > 0) {
const struct paging *paging = pg_structs->root_paging;
page_table_t pt = pg_structs->root_table;
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.
