From: Cam Macdonell <cam@cs.ualberta.ca>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: David Evensky <evensky@dancer.ca.sandia.gov>,
Pekka Enberg <penberg@kernel.org>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: Questions regarding ivshmem spec
Date: Mon, 29 Aug 2011 12:15:37 -0600 [thread overview]
Message-ID: <CAKjmth+S8gMbLd+4a9qoraRayeWq5jhAJEy2xffu+n2ftj+vqw@mail.gmail.com> (raw)
In-Reply-To: <1314631535.29761.28.camel@sasha>
On Mon, Aug 29, 2011 at 9:25 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
> On Thu, 2011-08-25 at 16:29 +0300, Sasha Levin wrote:
>> Hello,
>>
>> I am looking to implement an ivshmem device for KVM tools, the purpose
>> is to provide same functionality as QEMU and interoperability with QEMU.
>
> [snip]
>
>> 1. File handles and guest IDs are passed between the server and the
>> peers using sockets, is the protocol itself documented anywhere? I would
>> like to be able to work alongside QEMU servers/peers.
>
> I'm still wondering if someone could do a quick sketch of the
> client-server protocol or possibly point me to something that documents
> it?
Hi Sasha,
I have something like that. I'll be in touch when I find it.
Cam
>
> --
>
> Sasha.
>
>
WARNING: multiple messages have this Message-ID (diff)
From: Cam Macdonell <cam@cs.ualberta.ca>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: David Evensky <evensky@dancer.ca.sandia.gov>,
Pekka Enberg <penberg@kernel.org>,
qemu-devel <qemu-devel@nongnu.org>, kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Questions regarding ivshmem spec
Date: Mon, 29 Aug 2011 12:15:37 -0600 [thread overview]
Message-ID: <CAKjmth+S8gMbLd+4a9qoraRayeWq5jhAJEy2xffu+n2ftj+vqw@mail.gmail.com> (raw)
In-Reply-To: <1314631535.29761.28.camel@sasha>
On Mon, Aug 29, 2011 at 9:25 AM, Sasha Levin <levinsasha928@gmail.com> wrote:
> On Thu, 2011-08-25 at 16:29 +0300, Sasha Levin wrote:
>> Hello,
>>
>> I am looking to implement an ivshmem device for KVM tools, the purpose
>> is to provide same functionality as QEMU and interoperability with QEMU.
>
> [snip]
>
>> 1. File handles and guest IDs are passed between the server and the
>> peers using sockets, is the protocol itself documented anywhere? I would
>> like to be able to work alongside QEMU servers/peers.
>
> I'm still wondering if someone could do a quick sketch of the
> client-server protocol or possibly point me to something that documents
> it?
Hi Sasha,
I have something like that. I'll be in touch when I find it.
Cam
>
> --
>
> Sasha.
>
>
next prev parent reply other threads:[~2011-08-29 18:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 13:29 Questions regarding ivshmem spec Sasha Levin
2011-08-25 13:29 ` [Qemu-devel] " Sasha Levin
2011-08-25 14:00 ` Avi Kivity
2011-08-25 14:00 ` Avi Kivity
2011-08-25 14:39 ` Sasha Levin
2011-08-25 14:39 ` Sasha Levin
2011-08-25 14:40 ` Avi Kivity
2011-08-25 14:40 ` Avi Kivity
2011-08-25 14:42 ` Sasha Levin
2011-08-25 14:42 ` [Qemu-devel] " Sasha Levin
2011-08-29 15:25 ` Sasha Levin
2011-08-29 15:25 ` [Qemu-devel] " Sasha Levin
2011-08-29 18:15 ` Cam Macdonell [this message]
2011-08-29 18:15 ` Cam Macdonell
2011-08-30 17:37 ` Cam Macdonell
2011-08-30 17:37 ` [Qemu-devel] " Cam Macdonell
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=CAKjmth+S8gMbLd+4a9qoraRayeWq5jhAJEy2xffu+n2ftj+vqw@mail.gmail.com \
--to=cam@cs.ualberta.ca \
--cc=evensky@dancer.ca.sandia.gov \
--cc=kvm@vger.kernel.org \
--cc=levinsasha928@gmail.com \
--cc=penberg@kernel.org \
--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 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.