public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Avi Kivity <avi@qumranet.com>
Cc: linux-kernel@vger.kernel.org,
	Rusty Russell <rusty@rusycorp.com.au>,
	virtualization@lists.osdl.org, kvm-devel@lists.sourceforge.net
Subject: Re: [kvm-devel] [PATCH 3/3] virtio PCI device
Date: Thu, 08 Nov 2007 09:06:19 -0600	[thread overview]
Message-ID: <473325EB.5090907@us.ibm.com> (raw)
In-Reply-To: <47331F47.70304@qumranet.com>

Avi Kivity wrote:
> If a pci device is capable of dma (or issuing interrupts), it will be 
> useless with pv pci.

Hrm, I think we may be talking about different things.  Are you thinking 
that the driver I posted allows you to do PCI pass-through over virtio?  
That's not what it is.

The driver I posted is a virtio implementation that uses a PCI device.  
This lets you use virtio-blk and virtio-net under KVM.  The alternative 
to this virtio PCI device would be a virtio transport built with 
hypercalls like lguest has.  I choose a PCI device because it ensured 
that each virtio device showed up like a normal PCI device.

Am I misunderstanding what you're asking about?

Regards,

Anthony Liguori

>
>>>  I think that with Amit's pvdma patches you
>>> can support dma-capable devices as well without too much fuss.
>>>   
>>
>> What is the use case you're thinking of?  A semi-paravirt driver that 
>> does dma directly to a device?
>
> No, an unmodified driver that, by using clever tricks with dma_ops, 
> can do dma directly to guest memory.  See Amit's patches.
>
> In fact, why do a virtio transport at all?  It can be done either with 
> trap'n'emulate, or by directly mapping the device mmio space into the 
> guest.
>
>
> (what use case are you considering? devices without interrupts and 
> dma? pci door stoppers?)
>


  reply	other threads:[~2007-11-08 15:06 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 [this message]
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
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=473325EB.5090907@us.ibm.com \
    --to=aliguori@us.ibm.com \
    --cc=avi@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rusty@rusycorp.com.au \
    --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