Re: Running demo application in x86 platform

2018-02-07 Thread Jan Kiszka
On 2018-02-07 11:02, a.ku...@matellio.com wrote:
>  
>> The ioapic-demo is a special test you should not start with unless you
>> know what it does. Focus on apic-demo and maybe booting a second Linux.
>>
>> Jan
> 
> 
> Hi
> 
>  I tried to run apic-demo in non-root cell, but it is not giving any logs in 
> jailhouse console, whether we need to do any modification in non-root cell 
> config.

Please read the documentation regarding configuring the output console
of our demo inmates. Or start with the (almost) fully documented
QEMU/KVM reference case. There, configuration and (virtual) hardware
match without additional tuning.

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 on OrangePI PC2 and A35/A72 based board

2018-02-07 Thread Jan Kiszka
On 2018-02-07 10:27, bharat gohil wrote:
> Hi
> 
> I was trying to Run jailhouse on two board i.e OrangePi PC2 and Quad core 
> A35/A72 based SoC.
> 
> I am able run Jailhouse on OrangePI PC2 and ran simple application on single 
> core which blinks the LED which works fine on OrangePI PC2 board.
> 
> But I have problem running Jailhouse on other board which has A35 and A72.
> 
> I got following crash when enable Jailhouse on this board,
> 
> Initializing Jailhouse hypervisor v0.8 (9-g5eec601-dirty) on CPU 0
> Code location: 0xc0200060
> Page pool usage after early setup: mem 61/16356, remap 48/131072
> Initializing processors:
>  CPU 0... OK
>  CPU 1... OK
>  CPU 2... OK
> Adding virtual PCI device 00:00.0 to cell "Dione"
> Page pool usage after late setup: mem 66/16356, remap 53/131072
> FATAL: instruction abort at 0x40ebdee8
> 
> FATAL: unhandled trap (exception class 0x20)
> Cell state before exception:
>  pc: ff80008f0ee8   lr: ff80008f0ee8 spsr: 61c5 EL1
>  sp: ffc02f003bb0  esr: 20 1 086
>  x0:    x1:    x2: 
>  x3:    x4:    x5: 
>  x6:    x7:    x8: 
>  x9:   x10:   x11: 
> x12:   x13:   x14: 
> x15:   x16:   x17: 
> x18:   x19: ff80008f4910  x20: ff801000
> x21: ff801000  x22:   x23: 0140
> x24: ff80008f4600  x25: ff8008d26de0  x26: ff801000
> x27: 02c4  x28: ffc02f00  x29: ffc02f003bb0
> 
> Parking CPU 2 (Cell: "X")
> 
> It generate exception at 0x40ebdee8 which is DDR address.
> 
> I have mentioned DDR range including above address in to the root-cell 
> configuration like this,
>  /* RAM */ {
> .phys_start = 0x4000,
> .virt_start = 0x4000,
> .size =0x02FF,
> .flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | 
> JAILHOUSE_MEM_EXECUTE,
> },
> 
> Can anyone help me to figure out what is the problem or how to debug and 
> resolve this issue?

Only the root cell is running at this point, right? There is no overlap
of other regions or the hypervisor region itself?

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: Running demo application in x86 platform

2018-02-07 Thread a . kumar
 
> The ioapic-demo is a special test you should not start with unless you
> know what it does. Focus on apic-demo and maybe booting a second Linux.
> 
> Jan


Hi

 I tried to run apic-demo in non-root cell, but it is not giving any logs in 
jailhouse console, whether we need to do any modification in non-root cell 
config.

Thanks
Ashok

-- 
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 on OrangePI PC2 and A35/A72 based board

2018-02-07 Thread bharat gohil
Hi

I was trying to Run jailhouse on two board i.e OrangePi PC2 and Quad core 
A35/A72 based SoC.

I am able run Jailhouse on OrangePI PC2 and ran simple application on single 
core which blinks the LED which works fine on OrangePI PC2 board.

But I have problem running Jailhouse on other board which has A35 and A72.

I got following crash when enable Jailhouse on this board,

Initializing Jailhouse hypervisor v0.8 (9-g5eec601-dirty) on CPU 0
Code location: 0xc0200060
Page pool usage after early setup: mem 61/16356, remap 48/131072
Initializing processors:
 CPU 0... OK
 CPU 1... OK
 CPU 2... OK
Adding virtual PCI device 00:00.0 to cell "Dione"
Page pool usage after late setup: mem 66/16356, remap 53/131072
FATAL: instruction abort at 0x40ebdee8

