Thank you very much! It solves my problem. I have not looked at this project for a while. It is nice to migrated to CMAKE. Does you happen to know if the X86 VM connector can work in ARM? It would be good to have the communication between VM and native seL4 process.

Thanks again!

Best Regards -Daniel Wang

On Oct 4, 2018, at 2:36 PM, Mike Clark undefinedspace@gmail.com wrote:

I've been doing

# ../init-build.sh -DAARCH32=TRUE -DTk1Insecure=TRUE -DCAMKES_VM_APP=tk1_vm # ninja

If that doesn't work can you post logs?

On Thu, Oct 4, 2018 at 1:39 PM Daniel Wang <danielwang.ksu@gmail.com mailto:danielwang.ksu@gmail.com> wrote: Hi all,

It seems CAmkES-arm-vmm has been immigrated to cmake, How can I build it? I tried to build it by invoking:

# ../init-build.sh -DCAMKES_VM_APP=tk1_vm -DPLATFORM=tk1 # ninja

But it does not work.

Also, thank for the detailed CAmkES X86 documents. I’m wondering does the VM Connector and kernel modules work for ARM architecture, TK1 or TK1-SOM specifically?

Best Regards -Daniel Wang

---

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

Hi,

The x86 connectors don't currently work in the arm vmm unfortunately. The connectors that provide a virtual device to the guest OS require PCI virtualisation support to be added, and the connectors that create shared memory mappings into the guest physical address space also require implementation in the arm vmm. I believe we are about to start working on more consistent features between the two architectures and eventually have a single implementation rather than two.

Kent.

On Thu., 4 Oct. 2018, 21:06 Mike Clark, undefinedspace@gmail.com wrote:

That would be nice. I don't know if it works though.

Mike

On Thu, Oct 4, 2018, 3:05 PM Daniel Wang danielwang.ksu@gmail.com wrote:

...

Thank you very much! It solves my problem. I have not looked at this project for a while. It is nice to migrated to CMAKE. Does you happen to know if the X86 VM connector can work in ARM? It would be good to have the communication between VM and native seL4 process.

Thanks again!

Best Regards -Daniel Wang

On Oct 4, 2018, at 2:36 PM, Mike Clark undefinedspace@gmail.com wrote:

I've been doing

# ../init-build.sh -DAARCH32=TRUE -DTk1Insecure=TRUE -DCAMKES_VM_APP=tk1_vm # ninja

If that doesn't work can you post logs?

On Thu, Oct 4, 2018 at 1:39 PM Daniel Wang danielwang.ksu@gmail.com wrote:

...

Hi all,

It seems CAmkES-arm-vmm has been immigrated to cmake, How can I build it? I tried to build it by invoking:

# ../init-build.sh -DCAMKES_VM_APP=tk1_vm -DPLATFORM=tk1 # ninja

But it does not work.

Also, thank for the detailed CAmkES X86 documents. I’m wondering does the VM Connector and kernel modules work for ARM architecture, TK1 or TK1-SOM specifically?

Best Regards -Daniel Wang

---

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

---

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

No problem. For shared memory, if you use a regular dataport connector, there should be a way to register it as a device with a physical address. Then in Linux you could access the address using the /dev/mem file. As for signalling between components and the vm, I am not sure if there is already functions for this or not, but you may be able to inject notifications from other components into the vm guest via the vgic. And use hypercalls to go in the opposite direction. RPC is a bit more difficult because performing rpc from the VM outwards usually ends up with "stalling" the cpu while waiting for a response. But you can implement almost equivalent functionality by using shared memory and signalling.

Kent.

On Thu., 4 Oct. 2018, 21:18 Daniel Wang, danielwang.ksu@gmail.com wrote:

Thank you so much for your response! Is there any way for now that allows VM and native process communicate? Best Regards -Daniel Wang

On Oct 4, 2018, at 3:16 PM, Kent Mcleod kent.mcleod72@gmail.com wrote:

Hi,

The x86 connectors don't currently work in the arm vmm unfortunately. The connectors that provide a virtual device to the guest OS require PCI virtualisation support to be added, and the connectors that create shared memory mappings into the guest physical address space also require implementation in the arm vmm. I believe we are about to start working on more consistent features between the two architectures and eventually have a single implementation rather than two.

Kent.

On Thu., 4 Oct. 2018, 21:06 Mike Clark, undefinedspace@gmail.com wrote:

...

That would be nice. I don't know if it works though.

Mike

On Thu, Oct 4, 2018, 3:05 PM Daniel Wang danielwang.ksu@gmail.com wrote:

...

Thank you very much! It solves my problem. I have not looked at this project for a while. It is nice to migrated to CMAKE. Does you happen to know if the X86 VM connector can work in ARM? It would be good to have the communication between VM and native seL4 process.

Thanks again!

Best Regards -Daniel Wang

On Oct 4, 2018, at 2:36 PM, Mike Clark undefinedspace@gmail.com wrote:

I've been doing

# ../init-build.sh -DAARCH32=TRUE -DTk1Insecure=TRUE -DCAMKES_VM_APP=tk1_vm # ninja

If that doesn't work can you post logs?

On Thu, Oct 4, 2018 at 1:39 PM Daniel Wang danielwang.ksu@gmail.com wrote:

...

Hi all,

It seems CAmkES-arm-vmm has been immigrated to cmake, How can I build it? I tried to build it by invoking:

# ../init-build.sh -DCAMKES_VM_APP=tk1_vm -DPLATFORM=tk1 # ninja

But it does not work.

Also, thank for the detailed CAmkES X86 documents. I’m wondering does the VM Connector and kernel modules work for ARM architecture, TK1 or TK1-SOM specifically?

Best Regards -Daniel Wang

---

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

---

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