dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Dave Jiang <dave.jiang@intel.com>
Cc: dmaengine@vger.kernel.org, sanjay.k.kumar@intel.com
Subject: Re: [PATCH v2] dmaengine: idxd: fix interrupt completion after unmasking
Date: Mon, 4 May 2020 10:47:17 +0530	[thread overview]
Message-ID: <20200504051717.GF1375924@vkoul-mobl> (raw)
In-Reply-To: <158834641769.35613.1341160109892008587.stgit@djiang5-desk3.ch.intel.com>

On 01-05-20, 08:21, Dave Jiang wrote:
> The current implementation may miss completions after we unmask the
> interrupt. In order to make sure we process all competions, we need to:
> 1. Do an MMIO read from the device as a barrier to ensure that all PCI
>    writes for completions have arrived.
> 2. Check for any additional completions that we missed.

Applied, thanks

-- 
~Vinod

      reply	other threads:[~2020-05-04  5:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-01 15:21 [PATCH v2] dmaengine: idxd: fix interrupt completion after unmasking Dave Jiang
2020-05-04  5:17 ` Vinod Koul [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=20200504051717.GF1375924@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=sanjay.k.kumar@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;
as well as URLs for NNTP newsgroup(s).