Displaying 7 results from an estimated 7 matches for "msg00581".
Did you mean:
msg00381
2014 Jun 13
2
[Qemu-devel] Why I advise against using ivshmem
..., it is
possible to develop a vhost-serial as well, and it is possible to only
use the RPC and develop arbitrary shared-memory based tools using this
API. It's just that no one has done it yet.
Also, vhost-user is documented! See here:
https://lists.gnu.org/archive/html/qemu-devel/2014-03/msg00581.html
The only part of ivshmem that vhost doesn't include is the n-way
inter-guest doorbell. This is the part that requires a server and uio
driver. vhost only supports host->guest and guest->host doorbells.
>> * it doesn't require hugetlbfs (which only enabled shared memor...
2014 Jun 13
2
[Qemu-devel] Why I advise against using ivshmem
..., it is
possible to develop a vhost-serial as well, and it is possible to only
use the RPC and develop arbitrary shared-memory based tools using this
API. It's just that no one has done it yet.
Also, vhost-user is documented! See here:
https://lists.gnu.org/archive/html/qemu-devel/2014-03/msg00581.html
The only part of ivshmem that vhost doesn't include is the n-way
inter-guest doorbell. This is the part that requires a server and uio
driver. vhost only supports host->guest and guest->host doorbells.
>> * it doesn't require hugetlbfs (which only enabled shared memor...
2014 Jun 13
0
[Qemu-devel] Why I advise against using ivshmem
...do agree that it is promising.
And of course some tests are here:
https://lists.gnu.org/archive/html/qemu-devel/2014-03/msg00584.html
for some of the bullets you are listing (not all yet).
> Also, vhost-user is documented! See here:
> https://lists.gnu.org/archive/html/qemu-devel/2014-03/msg00581.html
as I told you, we'll send a contribution with ivshmem's documentation.
> The only part of ivshmem that vhost doesn't include is the n-way
> inter-guest doorbell. This is the part that requires a server and uio
> driver. vhost only supports host->guest and guest->...
2014 Jun 13
3
[Qemu-devel] Why I advise against using ivshmem
Il 13/06/2014 15:41, Vincent JARDIN ha scritto:
>> Fine, however Red Hat would also need a way to test ivshmem code, with
>> proper quality assurance (that also benefits upstream, of course). With
>> ivshmem this is not possible without the out-of-tree packages.
>
> You did not reply to my question: how to get the list of things that
> are/will be disabled by Redhat?
I
2014 Jun 13
3
[Qemu-devel] Why I advise against using ivshmem
Il 13/06/2014 15:41, Vincent JARDIN ha scritto:
>> Fine, however Red Hat would also need a way to test ivshmem code, with
>> proper quality assurance (that also benefits upstream, of course). With
>> ivshmem this is not possible without the out-of-tree packages.
>
> You did not reply to my question: how to get the list of things that
> are/will be disabled by Redhat?
I
2014 Jun 13
5
[Qemu-devel] Why I advise against using ivshmem
Some dropped quoted text restored.
Vincent JARDIN <vincent.jardin at 6wind.com> writes:
> Markus,
>
> see inline (I am not on all mailing list, please, keep the cc list).
>
>> Sure! The reasons for my dislike range from practical to
>> philosophical.
>>
>> My practical concerns include:
>>
>> 1. ivshmem code needs work, but has no maintainer
2014 Jun 13
5
[Qemu-devel] Why I advise against using ivshmem
Some dropped quoted text restored.
Vincent JARDIN <vincent.jardin at 6wind.com> writes:
> Markus,
>
> see inline (I am not on all mailing list, please, keep the cc list).
>
>> Sure! The reasons for my dislike range from practical to
>> philosophical.
>>
>> My practical concerns include:
>>
>> 1. ivshmem code needs work, but has no maintainer