FATAL: unhandled trap (exception class 0x20)
Cell state before exception:
 pc: ff80008f0ee8   lr: ff80008f0ee8 spsr: 61c5 EL1
 sp: ffc02f003bb0  esr: 20 1 086
 x0:    x1:    x2: 
 x3:    x4:    x5: 
 x6:    x7:    x8: 
 x9:   x10:   x11: 
x12:   x13:   x14: 
x15:   x16:   x17: 
x18:   x19: ff80008f4910  x20: ff801000
x21: ff801000  x22:   x23: 0140
x24: ff80008f4600  x25: ff8008d26de0  x26: ff801000
x27: 02c4  x28: ffc02f00  x29: ffc02f003bb0

Parking CPU 2 (Cell: "X")

It generate exception at 0x40ebdee8 which is DDR address.

I have mentioned DDR range including above address in to the root-cell 
configuration like this,
 /* RAM */ {
.phys_start = 0x4000,
.virt_start = 0x4000,
.size =0x02FF,
.flags = JAILHOUSE_MEM_READ | JAILHOUSE_MEM_WRITE | 
JAILHOUSE_MEM_EXECUTE,
},

Can anyone help me to figure out what is the problem or how to debug and 
resolve this issue?

Thanks,
Bharat

-- 
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: Running demo application in x86 platform

2018-02-07 Thread Jan Kiszka
On 2018-02-07 07:47, a.ku...@matellio.com wrote:
> Hi,
> 
> 
>   I am trying to run demo application in non-root cell, once we start demo 
> application we are not able see any logs in jailhouse console. But if we run 
> ioapic-demo it is giving some crash report in jailhouse console(pasted in 
> below). 
> 
> Started cell "ioapic-demo"
> FATAL: Invalid PIO read, port: 1802 size: 2
> RIP: 0x027a RSP: 0x6ff0 FLAGS: 2
> RAX: 0x0100 RBX: 0x0238 RCX: 0x0802
> RDX: 0x1802 RSI: 0x8020 RDI: 0x0022
> CS: 10 BASE: 0x AR-BYTES: a09b EFER.LMA 1
> CR0: 0x80010031 CR3: 0x2000 CR4: 0x2020
> EFER: 0x0500
> Parking CPU 2 (Cell: "ioapic-demo")
> VT-d fault event reported by IOMMU 1:
>  Source Identifier (bus:dev.func): f0:1f.0
>  Fault Reason: 0x26 Fault Info: 460 Type 0
> 
> 
> After seeing this crash we added [ 0x1800/8 ... 0x18fe/8] = -1, in root-cell 
> PIO_BITMAP field, but my system get hangs after enabling jailhouse. 
> 
> Can anyone give me a pointer how to solve this issue, and other thing is why 
> i am not able to see any logs or crash report when we tried to run other demo 
> application(apic-demo,tiny-demo etc..)
> 
> please find the root-cell and non-rootcell(ioapic-demo) file in the 
> attachments.

The ioapic-demo is a special test you should not start with unless you
know what it does. Focus on apic-demo and maybe booting a second Linux.

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: [PATCH 0/4] ARM: Add support for emtrion's octa-core emCON-RZ/G1H and Renesas SCIFA

2018-02-07 Thread Jan Kiszka
On 2018-02-07 08:25, von Wiarda, Jan wrote:
> Thanks, that was all. Unfortunately while correcting indentations somehow a 
> typo occurred in commit 542e845 in file inmates/lib/arm/include/mach.h on 
> line 57. What do you want me to do, send a fix for the typo or a v2 for the 
> patch that introduced the typo.

Thanks for the note. I've fixed this up in your commit and pushed again.

diff --git a/inmates/lib/arm/include/mach.h b/inmates/lib/arm/include/mach.h
index 458218c9..a35df626 100644
--- a/inmates/lib/arm/include/mach.h
+++ b/inmates/lib/arm/include/mach.h
@@ -54,7 +54,7 @@
 #elif defined(CONFIG_MACH_BANANAPI)
 #define CON_TYPE   "8250"
 #define CON_BASE   0x01c29c00
-#define CON_DIVIDER0x0da
+#define CON_DIVIDER0x0d
 
 #define CON_CLOCK_REG  0x01c2006c
 #define CON_GATE_NR23

Jan

