All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wright <chrisw@sous-sol.org>
To: James Neave <roboj1m@gmail.com>
Cc: Chris Wright <chrisw@sous-sol.org>,
	Alex Williamson <alex.williamson@redhat.com>,
	kvm@vger.kernel.org, "Roedel, Joerg" <Joerg.Roedel@amd.com>
Subject: Re: PCI Passthrough, error: The driver 'pci-stub' is occupying your device 0000:08:06.2
Date: Thu, 24 Feb 2011 16:13:32 -0800	[thread overview]
Message-ID: <20110225001332.GC4988@sequoia.sous-sol.org> (raw)
In-Reply-To: <AANLkTinhganuKabA3T2Yo52HkKaYdX5XJMF0bdxNgFxY@mail.gmail.com>

* James Neave (roboj1m@gmail.com) wrote:
> Just out of interest, what kind of mileage would I expect out of
> buying a shiny new PCIe tuner?

Hard to say.  One advantage would be if it's using MSI or MSI-X
interrupts.

> Can I pass through PCIe?

Often, yes (still some caveats w.r.t. extended config space I believe).

> Would it work better because it wouldn't be
> behind a bridge? WOULD it not be behind a bridge?

You should have a PCIe slot that does not sit behind a PCI-PCI bridge.

> As much as I'd hate to solve a problem with the application of money... :(

If you just want _one_ tuner to go to the guest, you should be able to
do that by unbinding the other devices and giving the guest just the one
usb controller (assuming just assigning the usb device itself is hitting
usb/qemu stack limitations).  The trick is to be sure to unbind any host
devices that are sharing interrupts with the one device you want the
guest to have.  With USB controllers you just have to be sure you know
which ports they map to so you don't kill a keyboard, mouse, external
disk, etc...

> (OT question, on mailing lists should I use Reply All or just reply
> and change the To address to kvm.vger.kernel.org?)

Reply all is best.

thanks,
-chris

  reply	other threads:[~2011-02-25  0:13 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-05 16:34 PCI Passthrough, error: The driver 'pci-stub' is occupying your device 0000:08:06.2 James Neave
2011-02-07 13:26 ` Daniel P. Berrange
2011-02-08  9:13   ` James Neave
2011-02-08  9:59   ` Kenni Lund
2011-02-08 10:17     ` James Neave
2011-02-12 16:04       ` James Neave
2011-02-14 17:48         ` Alex Williamson
2011-02-21 20:31           ` James Neave
2011-02-21 21:01             ` Alex Williamson
2011-02-21 22:25               ` James Neave
2011-02-21 22:49                 ` James Neave
2011-02-21 22:55                   ` James Neave
2011-02-21 23:05                     ` James Neave
2011-02-22  1:51                 ` Chris Wright
2011-02-22  9:18                   ` James Neave
2011-02-22  9:53                     ` Roedel, Joerg
2011-02-22 10:11                       ` James Neave
2011-02-23  0:11                     ` Chris Wright
2011-02-23 19:44                       ` James Neave
2011-02-23 20:09                         ` James Neave
2011-02-24  9:26                           ` James Neave
2011-02-25  0:13                             ` Chris Wright [this message]
2011-02-25  0:06                           ` Chris Wright
2011-02-25 22:47                             ` James Neave
2011-02-25 23:02                               ` James Neave
2011-02-25 23:09                                 ` James Neave
2011-02-25 23:31                                   ` Chris Wright
2011-02-28 13:42                                     ` James Neave
2011-02-28 15:31                                       ` Chris Wright
2011-02-28 20:25                                         ` James Neave
2011-03-01 20:54                                           ` James Neave
     [not found]                                         ` <BANLkTi=ZHpHU=Gd+tTcLysTD3duGY8PPjQ@mail.gmail.com>
2011-05-10 16:00                                           ` James Neave
2011-02-25 23:14                               ` Chris Wright
2011-02-24 23:59                         ` Chris Wright
2011-02-21 23:28           ` Chris Wright
2011-02-21 23:50             ` James Neave

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=20110225001332.GC4988@sequoia.sous-sol.org \
    --to=chrisw@sous-sol.org \
    --cc=Joerg.Roedel@amd.com \
    --cc=alex.williamson@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=roboj1m@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 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.