From: awallis@codeaurora.org (Adam Wallis)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3][for 4.15] dmaengine: dmatest: move callback wait queue to thread context
Date: Mon, 20 Nov 2017 10:27:44 -0500 [thread overview]
Message-ID: <d59802cd-8bf2-8ad8-a9aa-6117b433746b@codeaurora.org> (raw)
In-Reply-To: <CAPcyv4gw3++W0DG=84ansCjJAop_KZSXXinY7eDEsWQ4quhXCQ@mail.gmail.com>
On 11/17/2017 12:33 PM, Dan Williams wrote:
> On Fri, Nov 17, 2017 at 9:28 AM, Adam Wallis <awallis@codeaurora.org> wrote:
>> On 11/17/2017 12:01 PM, Adam Wallis wrote:
> [..]
>>> Dan
>>> An important part of my patch was severed in this v3 submission. My apologies.
>>>
>>> There is a change that addresses, I believe, your concern that was in v2
>>>
>>> /* terminate all transfers on specified channels */
>>> - if (ret)
>>> + if (ret || failed_tests)
>>> dmaengine_terminate_all(chan);
>>>
>>> Will clean up again, retest, and resubmit. Thanks for your patience and instruction.
>>
>> Dan, I thought the patch was truncated, but it's all there in V3. I should have
>> finished my coffee before responding. You are absolutely right that in the timed
>> out case that dmaengine_terminate_all(chan) should be called, and that change is
>> in fact already included in this patch set
>>
>> @@ -789,7 +782,7 @@ static int dmatest_func(void *data)
>> dmatest_KBs(runtime, total_len), ret);
>>
>> /* terminate all transfers on specified channels */
>> - if (ret)
>> + if (ret || failed_tests)
>> dmaengine_terminate_all(chan);
>>
>> Would you prefer that I add a better description in the commit text to address
>> the fact this was in fact added?
>
> Ah, sorry I overlooked that.
>
> What about the case where the dmaengine does not support the
> terminate_all operation? I think we should WARN in that case, but
> that's also where the per-operation allocation of a done variable can
> prevent done notifications leaking between operations.
>
Dan, thanks for your comments. I just released v4 of this patch. Let me know if
I misunderstood what you said above. I do acknowledge that container_of might be
less desirable than just changing the argument that we pass to the callback.
Open to your suggestions!
> _______________________________________________
> linux-arm-kernel mailing list
> linux-arm-kernel at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>
--
Adam Wallis
Qualcomm Datacenter Technologies as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2017-11-20 15:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-17 14:11 [PATCH v3][for 4.15] dmaengine: dmatest: move callback wait queue to thread context Adam Wallis
2017-11-17 15:12 ` Dan Williams
2017-11-17 15:28 ` Adam Wallis
2017-11-17 15:57 ` Dan Williams
2017-11-17 17:01 ` Adam Wallis
2017-11-17 17:17 ` Adam Wallis
2017-11-17 17:36 ` Dan Williams
2017-11-17 17:28 ` Adam Wallis
2017-11-17 17:33 ` Dan Williams
2017-11-20 15:27 ` Adam Wallis [this message]
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=d59802cd-8bf2-8ad8-a9aa-6117b433746b@codeaurora.org \
--to=awallis@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
/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.