From mboxrd@z Thu Jan  1 00:00:00 1970
From: Sasha Levin <levinsasha928@gmail.com>
Subject: Re: Questions regarding ivshmem spec
Date: Thu, 25 Aug 2011 17:42:03 +0300
Message-ID: <1314283323.3692.60.camel@lappy>
References: <1314278954.3692.55.camel@lappy>  <4E56556E.1080805@redhat.com>
	<1314283146.3692.59.camel@lappy>  <4E565EDF.4080800@redhat.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
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>
To: Avi Kivity <avi@redhat.com>
Return-path: <qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org>
In-Reply-To: <4E565EDF.4080800@redhat.com>
List-Unsubscribe: <https://lists.nongnu.org/mailman/options/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: </archive/html/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <https://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org
List-Id: kvm.vger.kernel.org

On Thu, 2011-08-25 at 17:40 +0300, Avi Kivity wrote:
> On 08/25/2011 05:39 PM, Sasha Levin wrote:
> > On Thu, 2011-08-25 at 17:00 +0300, Avi Kivity wrote:
> > >  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.
> > >
> >
> > But the doorbell is a single DWORD, so if a guest writes to it we'd
> > still need to figure out which guest/vector he wants to poke from
> > userspace, no?
> >
> > If it was an array of doorbells then yes, we could assign an ioeventfd
> > to each offset - but now I don't quite see how we can avoid passing
> > through the userspace.
> >
> 
> Use the datamatch facility.
> 
> We didn't want an array of registers to avoid scaling issues (PIO space 
> is quite small).
> 
> 

Ah, right.

Thanks!

-- 

Sasha.