From: Avi Kivity <avi@redhat.com>
To: nemesis@icequake.net
Cc: Alexander Graf <agraf@suse.de>, kvm@vger.kernel.org
Subject: Re: PCI passthrough resource remapping
Date: Thu, 14 Jan 2010 15:59:53 +0200 [thread overview]
Message-ID: <4B4F2359.9040100@redhat.com> (raw)
In-Reply-To: <20100110221538.GF4727@localhost.localdomain>
On 01/11/2010 12:15 AM, Ryan C. Underwood wrote:
> I guess I'll run the things I've found by the list to see if I'm off
> track or not.
>
> There is this patch:
> http://marc.info/?l=xen-devel&m=124748015304566&w=4
>
> which would seem to be related to what I'm doing, trying to pass through
> a multifunction device (a Ricoh firewire controller which has digital
> media card reader subfunctions).
>
> Then there is this patch:
> http://patchwork.kernel.org/patch/20195/
>
> Which is related to PCI passthrough without VT-d, but I have no idea if
> this patch is necessary or sufficient.
>
That effort has been discontinues.
> Also, just for further complication, the Ricoh chip does not support
> MSI and shares an IRQ on the system board with the USB host controller.
> I have rebound the USB host controller to pci-stub, but I'm not sure if
> that totally takes care of the IRQ-sharing-without-MSI issue.
>
Can you post lspci -vv output for that card? If it is pci 2.3 compliant
we might be able to handle the sharing.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-14 13:59 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-09 2:45 PCI passthrough resource remapping Ryan C. Underwood
2010-01-09 3:22 ` Alexander Graf
2010-01-10 21:53 ` Ryan C. Underwood
2010-01-10 22:15 ` Ryan C. Underwood
2010-01-14 13:59 ` Avi Kivity [this message]
2010-01-14 15:26 ` Ryan C. Underwood
2010-01-14 15:34 ` Avi Kivity
2010-01-14 15:47 ` Michael S. Tsirkin
2010-01-14 15:54 ` Avi Kivity
2010-01-14 18:31 ` Ryan C. Underwood
2010-01-14 19:09 ` Avi Kivity
2010-01-14 19:34 ` Ryan C. Underwood
2010-01-16 9:23 ` Avi Kivity
2010-01-15 13:11 ` Pasi Kärkkäinen
2010-01-15 13:15 ` Alexander Graf
2010-03-26 2:37 ` Kenni Lund
2010-03-26 3:00 ` Brian Jackson
2010-03-29 17:23 ` Kenni Lund
2010-03-29 19:17 ` Alexander Graf
2010-03-29 23:00 ` Kenni Lund
2010-03-29 23:12 ` Alexander Graf
2010-03-29 23:47 ` Chris Wright
2010-03-30 0:21 ` Kenni Lund
2010-03-30 2:08 ` Chris Wright
2010-03-30 22:27 ` Kenni Lund
2010-03-30 22:29 ` Alexander Graf
2010-03-30 23:52 ` Kenni Lund
2010-03-31 0:59 ` Chris Wright
2010-03-30 23:58 ` Chris Wright
2010-03-31 0:47 ` Kenni Lund
2010-03-31 1:32 ` Chris Wright
2010-03-31 10:07 ` Kenni Lund
2010-03-31 15:15 ` Chris Wright
2010-03-31 11:43 ` Kenni Lund
2010-03-31 12:24 ` Alexander Graf
2010-03-31 13:04 ` Kenni Lund
2010-03-31 15:18 ` Chris Wright
2010-03-31 15:23 ` Alexander Graf
2010-04-07 5:52 ` 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=4B4F2359.9040100@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=nemesis@icequake.net \
/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