Re: Inmate boot order question

Hi, Thanks for the info! The inmate is not running Linux, but a custom RTOS. We'll have to investigate the impact and possibilities on our side and come back with more info. Best Regards, Constantin On Mon, Dec 3, 2018 at 8:56 PM Jan Kiszka wrote: > On 03.12.18 17:39, Constantin Petra wr

Inmate boot order question

Hi, While using Jailhouse on Xeon (Inteld1521), having configured, for example, the inmate cell for cores 2&3, we could see that sometimes core 3 starts first, e.g: ... CPU 3 received SIPI, vector 100 CPU 2 received SIPI, vector 100 ... Looking into the code there is apparently no restriction

Re: Running ivshmem-demo in Jetson TK1.

Hi, I'm resending the patch(es) that were shared by Jonas a while ago. Best Regards, Constantin On Thu, Dec 7, 2017 at 10:08 PM, Henning Schild wrote: > Hi Claudio, > > Am Thu, 7 Dec 2017 17:29:45 +0100 > schrieb Claudio Scordino : > > > Hi

Re: ZCU102 environment questions

rote: > On 2017-10-10 08:38, Constantin Petra wrote: > > Hi, > > > > Just wanted to ask a few questions related to ZCU102 (Xilinx > Ultrascale+) environment you are using. > > > > We are having a hard time building the kernel from a different source &g

ZCU102 environment questions

, Constantin Petra -- 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: IVSHMEM future

Hi, Yes, thank you, this makes the current situation more clear. We'll probably try to get around option A for a POC - and keep an eye on the development of facts, see what would suit us on long term. Best Regards, Constantin -- You received this message because you are subscribed to the

IVSHMEM future

Hi, I was finally able to set up an IVSHMEM connection on Ultrascale+ (basic, using JAILHOUSE_SHMEM_PROTO_UNDEFINED, just interrupts working and access to shared memory area between host/guest) so I have a better perspective now. I am curious about the future development of IVSHMEM, the thread

Re: questions related to IVSHMEM/uio_ivshmem

Hi, I can now confirm that the patch 87fbf1f works and interrupts are received correctly, /dev/uiox is accessible and works as expected. Without it, I got a: "FATAL: forbidden access (exception class 0x24)" but I don't remember if this was triggered by Jailhouse or Linux. Best Regards,

Re: questions related to IVSHMEM/uio_ivshmem

jailhouse-next, is that the commit 87fbf1f / May 17th "? Best Regards, Constantin On Fri, Sep 1, 2017 at 4:21 PM, Henning Schild <henning.sch...@siemens.com> wrote: > Am Fri, 1 Sep 2017 05:36:31 -0700 > schrieb Constantin Petra <constantin.pe...@gmail.com>: > > > Hi, > >

questions related to IVSHMEM/uio_ivshmem

Hi, I have a question related to this above driver implementation, in an Ultrascale+ environment. This was taken from https://github.com/henning-schild/ivshmem-guest-code/blob/master/kernel_module/uio/uio_ivshmem.c, in an attempt to set up IVSHMEM connection (not ivshmem-net) with a different

Re: Running ivshmem-demo in Jetson TK1.

> efforts, getting a first working patch into a mergeable form is another > story. > > If there are legal reasons to not publish code on the list i suggest > you exchange patches between each other. But of cause i would like to > see contributions eventually ;). > > regards, >

Re: Running ivshmem-demo in Jetson TK1.

Hi, Sorry to pick this up after this time, but I would be interested in the pci.c modifications related to ARM for inmates (using MMIO instead of PIO). Was there a follow-up to the discussions above?(checked out the discussion archives but I can't find any). I would like to avoid re-inventing

Re: ZCU102 - starting a 32 bit inmate

g). Any idea on this? Maybe there are more things to handle? RMR_EL2 is maybe not implemented and I can't find information on it (accessing it resutls in a synchronous abort directly). Best Regards, Constantin On Mon, May 8, 2017 at 11:17 AM, Jan Kiszka <jan.kis...@siemens.com> wrote: >

