DPDK patches and discussions
 help / color / mirror / Atom feed
From: Long Li <longli@microsoft.com>
To: thomas <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Stephen Hemminger <sthemmin@microsoft.com>,
	 Jonathan Erb <jonathan.erb@banduracyber.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [dpdk-stable] [Patch v2] bus/vmbus: map to the correct ring buffer addresses for the secondary process
Date: Wed, 13 Oct 2021 17:42:26 +0000
Message-ID: <BY5PR21MB150676BBDFF5D5C190BDB62BCEB79@BY5PR21MB1506.namprd21.prod.outlook.com> (raw)
In-Reply-To: <1973433.8l5BURKI8a@thomas>

> Subject: Re: [dpdk-stable] [Patch v2] bus/vmbus: map to the correct ring buffer
> addresses for the secondary process
> 
> 29/09/2021 22:46, longli@linuxonhyperv.com:
> > 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.
> >
> > Fixes: 831dba47bd36 ("bus/vmbus: add Hyper-V virtual bus support")
> >
> > Reported-by: Jonathan Erb <jonathan.erb@banduracyber.com>
> > Cc: stable@dpdk.org
> > Signed-off-by: Long Li <longli@microsoft.com>
> 
> You forgot this ack from v1:
> Acked-by: Stephen Hemminger <sthemmin@microsoft.com>

Sorry, my bad.

Thank you!

> 
> Applied, thanks
> 


      reply	other threads:[~2021-10-13 17:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-29 20:46 [dpdk-dev] " longli
2021-10-13 11:55 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2021-10-13 17:42   ` Long Li [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=BY5PR21MB150676BBDFF5D5C190BDB62BCEB79@BY5PR21MB1506.namprd21.prod.outlook.com \
    --to=longli@microsoft.com \
    --cc=dev@dpdk.org \
    --cc=jonathan.erb@banduracyber.com \
    --cc=stable@dpdk.org \
    --cc=sthemmin@microsoft.com \
    --cc=thomas@monjalon.net \
    /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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror http://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ http://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git