Hi,
at a first look the configuration looks ok for me.
Il giorno giovedì 12 aprile 2018 19:49:09 UTC+2, Giovani Gracioli ha scritto:
> Hello,
>
> Thank you for the answers.
>
> My comments are below.
>
> 1) The root config is defined as follows (copied only the relevant parts):
>
> .platform_i
El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió:
> On 2018-04-12 15:15, iallende wrote:
> > It still does not work. I have the following:
> >
> > root@xilinx-zcu102-2017_4:~# modprobe jailhouse
> > [ 20.762034] jailhouse: loading out-of-tree module taints kernel.
> > root@x
Document jailhouse in general, jailhouse enable and parts of jailhouse
cell
user can enter
man jailhouse cell
or
man jailhouse-cell
No install procedure is yet provided
Signed-off-by: Francois-Frederic Ozog
---
man/man8/jailhouse-cell.8 | 129
On 2018-04-16 14:21, iallende wrote:
> El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió:
>> On 2018-04-12 15:15, iallende wrote:
>>> It still does not work. I have the following:
>>>
>>> root@xilinx-zcu102-2017_4:~# modprobe jailhouse
>>> [ 20.762034] jailhouse: loading out-o
Hi,
On 04/16/2018 02:21 PM, iallende wrote:
> El viernes, 13 de abril de 2018, 9:14:46 (UTC+2), J. Kiszka escribió:
>> On 2018-04-12 15:15, iallende wrote:
>>> It still does not work. I have the following:
>>>
>>> root@xilinx-zcu102-2017_4:~# modprobe jailhouse
>>> [ 20.762034] jailhouse: loadi
On 2018-04-16 14:28, f...@ozog.com wrote:
> Document jailhouse in general, jailhouse enable and parts of jailhouse cell
> user can enter
> man jailhouse cell
> or
> man jailhouse-cell
Cool, will have a look ASAP.
>
> No install procedure is yet provided
Yeah, that's likely easy to add later on.
On 2018-04-16 14:47, Jan Kiszka wrote:
> On 2018-04-16 14:28, f...@ozog.com wrote:
>> Document jailhouse in general, jailhouse enable and parts of jailhouse cell
>> user can enter
>> man jailhouse cell
>> or
>> man jailhouse-cell
>
> Cool, will have a look ASAP.
>
Unfortunately, your mail client
Yes, this is strange and it is not happening.
I added some prints in the pci_cell_init function (hypervisor/pci.c) and
ivhsmem_init function (hypervisor/arm-common/ivhsmem.c). When I enable the root
cell, I got the following:
pci_cell_init - cell ZynqMP-ZCU102, id = 0, num_pci_devices 2
pci_cel
I found the error. It was missing a config parameter in the non-root cell:
.num_pci_devices = 2 (in the .cell struct)
After inserting this, I got the correct output:
Shared memory connection established: "gic-demo-ivshmem" <--> "ZynqMP-ZCU102"
Thanks for the help.
> Yes, this is strange and it
From: Francois-Frederic Ozog
Document jailhouse in general, jailhouse enable and parts of jailhouse cell
user can enter
man jailhouse cell
or
man jailhouse-cell
No install procedure is yet provided
Signed-off-by: Francois-Frederic Ozog
---
man/man8/jailhouse-cell.8 | 129 +++
inmates cannot use X86_FEATURE_VMX from regular cpuid
as vcpu maks the bit explicitely on non-root cells.
use cpuid leaf 0 to detect AuthenticAMD and change to VMMCALL
Signed-off-by: Francois-Frederic Ozog
---
inmates/lib/x86/hypercall.c | 8
1 file changed, 4 insertions(+), 4 deletion
On 04/16/2018 05:29 PM, Francois-Frederic Ozog wrote:
> inmates cannot use X86_FEATURE_VMX from regular cpuid
> as vcpu maks the bit explicitely on non-root cells.
>
> use cpuid leaf 0 to detect AuthenticAMD and change to VMMCALL
>
> Signed-off-by: Francois-Frederic Ozog
> ---
> inmates/lib/x86
On 2018-04-16 17:41, Ralf Ramsauer wrote:
> On 04/16/2018 05:29 PM, Francois-Frederic Ozog wrote:
>> inmates cannot use X86_FEATURE_VMX from regular cpuid
>> as vcpu maks the bit explicitely on non-root cells.
>>
>> use cpuid leaf 0 to detect AuthenticAMD and change to VMMCALL
>>
>> Signed-off-by:
From: Jan Kiszka
They can switch on build options we don't want or support. This allows
to drop explicit gcov and OCR disabling. In some cases, this condition
was actually already fulfilled.
Signed-off-by: Jan Kiszka
---
Kbuild | 10 +-
configs/Makefile
Hello guys,
Now I am trying to send an interrupt from the root-cell (Linux) to the
bare-metal cell. The other way around, from the bare-metal to Linux, is
working. Whenever I start the bare-metal cell, I can see that an interrupt has
arrived by checking the /proc/interrupts (number 38 is the ui
This switches to the Isar version replacing multistrap with debootstrap.
As the isar-base-image no longer sets the host name, we need to do this
now.
Signed-off-by: Jan Kiszka
---
kas.yml| 2 +-
recipes-core/customizations/files/postinst | 2 ++
2 files change
On 2018-04-16 17:58, Giovani Gracioli wrote:
> Hello guys,
>
> Now I am trying to send an interrupt from the root-cell (Linux) to the
> bare-metal cell. The other way around, from the bare-metal to Linux, is
> working. Whenever I start the bare-metal cell, I can see that an interrupt
> has arri
From: Francois-Frederic Ozog
inmates cannot use X86_FEATURE_VMX from regular cpuid
as vcpu maks the bit explicitely on non-root cells.
use cpuid leaf 0 to detect AuthenticAMD and change to VMMCALL
use string compare for clearer code
Signed-off-by: Francois-Frederic Ozog
---
inmates/lib/x86/h
On 2018-04-16 19:46, Francois-Frederic Ozog wrote:
> From: Francois-Frederic Ozog
>
> inmates cannot use X86_FEATURE_VMX from regular cpuid
> as vcpu maks the bit explicitely on non-root cells.
>
> use cpuid leaf 0 to detect AuthenticAMD and change to VMMCALL
>
> use string compare for clearer
I added .vpci_irq_base = 136-32 to the bare-metal cell config (.cell) and now I
can see the interrupts generated by uio_send through the output of cat
/proc/interrupts:
CPU0 CPU1 CPU2
38: 38 0 0 GICv2 136 Edge uio_ivshmem,
uio_ivshmem
it's ok with me. compilers are so odd sometimes..
I guess we can keep the patch under wraps until I validate on the following
AMD https://www.packet.net/bare-metal/servers/compute
FF
On 16 April 2018 at 20:28, Jan Kiszka wrote:
> On 2018-04-16 19:46, Francois-Frederic Ozog wrote:
> > From: Fran
On 2018-04-16 20:35, Giovani Gracioli wrote:
> I added .vpci_irq_base = 136-32 to the bare-metal cell config (.cell) and now
> I can see the interrupts generated by uio_send through the output of cat
> /proc/interrupts:
>
>CPU0 CPU1 CPU2
> 38: 38 0
On 2018-04-16 20:28, Jan Kiszka wrote:
> On 2018-04-16 19:46, Francois-Frederic Ozog wrote:
>> From: Francois-Frederic Ozog
>>
>> inmates cannot use X86_FEATURE_VMX from regular cpuid
>> as vcpu maks the bit explicitely on non-root cells.
>>
>> use cpuid leaf 0 to detect AuthenticAMD and change to
Branch: refs/heads/next
Home: https://github.com/siemens/jailhouse
Commit: 574e21fc9e3bd545ec76ed3c58d4aa894f72733f
https://github.com/siemens/jailhouse/commit/574e21fc9e3bd545ec76ed3c58d4aa894f72733f
Author: Francois-Frederic Ozog
Date: 2018-04-16 (Mon, 16 Apr 2018)
Change
I instrumented the code with several prints.
When I start the bare-metal cell, I can see that an interrupt from CPU 3 is
issued and handled by CPU 0:
Started cell "gic-demo-ivshmem"
ivshmem_register_mmio() mmio->address = 8, mmio->is_write = 0, current cpu = 3
ivshmem_register_mmio() mmio->addre
25 matches
Mail list logo