> 
> -Ursprüngliche Nachricht-
> Von: Jan Kiszka [mailto:jan.kis...@siemens.com] 
> Gesendet: Dienstag, 6. Februar 2018 21:47
> An: von Wiarda, Jan; JailhouseMailingListe
> Betreff: Re: [PATCH 0/4] ARM: Add support for emtrion's octa-core 
> emCON-RZ/G1H and Renesas SCIFA
> 
> On 2018-01-31 14:34, jan.vonwia...@emtrion.com wrote:
>> From: Jan von Wiarda 
>>
>> This patchset introduces support for emtrion's octa-core emCON-RZ/G1H 
>> and Renesas SCIFA serial interfaces.
>>
>> Jan von Wiarda (4):
>>   configs: Add support for emtrion's octa-core emCON-RZ/G1H
>>   inmates: Add inmate support for Renesas SCIFA serial communication
>> interface
>>   arm: Add hypervisor support for Renesas SCIFA serial communication
>> interface
>>   core: Add Renesas SCIFA as console type
> 
> Thanks, applied to next, but with patch 4 first to avoid breaking the build 
> in between.
> 
> Jan
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence 
> Center Embedded Linux
> 

-- 
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.


[siemens/jailhouse] 5e2853: inmates: Add inmate support for Renesas SCIFA seri...

2018-02-07 Thread GitHub
  Branch: refs/heads/next
  Home:   https://github.com/siemens/jailhouse
  Commit: 5e2853933d0ccb81d873c65f4c4f9fc1cc823216
  
https://github.com/siemens/jailhouse/commit/5e2853933d0ccb81d873c65f4c4f9fc1cc823216
  Author: Ruediger Fichter 
  Date:   2018-02-07 (Wed, 07 Feb 2018)

  Changed paths:
M inmates/lib/arm-common/Makefile.lib
M inmates/lib/arm-common/include/uart.h
M inmates/lib/arm-common/printk.c
A inmates/lib/arm-common/uart-scifa.c
M inmates/lib/arm/include/mach.h

  Log Message:
  ---
  inmates: Add inmate support for Renesas SCIFA serial communication interface

Renesas boards support different types of serial communication interfaces.
This patch adds inmate support for the SCIFA SCI.

Signed-off-by: Jan von Wiarda 
Signed-off-by: Ruediger Fichter 
[Jan: removed spurious change of Banana-Pi CON_DIVIDER]
Signed-off-by: Jan Kiszka 


  Commit: f990b20aeca5b7e3f15f6e5c6e5d3efffba64074
  
https://github.com/siemens/jailhouse/commit/f990b20aeca5b7e3f15f6e5c6e5d3efffba64074
  Author: Ruediger Fichter 
  Date:   2018-02-07 (Wed, 07 Feb 2018)

  Changed paths:
M hypervisor/arch/arm-common/Kbuild
M hypervisor/arch/arm-common/dbg-write.c
M hypervisor/arch/arm-common/include/asm/uart.h
A hypervisor/arch/arm-common/uart-scifa.c

  Log Message:
  ---
  arm: Add hypervisor support for Renesas SCIFA serial communication interface

This patch adds hypervisor support for the SCIFA SCI.

Signed-off-by: Jan von Wiarda 
Signed-off-by: Ruediger Fichter 
Signed-off-by: Jan Kiszka 


  Commit: fba3f89deff642b0b755522aaa718e4af46fa7d5
  
https://github.com/siemens/jailhouse/commit/fba3f89deff642b0b755522aaa718e4af46fa7d5
  Author: Jan von Wiarda 
  Date:   2018-02-07 (Wed, 07 Feb 2018)

  Changed paths:
M Documentation/debug-output.md
M Documentation/setup-on-emtrion-emcon-rz-boards.md

  Log Message:
  ---
  documentation: Update emCON-RZ/G debug and setup documentation files

-added the two new debug interfaces HSCIF and SCIFA from Renesas to the debug 
output documentation
-updated device specific defines in setup documentation of emcon-RZ/G

Signed-off-by: Jan von Wiarda 
Signed-off-by: Jan Kiszka 


  Commit: 1fa90014cadf371052bb3c80b4e341d8e4357d65
  
https://github.com/siemens/jailhouse/commit/1fa90014cadf371052bb3c80b4e341d8e4357d65
  Author: Jan von Wiarda 
  Date:   2018-02-07 (Wed, 07 Feb 2018)

  Changed paths:
M configs/arm/dts/inmate-emtrion-emconrzg1e.dts
M configs/arm/dts/inmate-emtrion-emconrzg1m.dts

  Log Message:
  ---
  configs: Device Tree Revision for Linux inmates on emCON-RZ/G1E and 
emCON-RZ/G1M

This patchset removes the warnings of the latest 4.15 device tree compiler.
In addition it includes the defines of missing header files directly in the
device tree source file.

Signed-off-by: Jan von Wiarda 
Signed-off-by: Ruediger Fichter 
Signed-off-by: Jan Kiszka 


Compare: 
https://github.com/siemens/jailhouse/compare/37710286c118...1fa90014cadf

-- 
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.