All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@web.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: "Marc-André Lureau" <marcandre.lureau@gmail.com>,
	Jailhouse <jailhouse-dev@googlegroups.com>,
	"Wei Wang" <wei.w.wang@intel.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] Towards an ivshmem 2.0?
Date: Mon, 30 Jan 2017 09:05:40 +0100	[thread overview]
Message-ID: <fb9b35ff-0676-6f79-697d-2c5b54aa9bd9@web.de> (raw)
In-Reply-To: <87efzlvuup.fsf@dusky.pond.sub.org>

On 2017-01-30 09:02, Markus Armbruster wrote:
> Jan Kiszka <jan.kiszka@web.de> writes:
> 
>> On 2017-01-29 15:00, Marc-André Lureau wrote:
>>> Hi
>>>
>>> On Sun, Jan 29, 2017 at 12:44 PM Jan Kiszka <jan.kiszka@web.de
>>> <mailto:jan.kiszka@web.de>> wrote:
>>>
>>>     >> Of course, I'm careful with investing much time into expanding the
>>>     >> existing, for Jailhouse possibly sufficient design if there no real
>>>     >> interest in continuing the ivshmem support in QEMU - because of
>>>     >> vhost-pci or other reasons. But if that interest exists, it would be
>>>     >> beneficial for us to have QEMU supporting a compatible version
>>>     and using
>>>     >> the same guest drivers. Then I would start looking into concrete
>>>     patches
>>>     >> for it as well.
>>>     >
>>>     > Interest is difficult for me to gauge, not least because alternatives
>>>     > are still being worked on.
>>>
>>>     I'm considering to suggest this as GSoC project now.
>>>
>>>
>>> It's better for a student and for the community if the work get accepted
>>> in the end.
> 
> Yes.
> 
>>> So, I think that could be an intersting GSoC (implementing your ivshmem
>>> 2 proposal). However, if the qemu community isn't ready to accept a new
>>> ivshmem, and would rather have vhost-pci based solution, I would suggest
>>> a different project (hopefully Wei Wang can help define it and mentor):
>>> work on a vhost-pci using dedicated shared PCI BARs (and kernel support
>>> to avoid extra copy - if I understand the extra copy situation correctly).
>>
>> It's still open if vhost-pci can replace ivshmem (not to speak of being
>> desirable for Jailhouse - I'm still studying). In that light, having
>> both implementations available to do real comparisons is valuable IMHO.
> 
> Yes, but is it appropriate for GSoC?
> 
>> That said, we will play with open cards, explain the student the
>> situation and let her/him decide knowingly.
> 
> Both the student and the QEMU project need to consider the situation
> carefully.
> 
>> Jan
>>
>> PS: We have a mixed history /wrt actually merging student projects.
> 
> Yes, but having screwed up is no license to screw up some more :)
> 

After having received multiple feedbacks in this direction, I will drop
that proposal from our list. So, don't worry. ;)

Jan

  reply	other threads:[~2017-01-30  8:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-16  8:36 [Qemu-devel] Towards an ivshmem 2.0? Jan Kiszka
2017-01-16 12:41 ` Marc-André Lureau
2017-01-16 13:10   ` Jan Kiszka
2017-01-17  9:13     ` Wang, Wei W
2017-01-17  9:46       ` Jan Kiszka
2017-01-20 11:54         ` Wang, Wei W
2017-01-20 16:37           ` Jan Kiszka
2017-01-23  3:49             ` Wang, Wei W
2017-01-23 10:14               ` Måns Rullgård
2017-01-17  9:59     ` Stefan Hajnoczi
2017-01-17 10:32       ` Jan Kiszka
2017-01-29 11:56       ` msuchanek
2017-01-30 11:25         ` Stefan Hajnoczi
2017-01-16 14:18 ` Stefan Hajnoczi
2017-01-16 14:34   ` Jan Kiszka
2017-01-17 10:00     ` Stefan Hajnoczi
2017-01-23 14:19 ` Markus Armbruster
2017-01-25  9:18   ` Jan Kiszka
2017-01-27 19:36     ` Markus Armbruster
2017-01-29  8:43       ` Jan Kiszka
2017-01-29 14:00         ` Marc-André Lureau
2017-01-29 14:14           ` Jan Kiszka
2017-01-30  8:02             ` Markus Armbruster
2017-01-30  8:05               ` Jan Kiszka [this message]
2017-01-31  2:51             ` Wang, Wei W
2017-01-30  8:00         ` Markus Armbruster
2017-01-30  8:14           ` Jan Kiszka
2017-01-30 12:19             ` Markus Armbruster
2017-01-30 15:57               ` Jan Kiszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb9b35ff-0676-6f79-697d-2c5b54aa9bd9@web.de \
    --to=jan.kiszka@web.de \
    --cc=armbru@redhat.com \
    --cc=jailhouse-dev@googlegroups.com \
    --cc=marcandre.lureau@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wei.w.wang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.