From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:50233) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwZzj-0000t6-2Y for qemu-devel@nongnu.org; Thu, 25 Aug 2011 09:29:20 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QwZzh-0007ER-RS for qemu-devel@nongnu.org; Thu, 25 Aug 2011 09:29:19 -0400 Received: from mail-fx0-f45.google.com ([209.85.161.45]:45617) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QwZzh-0007E4-Ll for qemu-devel@nongnu.org; Thu, 25 Aug 2011 09:29:17 -0400 Received: by fxbb27 with SMTP id b27so1968928fxb.4 for ; Thu, 25 Aug 2011 06:29:16 -0700 (PDT) From: Sasha Levin Content-Type: text/plain; charset="us-ascii" Date: Thu, 25 Aug 2011 16:29:14 +0300 Message-ID: <1314278954.3692.55.camel@lappy> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] Questions regarding ivshmem spec List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: cam Cc: David Evensky , Pekka Enberg , qemu-devel , kvm 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.