[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20141022151254.GJ10074@8bytes.org>
Date: Wed, 22 Oct 2014 17:12:54 +0200
From: Joerg Roedel <joro@...tes.org>
To: Daniel Kurtz <djkurtz@...omium.org>
Cc: Grant Grundler <grundler@...omium.org>,
Stéphane Marchesin <marcheu@...omium.org>,
Simon Xue <xxm@...k-chips.com>,
Heiko Stuebner <heiko@...ech.de>,
Grant Likely <grant.likely@...aro.org>,
Rob Herring <robh+dt@...nel.org>,
open list <linux-kernel@...r.kernel.org>,
"open list:IOMMU DRIVERS" <iommu@...ts.linux-foundation.org>,
"moderated list:ARM/Rockchip SoC..."
<linux-arm-kernel@...ts.infradead.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
"open list:OPEN FIRMWARE AND..." <devicetree@...r.kernel.org>
Subject: Re: [PATCH v5 1/3] iommu/rockchip: rk3288 iommu driver
On Tue, Oct 14, 2014 at 04:02:40PM +0800, Daniel Kurtz wrote:
> +static void rk_iommu_detach_device(struct iommu_domain *domain,
> + struct device *dev)
> +{
> + struct rk_iommu *iommu = dev_get_drvdata(dev->archdata.iommu);
> + struct rk_iommu_domain *rk_domain = domain->priv;
> + unsigned long flags;
> +
> + /* Allow 'virtual devices' (eg drm) to detach from domain */
> + if (!iommu)
> + return;
> +
> + iommu->domain = NULL;
I guess this line is a left-over? Setting iommu->domain to NULL here
before you disabled the IOMMU interrupt is racy. To be fully secure, you
should make sure that no interrupt handler is still running after you
disabled the IOMMU irq and before setting iommu->domain = NULL.
Other than that the code looks good.
Joerg
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists