DPDK patches and discussions
 help / color / mirror / Atom feed
From: David Marchand <david.marchand@redhat.com>
To: Harman Kalra <hkalra@marvell.com>,
	"Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: dev <dev@dpdk.org>, Maciej Szwed <maciej.szwed@intel.com>
Subject: Re: [dpdk-dev] [PATCH v6] eal: fix: read data buffer on RTE_INTR_HANDLE_VFIO_REQ
Date: Tue, 19 Oct 2021 13:52:17 +0200	[thread overview]
Message-ID: <CAJFAV8zkoAd81nyM6LBj9NSSC+XuRG_DbK+H0iiGecu4PPu3uQ@mail.gmail.com> (raw)
In-Reply-To: <20211019100657.692706-1-maciej.szwed@intel.com>

On Tue, Oct 19, 2021 at 12:42 PM Maciej Szwed <maciej.szwed@intel.com> wrote:
>
> We should call read() on RTE_INTR_HANDLE_VFIO_REQ event
> to confirm that event.

It looks like a fix for:
Fixes: 0eb8a1c4c786 ("vfio: add request notifier interrupt")

This fix probably qualifies for backport, but this code has been like
this for a long time, with no report of a bug.
Should we backport it?

If there was no question on backporting it, I would apply it right
away, since I saw no comment from maintainers for such a long time.
I'll wait a bit more hoping to get a reply on my question on backporting.


-- 
David Marchand


  reply	other threads:[~2021-10-19 11:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 14:17 [dpdk-dev] [PATCH v2] eal: " Szwed, Maciej
2021-08-24  9:26 ` [dpdk-dev] [PATCH v3] " Maciej Szwed
2021-08-24  9:55 ` [dpdk-dev] [PATCH v4] " Maciej Szwed
2021-10-14 13:06   ` David Marchand
2021-10-19  9:51 ` [dpdk-dev] [PATCH v5] eal: fix: " Maciej Szwed
2021-10-19 10:06 ` [dpdk-dev] [PATCH v6] " Maciej Szwed
2021-10-19 11:52   ` David Marchand [this message]
2021-11-08 17:29     ` David Marchand

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=CAJFAV8zkoAd81nyM6LBj9NSSC+XuRG_DbK+H0iiGecu4PPu3uQ@mail.gmail.com \
    --to=david.marchand@redhat.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --cc=maciej.szwed@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).