Thank you, Ihor, That’s good to know. However, for now does the Vchan for ARM still functional? With help from Chris I was able to compile Vchan for both TK1 and EXYNOS5410. But I could not find /dev/vmm_manager virtual driver after boot. Does it need to have a Linux kernel module to mount and manage ioctl() syscall?

Best Regards -Daniel Wang

On Mar 13, 2018, at 8:44 PM, Ihor.Kuz@data61.csiro.au Ihor.Kuz@data61.csiro.au wrote:

We haven’t touched the vchan code in a while, and have pretty much stopped using vchan. We developed cross-vm dataports and events for x86[1], and will be starting work to complete those with cross-vm RPC and make that available on ARM too.

Of course that doesn’t help you right now, but just letting you know.

Ihor.

[1] https://wiki.sel4.systems/CAmkESVM#Cross_VM_Connectors

...

On 14 Mar 2018, at 12:43 am, Chris Guikema Chris.Guikema@dornerworks.com wrote:

Hey Daniel,

I had tried to setup the VM, and opened an issue on the camkes-arm-vm repo -https://github.com/SEL4PROJ/camkes-arm-vm/issues/3

The VChan is quite outdated. My issue should summarize what I had to do in order to get the system to compile.

Chris

From: Devel [mailto:devel-bounces@sel4.systems] On Behalf Of Daniel Wang Sent: Tuesday, March 13, 2018 3:49 AM To: devel@sel4.systems Subject: [seL4] Questions about Vchan

Hi all,

I’m trying to figure out how to use the Vchan library to setup communication between guest OS and native components. I got couple questions how you can give me some advices.

1. I saw the camkes_vchan_con_t structure in the helloworld components (camkes-arm-vm), but I could not find the implementation for vchan_con_new_connection(), vchan_con_rem_connection(), etc. Are those autogenerated by camkes? If so how it is generated?

static camkes_vchan_con_t con = { .connect = &vchan_con_new_connection, .disconnect = &vchan_con_rem_connection, .get_buf = &vchan_con_get_buf, .status = &vchan_con_status,

.alert = &vchan_con_ping, .wait = &vevent_wait, .poll = &vevent_poll,

.dest_dom_number = 0, .source_dom_number = 50, };

2. I tried to compile the Vchan support and demo helloworld components for odroid-xu. But the compile shows error due to the VM.h file (camkes-arm-vm/projects/vm/components/VM/src/cmks_vchan_vm.c:23) cannot be found. How can I generate the VM.h file?

Thanks a lot!

Best Regards -Daniel Wang

---

Devel mailing list Devel@sel4.systems https://sel4.systems/lists/listinfo/devel

I see. May I ask what is needed? I would like to spend some time on it. But I might need some guidance on setting up the communication between guest Linux and native component.I saw some code are there for allowing VM to add virq and registering functions. But I’m not sure how the sharemem is configured (I assume that is done by capdl). I’m not exactly sure what is need in the hardware-assisted virtualization environment.

Best Regards -Daniel Wang

On Mar 13, 2018, at 9:06 PM, Kent.Mcleod@data61.csiro.au wrote:

As far as I am aware, the arm support for Vchans was never finished.​ I tried to get it running once and I believe the issue was that it expected the same vmm_manager device that the x86 vmm provides, but this isn't implemented on the ARM vmm.

Kind regards,

Kent McLeod From: Devel devel-bounces@sel4.systems on behalf of Daniel Wang danielwang.ksu@gmail.com Sent: Wednesday, March 14, 2018 2:57 PM To: Kuz, Ihor (Data61, Kensington NSW) Cc: devel@sel4.systems Subject: Re: [seL4] Questions about Vchan

Thank you, Ihor, That’s good to know. However, for now does the Vchan for ARM still functional? With help from Chris I was able to compile Vchan for both TK1 and EXYNOS5410. But I could not find /dev/vmm_manager virtual driver after boot. Does it need to have a Linux kernel module to mount and manage ioctl() syscall?

Best Regards -Daniel Wang

...

On Mar 13, 2018, at 8:44 PM, <Ihor.Kuz@data61.csiro.au mailto:Ihor.Kuz@data61.csiro.au> <Ihor.Kuz@data61.csiro.au mailto:Ihor.Kuz@data61.csiro.au> wrote:

We haven’t touched the vchan code in a while, and have pretty much stopped using vchan. We developed cross-vm dataports and events for x86[1], and will be starting work to complete those with cross-vm RPC and make that available on ARM too.

Of course that doesn’t help you right now, but just letting you know.

Ihor.

[1] https://wiki.sel4.systems/CAmkESVM#Cross_VM_Connectors https://wiki.sel4.systems/CAmkESVM#Cross_VM_Connectors

...

On 14 Mar 2018, at 12:43 am, Chris Guikema <Chris.Guikema@dornerworks.com mailto:Chris.Guikema@dornerworks.com> wrote:

Hey Daniel,

I had tried to setup the VM, and opened an issue on the camkes-arm-vm repo -https://github.com/SEL4PROJ/camkes-arm-vm/issues/3 https://github.com/SEL4PROJ/camkes-arm-vm/issues/3

The VChan is quite outdated. My issue should summarize what I had to do in order to get the system to compile.

Chris

From: Devel [mailto:devel-bounces@sel4.systems mailto:devel-bounces@sel4.systems] On Behalf Of Daniel Wang Sent: Tuesday, March 13, 2018 3:49 AM To: devel@sel4.systems mailto:devel@sel4.systems Subject: [seL4] Questions about Vchan

Hi all,

I’m trying to figure out how to use the Vchan library to setup communication between guest OS and native components. I got couple questions how you can give me some advices.

1. I saw the camkes_vchan_con_t structure in the helloworld components (camkes-arm-vm), but I could not find the implementation for vchan_con_new_connection(), vchan_con_rem_connection(), etc. Are those autogenerated by camkes? If so how it is generated?

static camkes_vchan_con_t con = { .connect = &vchan_con_new_connection, .disconnect = &vchan_con_rem_connection, .get_buf = &vchan_con_get_buf, .status = &vchan_con_status,

.alert = &vchan_con_ping, .wait = &vevent_wait, .poll = &vevent_poll,

.dest_dom_number = 0, .source_dom_number = 50, };

2. I tried to compile the Vchan support and demo helloworld components for odroid-xu. But the compile shows error due to the VM.h file (camkes-arm-vm/projects/vm/components/VM/src/cmks_vchan_vm.c:23) cannot be found. How can I generate the VM.h file?

Thanks a lot!

Best Regards -Daniel Wang

---

Devel mailing list Devel@sel4.systems mailto:Devel@sel4.systems https://sel4.systems/lists/listinfo/devel