All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexis Bruemmer <alexisb@us.ibm.com>
To: FUJITA Tomonori <fujita.tomonori@lab.ntt.co.jp>
Cc: muli@il.ibm.com, linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: [PATCH 0/2] x86: per-device dma_mapping_ops
Date: Wed, 14 May 2008 19:00:13 -0700	[thread overview]
Message-ID: <1210816813.5596.13.camel@alexis> (raw)
In-Reply-To: <20080515101212Z.tomof@acm.org>

On Thu, 2008-05-15 at 10:12 +0900, FUJITA Tomonori wrote:
> On Wed, 14 May 2008 08:49:24 +0300
> Muli Ben-Yehuda <muli@il.ibm.com> wrote:
> 
> > On Tue, May 13, 2008 at 03:04:50PM +0900, FUJITA Tomonori wrote:
<snip>
> > Awesome! Much needed, thank you for doing this.
> 
> No problem. Well, as you know, it's just a base. We need more work to
> solve the problems on the top of this.
Yes thank you!  
> 
> I'd like to have a mechanism to register a hook called when a new pci
> (or dma capable) device is created. It enables IOMMUs to set up an
> appropriate dma_mapping_ops per device. It could also enables us to
> simplify the IOMMUs code to initilize devices at startup (for exmple,
> intel-iommu checks all the pci devices and creates a domain per device
> if necessary).
I wanted to try and create a test version of this, at least for the
calgary side, but ran into an error with this patch set:

Fusion MPT SAS Host driver 3.04.06
ACPI: PCI Interrupt 0000:34:00.0[A] -> GSI 142 (level, low) -> IRQ 142
mptbase: ioc0: Initiating bringup
ioc0: LSISAS1078 C1: Capabilities={Initiator}
mptbase: ioc0: PCI-MSI enabled
Calgary: DMA error on CalIOC2 PHB 0x33
Calgary: 0x02000000@CSR 0x00000000@PLSSR 0xb0008000@CSMR 0x00000000@MCK
Calgary: 0x00000000@0x810 0xfee0c000@0x820 0x00000000@0x830
0x00000000@0x840 0x03804a00@0x850 0x00000000@0x860 0x00000000@0x870
Calgary: 0x00000000@0xcb0
mptbase: ioc0: Initiating recovery
mptbase: ioc0: WARNING - Unexpected doorbell active!
mptbase: ioc0: WARNING - NOT READY!
mptbase: ioc0: WARNING - Cannot recover rc = -1!
mptbase: ioc0: WARNING - Firmware Reload FAILED!
Clocksource tsc unstable (delta = 48333779773 ns)

Not sure what is causing this error, but will keep digging.  Any ideas?

--Alexis


  reply	other threads:[~2008-05-15  2:04 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-13  6:04 [PATCH 0/2] x86: per-device dma_mapping_ops FUJITA Tomonori
2008-05-13  6:04 ` [PATCH 1/2] add the device argument to dma_mapping_error FUJITA Tomonori
2008-05-13  6:04   ` [PATCH 2/2] x86: per-device dma_mapping_ops support FUJITA Tomonori
2008-05-14  5:55     ` Muli Ben-Yehuda
2008-05-15 20:45     ` Yinghai Lu
2008-05-16  3:44       ` FUJITA Tomonori
2008-05-13 15:39   ` [PATCH 1/2] add the device argument to dma_mapping_error Randy Dunlap
2008-05-15  1:12     ` FUJITA Tomonori
2008-05-14  5:49 ` [PATCH 0/2] x86: per-device dma_mapping_ops Muli Ben-Yehuda
2008-05-15  1:12   ` FUJITA Tomonori
2008-05-15  2:00     ` Alexis Bruemmer [this message]
2008-05-15  2:30       ` FUJITA Tomonori
2008-05-15 18:21         ` Alexis Bruemmer
2008-05-15 15:17       ` Muli Ben-Yehuda
2008-05-15 15:15     ` Muli Ben-Yehuda
2008-05-15  9:01 ` Andi Kleen
2008-05-15  9:16   ` FUJITA Tomonori
2008-05-15  9:30     ` Andi Kleen
2008-05-15  9:41       ` FUJITA Tomonori
2008-05-15 10:48         ` Andi Kleen
2008-05-15 15:32           ` Muli Ben-Yehuda
2008-05-16  3:44           ` FUJITA Tomonori
2008-05-16  5:24             ` Andi Kleen
2008-05-19  6:32               ` FUJITA Tomonori
2008-05-15 15:26         ` Muli Ben-Yehuda
2008-05-15 21:03           ` Andi Kleen
2008-05-15 21:39             ` Muli Ben-Yehuda
2008-05-15 21:45               ` Andi Kleen
2008-05-15 21:53                 ` Muli Ben-Yehuda
2008-05-15 22:05                   ` Muli Ben-Yehuda
2008-05-15 18:25     ` Alexis Bruemmer

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=1210816813.5596.13.camel@alexis \
    --to=alexisb@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=fujita.tomonori@lab.ntt.co.jp \
    --cc=linux-kernel@vger.kernel.org \
    --cc=muli@il.ibm.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.