From: Arnd Bergmann <arnd@arndb.de>
To: Rusty Russell <rusty@rustcorp.com.au>,
David Miller <davem@davemloft.net>,
linux-kernel@vger.kernel.org, linuxppc-dev@ozlabs.org,
shemminger@vyatta.com, netdev@vger.kernel.org
Subject: Re: [PATCH RFC v5] net: add PCINet driver
Date: Thu, 15 Jan 2009 21:57:41 +0100 [thread overview]
Message-ID: <200901152157.42500.arnd@arndb.de> (raw)
In-Reply-To: <20090115182034.GA9091@ovro.caltech.edu>
On Thursday 15 January 2009, Ira Snyder wrote:
> Some sort of Broadcom chipset, I think. Full dmesg and lspci output are
> appended.
>
> The PCI bridge does mention MSI, so maybe it does support it. Would
> using the DMA from the host mean that the guest system couldn't use the
> DMA controller at all? All of the channels share the same interrupt line
> on the guest. I need one channel on the DMA controller on the guest to
> do realtime transfers from some data processing FPGAs on the board.
The PCI-CompactPCI bridge supports MSI, but that does not imply that
the host does. My limited understanding of x86 tells me that you need
to enable the I/O-APIC in order to use MSI. Your log shows two relavant
lines:
[ 0.000000] Local APIC disabled by BIOS -- you can enable it with "lapic"
and
[ 2.146845] IO APIC resources could be not be allocated.
I think you first need to enable the local APIC, then find out what the
problem with the IO APIC is. If possible, try enabling ACPI (sic) in the
BIOS in order to get the APIC support.
If you get that to work, you can use the interrupt line of the DMA controller
to signal interrupts to the FSL machine, while using DMA transfers to the
MSI address for sending interrupts to the host machine.
Arnd <><
next prev parent reply other threads:[~2009-01-15 21:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-07 19:50 [PATCH RFC v5] net: add PCINet driver Ira Snyder
2009-01-08 19:16 ` David Miller
2009-01-08 19:27 ` Ira Snyder
2009-01-08 21:51 ` Ira Snyder
2009-01-10 23:32 ` Benjamin Herrenschmidt
2009-01-12 17:56 ` Arnd Bergmann
2009-01-13 2:32 ` Rusty Russell
2009-01-13 3:34 ` Ira Snyder
2009-01-13 16:33 ` Arnd Bergmann
2009-01-13 16:40 ` Ira Snyder
2009-01-13 17:42 ` Arnd Bergmann
2009-01-15 0:12 ` Ira Snyder
2009-01-15 12:58 ` Arnd Bergmann
2009-01-15 16:54 ` Ira Snyder
2009-01-15 17:53 ` Arnd Bergmann
2009-01-15 18:20 ` Ira Snyder
2009-01-15 20:57 ` Arnd Bergmann [this message]
2009-01-15 23:27 ` Ira Snyder
2009-01-15 19:21 ` Ira Snyder
2009-01-15 21:22 ` Arnd Bergmann
2009-01-15 21:40 ` Ira Snyder
2009-01-15 22:53 ` Arnd Bergmann
2009-01-15 23:31 ` Ira Snyder
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=200901152157.42500.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=shemminger@vyatta.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