[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2124490.J3euH9zgZk@phil>
Date: Tue, 05 Apr 2016 10:10:48 -0700
From: Heiko Stuebner <heiko@...ech.de>
To: Joerg Roedel <joro@...tes.org>
Cc: Tomeu Vizoso <tomeu.vizoso@...labora.com>,
linux-kernel@...r.kernel.org, iommu@...ts.linux-foundation.org,
linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org
Subject: Re: [PATCH] iommu/rockchip: Only log stall errors when attaching
Am Dienstag, 5. April 2016, 09:48:15 schrieb Heiko Stuebner:
> Am Dienstag, 5. April 2016, 16:57:26 schrieb Joerg Roedel:
> > On Tue, Mar 22, 2016 at 04:04:33PM +0100, Tomeu Vizoso wrote:
> > > Move the logging of timeouts when stalling the MMU to
> > > rk_iommu_attach_device, as it's expected that sometimes the MMU won't
> > > get stalled when detaching a device, and it's not a real problem that
> > > would need to be communicated to the user.
> > >
> > > Signed-off-by: Tomeu Vizoso <tomeu.vizoso@...labora.com>
> >
> > Heiko, any opinion on this patch?
>
> I don't know enough about iommus (and the rockchip implementation) to
> judge if this is correct. The reasoning sound right though and it seems
> to fix an issue for Tomeu.
>
> One complaint would be that I'd expect the behaviour to match between the
> enable and disable functions. Meaning I'd want the error message from
> rk_iommu_disable_stall to also move rk_iommu_attach_device.
hmm, or does John's patch maybe tie into this problem?
Aka, does the iommu simply does not detect when it's already stalled and
emits the timeout then?
Tomeu, in which cases do you see the excess error message?
Powered by blists - more mailing lists