From: Sasha Levin <levinsasha928@gmail.com> To: cam <cam@cs.ualberta.ca> 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: Questions regarding ivshmem spec Date: Thu, 25 Aug 2011 16:29:14 +0300 [thread overview] Message-ID: <1314278954.3692.55.camel@lappy> (raw) 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. Going through the spec (I found here: https://gitorious.org/nahanni/guest-code/blobs/master/device_spec.txt ) and the code in QEMU I have gathered several questions, I'll be happy for some help with it. 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. 2. The spec describes DOORBELL as an array of DWORDs, when one guest wants to poke a different guest it would write something into the offset of the other guest in the DOORBELL array. Looking at the implementation in QEMU, DOORBELL is one DWORD, when writing to it the upper WORD is the guest id and the lower WORD is the value. What am I missing here? 3. There are 3 ways for guests to communicate between each other, and I'm assuming all guests using the same SHM block must use the same method. Is it safe to assume we'll always use ioeventfds as in the implementation now? Thanks! -- Sasha.
WARNING: multiple messages have this Message-ID (diff)
From: Sasha Levin <levinsasha928@gmail.com> To: cam <cam@cs.ualberta.ca> 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: [Qemu-devel] Questions regarding ivshmem spec Date: Thu, 25 Aug 2011 16:29:14 +0300 [thread overview] Message-ID: <1314278954.3692.55.camel@lappy> (raw) 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. Going through the spec (I found here: https://gitorious.org/nahanni/guest-code/blobs/master/device_spec.txt ) and the code in QEMU I have gathered several questions, I'll be happy for some help with it. 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. 2. The spec describes DOORBELL as an array of DWORDs, when one guest wants to poke a different guest it would write something into the offset of the other guest in the DOORBELL array. Looking at the implementation in QEMU, DOORBELL is one DWORD, when writing to it the upper WORD is the guest id and the lower WORD is the value. What am I missing here? 3. There are 3 ways for guests to communicate between each other, and I'm assuming all guests using the same SHM block must use the same method. Is it safe to assume we'll always use ioeventfds as in the implementation now? Thanks! -- Sasha.
next reply other threads:[~2011-08-25 13:29 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-25 13:29 Sasha Levin [this message] 2011-08-25 13:29 ` [Qemu-devel] Questions regarding ivshmem spec 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 2011-08-29 18:15 ` [Qemu-devel] " 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=1314278954.3692.55.camel@lappy \ --to=levinsasha928@gmail.com \ --cc=cam@cs.ualberta.ca \ --cc=evensky@dancer.ca.sandia.gov \ --cc=kvm@vger.kernel.org \ --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: linkBe 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.