From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: dave.jiang@intel.com, kristen.c.accardi@intel.com,
kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH v1] dmaengine: dmatest: Fix dmatest waiting less when interrupted
Date: Tue, 11 Mar 2025 02:36:42 +0530 [thread overview]
Message-ID: <174164080219.489187.12685687661837510000.b4-ty@kernel.org> (raw)
In-Reply-To: <20250305230007.590178-1-vinicius.gomes@intel.com>
On Wed, 05 Mar 2025 15:00:06 -0800, Vinicius Costa Gomes wrote:
> Change the "wait for operation finish" logic to take interrupts into
> account.
>
> When using dmatest with idxd DMA engine, it's possible that during
> longer tests, the interrupt notifying the finish of an operation
> happens during wait_event_freezable_timeout(), which causes dmatest to
> cleanup all the resources, some of which might still be in use.
>
> [...]
Applied, thanks!
[1/1] dmaengine: dmatest: Fix dmatest waiting less when interrupted
commit: e87ca16e99118ab4e130a41bdf12abbf6a87656c
Best regards,
--
~Vinod
next prev parent reply other threads:[~2025-03-10 21:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 23:00 [PATCH v1] dmaengine: dmatest: Fix dmatest waiting less when interrupted Vinicius Costa Gomes
2025-03-05 23:14 ` Dave Jiang
2025-03-10 21:06 ` Vinod Koul [this message]
2025-03-12 18:58 ` Nathan Lynch
2025-03-12 22:13 ` Vinicius Costa Gomes
2025-03-13 14:10 ` Nathan Lynch
2025-03-13 16:36 ` Vinicius Costa Gomes
2025-03-13 21:21 ` Nathan Lynch
2025-03-13 23:29 ` Vinicius Costa Gomes
2025-03-14 21:35 ` Nathan Lynch
2025-03-14 22:24 ` Vinicius Costa Gomes
2025-04-02 13:45 ` Nathan Lynch
2025-04-03 3:44 ` Vinicius Costa Gomes
2025-04-03 16:24 ` Nathan Lynch
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=174164080219.489187.12685687661837510000.b4-ty@kernel.org \
--to=vkoul@kernel.org \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=kristen.c.accardi@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.sang@intel.com \
--cc=vinicius.gomes@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox