Linux IOMMU Development
 help / color / mirror / Atom feed
From: Will Deacon <will.deacon-5wv7dgnIgG8@public.gmane.org>
To: Joerg Roedel <joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
Cc: "iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org"
	<iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org>
Subject: Re: [GIT PULL] iommu/arm-smmu: fixes for 3.14
Date: Tue, 18 Feb 2014 18:36:26 +0000	[thread overview]
Message-ID: <20140218183626.GC2010@mudshark.cambridge.arm.com> (raw)
In-Reply-To: <20140218175027.GE11432-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>

Hi Joerg,

On Tue, Feb 18, 2014 at 05:50:27PM +0000, Joerg Roedel wrote:
> On Mon, Feb 10, 2014 at 06:32:32PM +0000, Will Deacon wrote:
> >   - Andreas Herrmann took the driver for a run with a real SATA
> >     controller, which caused the new mutex-based locking to explode
> >     since we require mappings in atomic context
> 
> I just did quick review of the changes. Was the SATA controller using
> the IOMMU through the DMA-API? In this case you would need the IRQ-safe
> spinlocks to avoid dead-locks because the DMA-API can be used from
> IRQ-context.

Unfortunately, I don't know and since Calxeda has ceased to be, Andreas is
no longer working on this (I suspect his email address also bounces).

I can send an additional patch using spin_*_irq{save,restore} for the
domain->lock if you like?

Will

  parent reply	other threads:[~2014-02-18 18:36 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-10 18:32 [GIT PULL] iommu/arm-smmu: fixes for 3.14 Will Deacon
     [not found] ` <20140210183232.GH12826-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2014-02-18 11:27   ` Joerg Roedel
2014-02-18 17:50   ` Joerg Roedel
     [not found]     ` <20140218175027.GE11432-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-02-18 18:36       ` Will Deacon [this message]
     [not found]         ` <20140218183626.GC2010-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2014-02-18 19:21           ` Will Deacon
     [not found]             ` <20140218192137.GJ2010-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2014-02-20 11:29               ` Joerg Roedel
     [not found]                 ` <20140220112919.GG11432-zLv9SwRftAIdnm+yROfE0A@public.gmane.org>
2014-02-20 11:51                   ` Will Deacon
     [not found]                     ` <20140220115127.GH3615-MRww78TxoiP5vMa5CHWGZ34zcgK1vI+I0E9HWUfgJXw@public.gmane.org>
2014-02-20 12:14                       ` Joerg Roedel

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=20140218183626.GC2010@mudshark.cambridge.arm.com \
    --to=will.deacon-5wv7dgnigg8@public.gmane.org \
    --cc=iommu-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=joro-zLv9SwRftAIdnm+yROfE0A@public.gmane.org \
    /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