On Thu, Apr 18, 2013 at 01:56:42PM -0500, Suthikulpanit, Suravee wrote:
> On 4/18/2013 1:35 PM, Joerg Roedel wrote:
> According to the "kernel/irq/handle.c:irq_wake_thread()", I thought
> that for the threaded IRQ, if the system getting a new interrupt
> from the device while the thread is running
Hi Olav,
On Tue, Apr 16, 2013 at 07:18:42PM +0100, Olav Haugan wrote:
> On 4/15/2013 6:13 AM, Will Deacon wrote:
> > If so, doesn't that strongly tie your video driver to the SMMU?
>
> Isn't this more or less what you are doing in DT where you associate
> specific devices with an IOMMU (mmu-maste
On 4/18/2013 1:35 PM, Joerg Roedel wrote:
On Thu, Apr 18, 2013 at 11:59:58AM -0500, Suthikulpanit, Suravee wrote:
One last concern I have for this patch is the case when we re-enable
the interrupt, then another interrupt happens while we processing
the log and set the bit. If the interrupt thre
On Thu, Apr 18, 2013 at 11:59:58AM -0500, Suthikulpanit, Suravee wrote:
> One last concern I have for this patch is the case when we re-enable
> the interrupt, then another interrupt happens while we processing
> the log and set the bit. If the interrupt thread doesn't check this
> right before th
Joerg,
One last concern I have for this patch is the case when we re-enable the
interrupt, then another interrupt happens while we processing the log
and set the bit. If the interrupt thread doesn't check this right
before the thread exits the handler. We could still end up leaving the
inte
Joerg,
Do you have any more concerns about this patch?
Thank you,
Suravee
On 4/10/2013 10:57 AM, suravee.suthikulpa...@amd.com wrote:
From: Suravee Suthikulpanit
Add logic to decode AMD IOMMU event flag based on information from AMD IOMMU
specification.
This should simplify debugging IOMMU
On Thu, Apr 18, 2013 at 11:13:19AM -0500, Suravee Suthikulanit wrote:
> This workaround is required for both event log and ppr log. Your
> patch is only taking care of the event log.
Right, thanks for the notice. Here is the updated patch.
>From cebe04596989c4b9001e2c1571c4fb219ea37b99 Mon Sep 1
Joerg,
This workaround is required for both event log and ppr log. Your patch
is only taking care of the event log.
Suravee
On 4/18/2013 11:02 AM, Joerg Roedel wrote:
On Mon, Apr 15, 2013 at 02:07:46AM -0500, suravee.suthikulpa...@amd.com wrote:
drivers/iommu/amd_iommu.c | 145 +
On Mon, Apr 15, 2013 at 02:07:46AM -0500, suravee.suthikulpa...@amd.com wrote:
> drivers/iommu/amd_iommu.c | 145
> +
That is way too much for a simple erratum workaround, and too much for a
stable backport. I queued the patch below instead, which has
