On 2014-06-17 07:24, Paolo Bonzini wrote:
> Il 15/06/2014 08:20, Jan Kiszka ha scritto:
>>> > I think implementing Xen hypercalls in jailhouse for grant table and
>>> > event channels would actually make a lot of sense. The Xen
>>> > implementation is 2.5kLOC and I think it should be possible to c
Il 15/06/2014 08:20, Jan Kiszka ha scritto:
> I think implementing Xen hypercalls in jailhouse for grant table and
> event channels would actually make a lot of sense. The Xen
> implementation is 2.5kLOC and I think it should be possible to compact
> it noticeably, especially if you limit yourse
On 2014-06-13 10:45, Paolo Bonzini wrote:
> Il 13/06/2014 08:23, Jan Kiszka ha scritto:
That would preserve zero-copy capabilities (as long as you can work
against the shared mem directly, e.g. doing DMA from a physical NIC or
storage device into it) and keep the hypervisor out of th
Il 13/06/2014 08:23, Jan Kiszka ha scritto:
That would preserve zero-copy capabilities (as long as you can work
against the shared mem directly, e.g. doing DMA from a physical NIC or
storage device into it) and keep the hypervisor out of the loop.
>
> This seems ill thought out. How will you pr
On 2014-06-13 02:47, Rusty Russell wrote:
> Jan Kiszka writes:
>> On 2014-06-12 04:27, Rusty Russell wrote:
>>> Henning Schild writes:
>>> It was also never implemented, and remains a thought experiment.
>>> However, implementing it in lguest should be fairly easy.
>>
>> The reason why a trusted
Jan Kiszka writes:
> On 2014-06-12 04:27, Rusty Russell wrote:
>> Henning Schild writes:
>> It was also never implemented, and remains a thought experiment.
>> However, implementing it in lguest should be fairly easy.
>
> The reason why a trusted helper, i.e. additional logic in the
> hypervisor,
On 12/06/2014 09:44, Henning Schild wrote:
It may be used, but that doesn't mean it's maintained, or robust
>against abuse. My advice is to steer clear of it.
Could you elaborate on why you advice against it?
+1 elaborate please.
beside the DPDK source code, some other common use cases:
-
On Thu, 12 Jun 2014 08:48:04 +0200
Markus Armbruster wrote:
> Vincent JARDIN writes:
>
> > On 10/06/2014 18:48, Henning Schild wrote:> Hi,
> >> In a first prototype i implemented a ivshmem[2] device for the
> >> hypervisor. That way we can share memory between virtual machines.
> >> Ivshmem is
Vincent JARDIN writes:
> On 10/06/2014 18:48, Henning Schild wrote:> Hi,
>> In a first prototype i implemented a ivshmem[2] device for the
>> hypervisor. That way we can share memory between virtual machines.
>> Ivshmem is nice and simple but does not seem to be used anymore.
>> And it
>> does no
On 2014-06-12 04:27, Rusty Russell wrote:
> Henning Schild writes:
>> Hi,
>>
>> i am working on the jailhouse[1] project and am currently looking at
>> inter-VM communication. We want to connect guests directly with virtual
>> consoles based on shared memory. The code complexity in the hypervisor
Henning Schild writes:
> Hi,
>
> i am working on the jailhouse[1] project and am currently looking at
> inter-VM communication. We want to connect guests directly with virtual
> consoles based on shared memory. The code complexity in the hypervisor
> should be minimal, it should just make the shar
On 10/06/2014 18:48, Henning Schild wrote:> Hi,
> In a first prototype i implemented a ivshmem[2] device for the
> hypervisor. That way we can share memory between virtual machines.
> Ivshmem is nice and simple but does not seem to be used anymore.
> And it
> does not define higher level devices,
12 matches
Mail list logo
