All of lore.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@redhat.com>
To: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: Cam Macdonell <cam@cs.ualberta.ca>, kvm@vger.kernel.org
Subject: Re: [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts.
Date: Mon, 18 May 2009 17:26:15 +0300	[thread overview]
Message-ID: <4A117007.7040202@redhat.com> (raw)
In-Reply-To: <200905181607.32924.borntraeger@de.ibm.com>

Christian Borntraeger wrote:
> Sorry for the late question, but I missed your first version. Is there a way to change that code to use virtio instead of PCI? That would allow us to use this driver on s390 and maybe other virtio transports.
>   

Opinion differs.  See the discussion in 
http://article.gmane.org/gmane.comp.emulators.kvm.devel/30119.

To summarize, Anthony thinks it should use virtio, while I believe 
virtio is useful for exporting guest memory, not for importing host memory.

-- 
error compiling committee.c: too many arguments to function


  reply	other threads:[~2009-05-18 14:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-07 16:26 [PATCH v2] Driver for Inter-VM shared memory device for KVM supporting interrupts Cam Macdonell
2009-05-18 14:07 ` Christian Borntraeger
2009-05-18 14:26   ` Avi Kivity [this message]
2009-05-19  9:00     ` Christian Bornträger
2009-05-19  9:10       ` Avi Kivity
2009-05-19 16:51         ` Cam Macdonell
2009-05-20  2:58           ` Rusty Russell
2009-05-20  7:33             ` Christian Bornträger
2009-05-20  8:45               ` Avi Kivity
2009-05-20  9:07                 ` Christian Bornträger
2009-05-20  9:11                   ` Avi Kivity
2009-05-20  9:20                     ` Christian Bornträger
2009-05-25  6:18               ` Rusty Russell
2009-05-20  8:07             ` François Diakhate
2009-05-19 18:39       ` Anthony Liguori
2009-05-20  7:33         ` Christian Bornträger
2009-05-20 13:26           ` Anthony Liguori
2009-05-18 16:56   ` 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=4A117007.7040202@redhat.com \
    --to=avi@redhat.com \
    --cc=borntraeger@de.ibm.com \
    --cc=cam@cs.ualberta.ca \
    --cc=kvm@vger.kernel.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 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.