public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: dor.laor@qumranet.com
Cc: kvm-devel <kvm-devel@lists.sourceforge.net>,
	Nicolas Daneau <nicolas.daneau@gmail.com>
Subject: Re: qemu/kvm: support for pci passthrough
Date: Thu, 08 May 2008 17:26:05 -0500	[thread overview]
Message-ID: <48237DFD.3020309@codemonkey.ws> (raw)
In-Reply-To: <1210279125.24261.323.camel@localhost.localdomain>

Dor Laor wrote:
> On Thu, 2008-05-08 at 12:03 +0200, Nicolas Daneau wrote:
>> Hi,
>>
>> I saw there was an active discussion about pci passthrough support in
>> KVM. I'm not a Dev, only a sys admin that need this support. As i saw
>> on the KVM home page that this feature is plan for 2H2008 in the
>> roadmap, I wondered if you already have a more precise time frame for
>> this release? Xen already have this feature but for the rest i prfer
>> KVM. As this is a key point for the final decsion (we have a Digium
>> TDM11B FXO/FXS pci card for an Asterisk VM), i'm waiting for an update
>> about this feature.
>>
> 
> This is feature is indeed work in progress. We have floating patches for
> several solutions:
> 1. Using Intel's VT-d - hw iommu support.
>    Patches were sent, needs some more scrubbing. The good thing is that 
>    it can live withing the kvm module and does not have to wait for 
>    kernel inclusion like the two below.

Nope, it uses the existing Linux VT-d support and requires patches to 
the existing code.  It can't live entirely within the external module.

Regards,

Anthony Liguori


> 2. PV dma - good only for Linux guests. Some locking issues needs to be 
>    solved + get into mainline kernel (>=2.6.27)
> 3. 1-1 mapping of the guest-host addresses. 
>    Will work for any guest, no need for special hw, good only for 
>    single guest and not 100% secure.
>    Needs a little more attention, worked in the past privately.
> 
> Bottom line, soon you'll have more than one option for pci pass through
> using kvm. There is no assurance we'll make it exactly in Q2.
> You can help by applying patches and sending results.
> Cheers,
> Dor
> 
>> Thanks for your answer
>>


-------------------------------------------------------------------------
This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
Don't miss this year's exciting event. There's still time to save $100. 
Use priority code J8TL2D2. 
http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone

           reply	other threads:[~2008-05-08 22:26 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1210279125.24261.323.camel@localhost.localdomain>]

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=48237DFD.3020309@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --cc=dor.laor@qumranet.com \
    --cc=kvm-devel@lists.sourceforge.net \
    --cc=nicolas.daneau@gmail.com \
    /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