public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Cam Macdonell <cam@cs.ualberta.ca>
Cc: kvm@vger.kernel.org, qemu-devel@nongnu.org
Subject: Re: [PATCH v3 0/2] Inter-VM shared memory PCI device
Date: Fri, 26 Mar 2010 18:56:11 +0300	[thread overview]
Message-ID: <4BACD91B.2070604@redhat.com> (raw)
In-Reply-To: <8286e4ee1003251605rd3b0694tb2e98bd34e9b0fea@mail.gmail.com>

On 03/26/2010 01:05 AM, Cam Macdonell wrote:
>
>> I meant a unicast doorbell: 16 bits for guest ID, 16 bits for vector number.
>>      
> Ah, yes.  Who knew "two bit registers" is an ambiguous term.  Do you
> strongly prefer the one doorbell design?
>    

Just floating out ideas.  An advantage is that it conserves register 
space; this is important if we use PIO.  For mmio this isn't so important.

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2010-03-26 15:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-25  6:08 [PATCH v3 0/2] Inter-VM shared memory PCI device Cam Macdonell
2010-03-25  6:08 ` [PATCH v3 1/2] Support adding a file to qemu's ram allocation Cam Macdonell
2010-03-25  6:08   ` [PATCH v3 2/2] Inter-VM shared memory PCI device Cam Macdonell
2010-03-25  9:04 ` [PATCH v3 0/2] " Avi Kivity
2010-03-25  9:21   ` Michael S. Tsirkin
2010-03-25 16:11     ` Cam Macdonell
2010-03-25  9:26   ` Markus Armbruster
2010-03-25  9:37     ` Avi Kivity
2010-03-25 16:50   ` Cam Macdonell
2010-03-25 17:02     ` Avi Kivity
2010-03-25 17:35       ` Cam Macdonell
2010-03-25 17:48         ` Avi Kivity
2010-03-25 18:17           ` Cam Macdonell
2010-03-25 21:10             ` Avi Kivity
2010-03-25 23:05               ` Cam Macdonell
2010-03-26 15:56                 ` Avi Kivity [this message]
2010-03-26  1:32             ` [Qemu-devel] " Jamie Lokier
2010-03-26 15:52               ` 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=4BACD91B.2070604@redhat.com \
    --to=avi@redhat.com \
    --cc=cam@cs.ualberta.ca \
    --cc=kvm@vger.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