public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Carsten Otte <cotte@de.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
	Eric Van Hensbergen <ericvanhensbergen@us.ibm.com>,
	kvm-devel@lists.sourceforge.net, lguest <lguest@ozlabs.org>,
	linux-kernel@vger.kernel.org, virtualization@lists.osdl.org
Subject: Re: [kvm-devel] [PATCH 3/3] virtio PCI device
Date: Tue, 27 Nov 2007 10:09:50 +0100	[thread overview]
Message-ID: <474BDEDE.6060603@de.ibm.com> (raw)
In-Reply-To: <474BDD28.7050801@qumranet.com>

Avi Kivity wrote:
> No, definitely not define a hypercall ABI.  The feature bit should say 
> "this device understands a hypervisor-specific way of kicking.  consult 
> your hypervisor manual and cpuid bits for further details.  should you 
> not be satisfied with this method, port io is still available".
...unless you're lucky enough to be on s390 where pio is not available.
I don't see why we'd have two different ways to talk to a virtio 
device. I think we should use a hypercall for interrupt injection, 
without support for grumpy old soldered pci features other than 
HPA-style Lguest PCI bus organization. There are no devices that we 
want to be backward compatible with.

  reply	other threads:[~2007-11-27  9:10 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08  2:46 [PATCH 0/3] virtio PCI driver Anthony Liguori
2007-11-08  2:46 ` [PATCH 1/3] Export vring functions for modules to use Anthony Liguori
2007-11-08  2:46   ` [PATCH 2/3] Put the virtio under the virtualization menu Anthony Liguori
2007-11-08  2:46     ` [PATCH 3/3] virtio PCI device Anthony Liguori
2007-11-08  6:12       ` [kvm-devel] " Avi Kivity
2007-11-08 13:54         ` Anthony Liguori
2007-11-08 14:37           ` Avi Kivity
2007-11-08 15:06             ` Anthony Liguori
2007-11-08 15:13               ` Avi Kivity
2007-11-08 23:43           ` Dor Laor
2007-11-08 17:46       ` Arnd Bergmann
2007-11-08 19:04         ` Anthony Liguori
2007-11-09 11:03           ` Arnd Bergmann
2007-11-09  0:39       ` Dor Laor
2007-11-09  2:17         ` Anthony Liguori
2007-11-20 15:01       ` Avi Kivity
2007-11-20 15:43         ` Anthony Liguori
2007-11-20 16:12           ` Avi Kivity
2007-11-20 22:16             ` Anthony Liguori
2007-11-21  7:13               ` Avi Kivity
2007-11-21 18:22                 ` Zachary Amsden
2007-11-22  7:32                   ` Avi Kivity
2007-11-23 16:51                 ` Anthony Liguori
2007-11-23 17:47                   ` Avi Kivity
2007-11-26 19:18                     ` Anthony Liguori
2007-11-27  9:02                       ` Avi Kivity
2007-11-27  9:09                         ` Carsten Otte [this message]
2007-11-27  9:27                           ` Avi Kivity
2007-11-27 10:12                             ` Carsten Otte
2007-11-27 10:19                               ` Avi Kivity
2007-11-27 10:28                                 ` Carsten Otte
2007-11-27  9:25                         ` Arnd Bergmann
2007-11-08  6:49     ` [kvm-devel] [PATCH 2/3] Put the virtio under the virtualization menu Avi Kivity

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=474BDEDE.6060603@de.ibm.com \
    --to=cotte@de.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=carsteno@de.ibm.com \
    --cc=ericvanhensbergen@us.ibm.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=lguest@ozlabs.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=virtualization@lists.osdl.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