From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Date: Sun, 3 Mar 2013 23:58:28 +0100
From: Joerg Roedel <joro@8bytes.org>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: shuah.khan@hp.com, iommu@lists.linux-foundation.org,
	LKML <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	Greg KH <gregkh@linuxfoundation.org>, shuahkhan@gmail.com
Subject: Re: [PATCH 3.2] iommu/amd: Initialize device table after dma_ops
Message-ID: <20130303225828.GA22602@8bytes.org>
References: <1362087590.2822.44.camel@lorien2>
 <1362265235.3768.156.camel@deadeye.wl.decadent.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1362265235.3768.156.camel@deadeye.wl.decadent.org.uk>
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <stable.vger.kernel.org>

Hi Ben,

On Sat, Mar 02, 2013 at 11:00:35PM +0000, Ben Hutchings wrote:
> I'm not convinced about this backport, because the order of
> initialisation already changed a lot after 3.2 and before the upstream
> commit.  So I'm going to wait for Joerg to confirm that this makes sense
> before adding it to the patch queue.

The patch looks good, it fixes a race condition during amd_iommu
initialization. I'll also gave the backport a test to be sure it
doesn't break anything.

Thanks,

	Joerg