From: Avi Kivity <avi@redhat.com>
To: nemesis@icequake.net
Cc: Alexander Graf <agraf@suse.de>,
kvm@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: PCI passthrough resource remapping
Date: Thu, 14 Jan 2010 17:34:42 +0200 [thread overview]
Message-ID: <4B4F3992.3000906@redhat.com> (raw)
In-Reply-To: <20100114152652.GI4727@localhost.localdomain>
On 01/14/2010 05:26 PM, Ryan C. Underwood wrote:
> On Thu, Jan 14, 2010 at 03:59:53PM +0200, Avi Kivity wrote:
>
>> >
>>
>>> > >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.
>>
> It claims to be PCI 3.0 compliant. But I don't see any mention MSI
> anywhere in the specification:
> http://www.aeneas.com.cn/PDF/Ricoh/2005/R5C832E1%5B1%5D.00.pdf
>
> Attached is lspci -vv, thanks.
>
>
>
> 08:09.0 FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 05) (prog-if 10)
> Subsystem: Hewlett-Packard Company Device 30cd
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium>TAbort-<TAbort-<MAbort->SERR-<PERR- INTx-
> Latency: 64 (500ns min, 1000ns max)
> Interrupt: pin A routed to IRQ 16
> Region 0: [virtual] Memory at f4400000 (32-bit, non-prefetchable) [size=2K]
> Capabilities:<access denied>
> Kernel driver in use: pci-stub
> Kernel modules: firewire-ohci, ohci1394
>
>
Michael, I think 'DisINTx-' means the device is not PCI 2.3 compliant?
> 08:09.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev 12)
> Subsystem: Hewlett-Packard Company Device 30cd
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr+ Stepping- SERR+ FastB2B- DisINTx+
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium>TAbort-<TAbort-<MAbort->SERR-<PERR- INTx-
> Latency: 248, Cache Line Size: 1020 bytes
> Interrupt: pin B routed to IRQ 10
> Region 0: Memory at f4401400 (32-bit, non-prefetchable) [size=256]
> Capabilities:<access denied>
> Kernel driver in use: pci-stub
>
But another function has this feature?
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2010-01-14 15:34 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
2010-01-14 15:26 ` Ryan C. Underwood
2010-01-14 15:34 ` Avi Kivity [this message]
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=4B4F3992.3000906@redhat.com \
--to=avi@redhat.com \
--cc=agraf@suse.de \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--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