DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: longli@linuxonhyperv.com
Cc: dev@dpdk.org, Stephen Hemminger <sthemmin@microsoft.com>,
	Jonathan Erb <jonathan.erb@banduracyber.com>,
	Long Li <longli@microsoft.com>,
	stable@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] bus/vmbus: map to the correct ring buffer addresses for the secondary process
Date: Tue, 31 Aug 2021 10:15:14 -0700	[thread overview]
Message-ID: <20210831101514.2e6d1bba@hermes.local> (raw)
In-Reply-To: <1630389404-13468-1-git-send-email-longli@linuxonhyperv.com>

On Mon, 30 Aug 2021 22:56:44 -0700
longli@linuxonhyperv.com wrote:

> From: Long Li <longli@microsoft.com>
> 
> The driver code had wrong assumption that all the addresses to ring buffers
> in the secondary process are the same as those in the primary process. This
> is not always correct as the channels could be mapped to different
> addresses in the secondary process.
> 
> Fix this by keeping track of all the mapped addresses from the primary
> process in the shared uio_res, and have second process map to the same
> addresses.
> 
> Reported-by: Jonathan Erb <jonathan.erb@banduracyber.com>
> Cc: stable@dpdk.org
> Signed-off-by: Long Li <longli@microsoft.com>

I prefer that messages not get split across lines, but this looks fine.

Fixes: 831dba47bd36 ("bus/vmbus: add Hyper-V virtual bus support")

Acked-by: Stephen Hemminger <sthemmin@microsoft.com>

      reply	other threads:[~2021-08-31 17:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-31  5:56 longli
2021-08-31 17:15 ` Stephen Hemminger [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=20210831101514.2e6d1bba@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=dev@dpdk.org \
    --cc=jonathan.erb@banduracyber.com \
    --cc=longli@linuxonhyperv.com \
    --cc=longli@microsoft.com \
    --cc=stable@dpdk.org \
    --cc=sthemmin@microsoft.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).