From: leonid.ravich@dell.com
To: dmaengine@vger.kernel.org
Cc: lravich@gmail.com, Leonid Ravich <Leonid.Ravich@dell.com>,
Dan Williams <dan.j.williams@intel.com>,
Vinod Koul <vkoul@kernel.org>, Dave Jiang <dave.jiang@intel.com>,
Allison Randal <allison@lohutok.net>,
Alexios Zavras <alexios.zavras@intel.com>,
Thomas Gleixner <tglx@linutronix.de>,
"Alexander.Barabash@dell.com" <Alexander.Barabash@dell.com>,
linux-kernel@vger.kernel.org
Subject: [PATCH 3/3] dmaengine: ioat: adding missed issue_pending to timeout handler
Date: Wed, 22 Apr 2020 14:22:07 +0300 [thread overview]
Message-ID: <1587554529-29839-3-git-send-email-leonid.ravich@dell.com> (raw)
In-Reply-To: <1587554529-29839-1-git-send-email-leonid.ravich@dell.com>
From: Leonid Ravich <Leonid.Ravich@emc.com>
completion timeout might trigger unnesesery DMA engine hw reboot
in case of missed issue_pending() .
Signed-off-by: Leonid Ravich <Leonid.Ravich@emc.com>
---
drivers/dma/ioat/dma.c | 7 +++++++
1 file changed, 7 insertions(+)
diff --git a/drivers/dma/ioat/dma.c b/drivers/dma/ioat/dma.c
index 55a8cf1..2ab07a3 100644
--- a/drivers/dma/ioat/dma.c
+++ b/drivers/dma/ioat/dma.c
@@ -955,6 +955,13 @@ void ioat_timer_event(struct timer_list *t)
goto unlock_out;
}
+ /* handle missed issue pending case */
+ if (ioat_ring_pending(ioat_chan)) {
+ spin_lock_bh(&ioat_chan->prep_lock);
+ __ioat_issue_pending(ioat_chan);
+ spin_unlock_bh(&ioat_chan->prep_lock);
+ }
+
set_bit(IOAT_COMPLETION_ACK, &ioat_chan->state);
mod_timer(&ioat_chan->timer, jiffies + COMPLETION_TIMEOUT);
unlock_out:
--
1.9.3
next prev parent reply other threads:[~2020-04-22 11:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 11:22 [PATCH 1/3] dmaengine: ioat: removing duplicate code from " leonid.ravich
2020-04-22 11:22 ` [PATCH 2/3] dmaengine: ioat: remove unnesesery double complition timer modification leonid.ravich
2020-04-22 11:22 ` leonid.ravich [this message]
2020-04-22 14:21 ` [PATCH 3/3] dmaengine: ioat: adding missed issue_pending to timeout handler Dave Jiang
2020-04-22 16:45 ` Ravich, Leonid
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=1587554529-29839-3-git-send-email-leonid.ravich@dell.com \
--to=leonid.ravich@dell.com \
--cc=Alexander.Barabash@dell.com \
--cc=alexios.zavras@intel.com \
--cc=allison@lohutok.net \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lravich@gmail.com \
--cc=tglx@linutronix.de \
--cc=vkoul@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®