ZCU102 - starting a 32 bit inmate

Hi, What would be the choice for starting a 32-bit OS (EL1)? Starting a 64-bit OS and switching at runtime to 32-bit is not possible AFAIK, the transition should be from EL2, using "eret" instruction after setting HCR_EL2.RW and setting up SPSR_EL2 with 32-bit mode (xilinx uboot seems to

Re: [PATCH v1 0/8] support arbitrary inmate entry points on ARM

Tested-by: Constantin Petra onstantin.pe...@gmail.com> On Thu, May 4, 2017 at 6:07 PM, Ralf Ramsauer < ralf.ramsa...@oth-regensburg.de> wrote: > Hi, > > On 05/04/2017 05:01 PM, Constantin Petra wrote: > > Hi again, > > > > I was able to run the uart-demo on 1

Re: [PATCH v1 0/8] support arbitrary inmate entry points on ARM

: > Hi, > > yes, there is quite a bunch of more patches in my local queue... :) > > Let me push those ARM Entry Point patches to some repo: > https://github.com/lfd/jailhouse/tree/arm-entry > > Rebased to latest next. If you successfully tested them, just drop a > Tested-By. > &

Re: [PATCH v1 0/8] support arbitrary inmate entry points on ARM

Hi, We're really interested in these patches, we want to use a different start address for a 1:1 mapping of a binary, and stomped into the fact that we couldn't get it to start from the needed address (on ZCU102). Unfortunately it seems like I cannot get these patches from mail, is there any

Re: Jailhouse on Ultrascale+ (ZCU102)

t 11:19 AM, Constantin Petra < constantin.pe...@gmail.com> wrote: > Hi, > > Sure, I have added the archive containing the image files and jailhouse > build here (the archive contains the /tftpboot folder directly) > https://drive.google.com/file/d/0B2bhbcx8eg-caTBNdnZ4cWhJcW

Re: Jailhouse on Ultrascale+ (ZCU102)

; > On 19 April 2017 at 05:37, Jan Kiszka <jan.kis...@web.de> wrote: > > >> On 2017-04-19 05:48, Constantin Petra wrote: > > >>> So from some reason, under QEMU something is not in place, but what > can > > >>> that be? It would be convenient from o

Re: Jailhouse on Ultrascale+ (ZCU102)

running 3 Best Regards, Constantin On Tue, Apr 18, 2017 at 1:32 PM, Constantin Petra < constantin.pe...@gmail.com> wrote: > Hi, > > Yes, that's correct, I'm trying to run the whole stack in QEMU, not > hardware. > > Best Regards, > Constantin > > On Tue, Apr

Re: Jailhouse on Ultrascale+ (ZCU102)

Hi, Yes, that's correct, I'm trying to run the whole stack in QEMU, not hardware. Best Regards, Constantin On Tue, Apr 18, 2017 at 12:52 PM, Jan Kiszka wrote: > On 2017-04-18 10:22, constantin.pe...@gmail.com wrote: > > Hi, > > > > I have made the changes to pci.c, but QEMU

Re: Jailhouse on Ultrascale+ (ZCU102)

Hello, I have tried a kernel 4.10 from torvalds/linux branch with applied patches, however something is not in place. When running petalinux-build or petalinux-config, I get: make: Entering directory

Re: Jailhouse on Ultrascale+ (ZCU102)

On Tuesday, April 11, 2017 at 6:35:55 PM UTC+3, Constantin Petra wrote: > Thanks Jan, > > > I'll check it out! > > > Constantin > > > On Tue, Apr 11, 2017 at 4:39 PM, Jan Kiszka <jan.kis...@siemens.com> wrote: > On 2017-04-11 15:19, cons

Jailhouse on Ultrascale+ (ZCU102)

Hi, Is it possible to run Jailhouse in QEMU for ZCU102 (Using Petalinux 2016.4)? There is apparently support for configuration and applications, but QEMU just hangs when calling "jailhouse enable jailhouse/configs/zynqmp-zcu102.cell" In "zynqmp-zcu102.c" it is mentioned: "Reservation via device