From: Avi Kivity <avi@redhat.com>
To: Alexander Graf <agraf@suse.de>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
KVM General <kvm@vger.kernel.org>,
Jan Kiszka <jan.kiszka@siemens.com>,
"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>,
Luiz Capitulino <lcapitulino@redhat.com>,
Gerd Hoffmann <kraxel@redhat.com>, Adam Litke <agl@us.ibm.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Cam Macdonell <cam@cs.ualberta.ca>
Subject: [Qemu-devel] Re: Ideas wiki for GSoC 2010
Date: Thu, 11 Mar 2010 13:58:21 +0200 [thread overview]
Message-ID: <4B98DADD.9060600@redhat.com> (raw)
In-Reply-To: <AAC0E65B-073A-48C3-BB5A-A0C2838FC7D6@suse.de>
On 03/11/2010 01:56 PM, Alexander Graf wrote:
> On 11.03.2010, at 12:54, Avi Kivity wrote:
>
>
>> On 03/11/2010 01:25 PM, Alexander Graf wrote:
>>
>>> The list is also still missing a lot of potential mentors for the listed ideas. Let me propose some here :)
>>>
>>> == Shared memory transport between guest(s) and host ==
>>>
>>> Sounds like Avi would be a good fit. I'm pretty unknowledgeable when it comes to shm.
>>>
>>>
>> Not sure what this is.
>>
> Cam's shared memory device.
>
That's plain shared memory among guests (though the host could also
participate). "transport" evokes something like virtio rings.
I could mentor it, though I prefer something in kvm, and it looks close
to completion.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-03-11 11:58 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 21:30 [Qemu-devel] Ideas wiki for GSoC 2010 Luiz Capitulino
2010-03-11 7:55 ` [Qemu-devel] " Avi Kivity
2010-03-11 9:43 ` Paolo Bonzini
2010-03-11 11:25 ` Alexander Graf
2010-03-11 11:54 ` Avi Kivity
2010-03-11 11:56 ` Alexander Graf
2010-03-11 11:58 ` Avi Kivity [this message]
2010-03-11 12:03 ` Alexander Graf
2010-03-11 12:15 ` Avi Kivity
2010-03-12 10:49 ` [Qemu-devel] Re: [Android-virt] " Christoffer Dall
2010-03-12 12:32 ` Luiz Capitulino
2010-03-11 19:06 ` [Qemu-devel] " Cam Macdonell
2010-03-11 12:09 ` Paolo Bonzini
2010-03-11 13:19 ` Luiz Capitulino
2010-03-13 3:13 ` Edgar E. Iglesias
2010-03-11 13:16 ` Luiz Capitulino
2010-03-12 10:47 ` Jes Sorensen
2010-03-11 12:59 ` Luiz Capitulino
2010-03-11 13:00 ` Alexander Graf
2010-03-11 13:21 ` Luiz Capitulino
2010-03-11 22:59 ` Jamie Lokier
2010-03-12 9:48 ` Paolo Bonzini
2010-03-12 9:59 ` Gleb Natapov
2010-03-11 12:26 ` Avi Kivity
2010-03-11 13:09 ` [Qemu-devel] " Lucas Meneghel Rodrigues
2010-03-12 15:11 ` Adam Litke
2010-03-12 15:22 ` Luiz Capitulino
2010-03-12 15:38 ` Adam Litke
2010-03-12 15:56 ` Luiz Capitulino
2010-03-12 16:36 ` Anthony Liguori
2010-03-12 17:35 ` Luiz Capitulino
2010-03-15 12:25 ` Avi Kivity
2010-03-15 12:38 ` Joerg Roedel
2010-03-15 12:42 ` Avi Kivity
2010-03-15 13:14 ` Anthony Liguori
2010-03-15 15:59 ` Joerg Roedel
2010-03-15 12:53 ` Muli Ben-Yehuda
2010-03-15 13:03 ` Joerg Roedel
2010-03-15 13:11 ` Avi Kivity
2010-03-15 13:23 ` Anthony Liguori
2010-03-15 15:06 ` Avi Kivity
2010-03-16 1:21 ` Anthony Liguori
2010-03-16 5:50 ` Avi Kivity
2010-03-15 13:24 ` Joerg Roedel
2010-03-15 13:55 ` Anthony Liguori
2010-03-15 14:18 ` Muli Ben-Yehuda
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=4B98DADD.9060600@redhat.com \
--to=avi@redhat.com \
--cc=agl@us.ibm.com \
--cc=agraf@suse.de \
--cc=aliguori@us.ibm.com \
--cc=cam@cs.ualberta.ca \
--cc=jan.kiszka@siemens.com \
--cc=kraxel@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).