From: Joerg Roedel <joro@8bytes.org>
To: Rob Clark <robdclark@gmail.com>
Cc: "iommu@lists.linux-foundation.org"
<iommu@lists.linux-foundation.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
Jordan Crouse <jcrouse@codeaurora.org>,
Will Deacon <will.deacon@arm.com>,
Robin Murphy <robin.murphy@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] iommu: arm-smmu: stall support
Date: Fri, 22 Sep 2017 11:02:05 +0200 [thread overview]
Message-ID: <20170922090204.GJ8398@8bytes.org> (raw)
In-Reply-To: <CAF6AEGuutkqjrWk4jagE=p-NwHgxdiPZjjsaFsfwtczK568j+A@mail.gmail.com>
On Tue, Sep 19, 2017 at 10:23:43AM -0400, Rob Clark wrote:
> I would like to decide in the IRQ whether or not to queue work or not,
> because when we get a gpu fault, we tend to get 1000's of gpu faults
> all at once (and I really only need to handle the first one). I
> suppose that could also be achieved by having a special return value
> from the fault handler to say "call me again from a wq"..
>
> Note that in the drm driver I already have a suitable wq to queue the
> work, so it really doesn't buy me anything to have the iommu driver
> toss things off to a wq for me. Might be a different situation for
> other drivers (but I guess mostly other drivers are using iommu API
> indirectly via dma-mapping?)
Okay, so since you are the only user for now, we don't need a
work-queue. But I still want the ->resume call-back to be hidden in the
iommu code and not be exposed to users.
We already have per-domain fault-handlers, so the best solution for now
is to call ->resume from report_iommu_fault() when the fault-handler
returns a special value.
Regards,
Joerg
WARNING: multiple messages have this Message-ID (diff)
From: joro@8bytes.org (Joerg Roedel)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC] iommu: arm-smmu: stall support
Date: Fri, 22 Sep 2017 11:02:05 +0200 [thread overview]
Message-ID: <20170922090204.GJ8398@8bytes.org> (raw)
In-Reply-To: <CAF6AEGuutkqjrWk4jagE=p-NwHgxdiPZjjsaFsfwtczK568j+A@mail.gmail.com>
On Tue, Sep 19, 2017 at 10:23:43AM -0400, Rob Clark wrote:
> I would like to decide in the IRQ whether or not to queue work or not,
> because when we get a gpu fault, we tend to get 1000's of gpu faults
> all at once (and I really only need to handle the first one). I
> suppose that could also be achieved by having a special return value
> from the fault handler to say "call me again from a wq"..
>
> Note that in the drm driver I already have a suitable wq to queue the
> work, so it really doesn't buy me anything to have the iommu driver
> toss things off to a wq for me. Might be a different situation for
> other drivers (but I guess mostly other drivers are using iommu API
> indirectly via dma-mapping?)
Okay, so since you are the only user for now, we don't need a
work-queue. But I still want the ->resume call-back to be hidden in the
iommu code and not be exposed to users.
We already have per-domain fault-handlers, so the best solution for now
is to call ->resume from report_iommu_fault() when the fault-handler
returns a special value.
Regards,
Joerg
next prev parent reply other threads:[~2017-09-22 9:02 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-14 19:44 [RFC] iommu: arm-smmu: stall support Rob Clark
2017-09-14 19:44 ` Rob Clark
2017-09-14 19:44 ` Rob Clark
2017-09-18 11:13 ` Jean-Philippe Brucker
2017-09-18 11:13 ` Jean-Philippe Brucker
[not found] ` <9c2c136a-8c0f-6196-a135-0135b41c9b6e-5wv7dgnIgG8@public.gmane.org>
2017-09-18 12:11 ` Rob Clark
2017-09-18 12:11 ` Rob Clark
2017-09-18 12:11 ` Rob Clark
[not found] ` <CAF6AEGv0WZe-bYXUVYt4WxMX3RFnZxr5038pDg3VOiP8Edx+4Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-18 17:33 ` Will Deacon
2017-09-18 17:33 ` Will Deacon
2017-09-18 17:33 ` Will Deacon
2017-09-19 12:30 ` Joerg Roedel
2017-09-19 12:30 ` Joerg Roedel
2017-09-19 14:23 ` Rob Clark
2017-09-19 14:23 ` Rob Clark
2017-09-22 9:02 ` Joerg Roedel [this message]
2017-09-22 9:02 ` Joerg Roedel
2017-09-22 10:02 ` Jean-Philippe Brucker
2017-09-22 10:02 ` Jean-Philippe Brucker
2017-09-22 18:42 ` Rob Clark
2017-09-22 18:42 ` Rob Clark
[not found] ` <CAF6AEGuh0FiNWEAmFm+7-7pc6MV5hKKz9cyA_J0d256bY-nYOQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-09-27 12:15 ` Joerg Roedel
2017-09-27 12:15 ` Joerg Roedel
2017-09-27 12:15 ` Joerg Roedel
2017-09-27 13:49 ` Jean-Philippe Brucker
2017-09-27 13:49 ` Jean-Philippe Brucker
2017-09-27 14:35 ` Joerg Roedel
2017-09-27 14:35 ` Joerg Roedel
2017-09-27 16:14 ` Rob Clark
2017-09-27 16:14 ` Rob Clark
2019-05-10 18:23 ` Rob Clark
2019-05-10 18:23 ` Rob Clark
2019-05-10 18:23 ` Rob Clark
2019-05-13 18:37 ` Jean-Philippe Brucker
2019-05-13 18:37 ` Jean-Philippe Brucker
2019-05-13 18:37 ` Jean-Philippe Brucker
2019-05-14 1:54 ` Rob Clark
2019-05-14 1:54 ` Rob Clark
2019-05-14 1:54 ` Rob Clark
2019-05-14 10:24 ` Robin Murphy
2019-05-14 10:24 ` Robin Murphy
2019-05-14 10:24 ` Robin Murphy
2019-05-14 17:17 ` Rob Clark
2019-05-14 17:17 ` Rob Clark
2019-05-14 17:17 ` Rob Clark
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=20170922090204.GJ8398@8bytes.org \
--to=joro@8bytes.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jcrouse@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robdclark@gmail.com \
--cc=robin.murphy@arm.com \
--cc=will.deacon@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.