qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Pekka Enberg <penberg@kernel.org>, cam <cam@cs.ualberta.ca>,
	qemu-devel <qemu-devel@nongnu.org>,
	David Evensky <evensky@dancer.ca.sandia.gov>,
	kvm <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] Questions regarding ivshmem spec
Date: Thu, 25 Aug 2011 17:00:14 +0300	[thread overview]
Message-ID: <4E56556E.1080805@redhat.com> (raw)
In-Reply-To: <1314278954.3692.55.camel@lappy>

On 08/25/2011 04:29 PM, Sasha Levin wrote:
> 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?
>

The spec in qemu.git is accurate.  The intent is to use an ioeventfd 
bound into an irqfd so a write into the doorbell injects an interrupt 
directly into the other guest, without going through qemu^Wkvm tool.

-- 
I have a truly marvellous patch that fixes the bug which this
signature is too narrow to contain.

  reply	other threads:[~2011-08-25 14:00 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-25 13:29 [Qemu-devel] Questions regarding ivshmem spec Sasha Levin
2011-08-25 14:00 ` Avi Kivity [this message]
2011-08-25 14:39   ` Sasha Levin
2011-08-25 14:40     ` Avi Kivity
2011-08-25 14:42       ` Sasha Levin
2011-08-29 15:25 ` Sasha Levin
2011-08-29 18:15   ` Cam Macdonell
2011-08-30 17:37 ` 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=4E56556E.1080805@redhat.com \
    --to=avi@redhat.com \
    --cc=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 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).