patches for DPDK stable branches
 help / color / mirror / Atom feed
From: "Xueming(Steven) Li" <xuemingl@nvidia.com>
To: Chaoyong He <chaoyong.he@corigine.com>,
	"stable@dpdk.org" <stable@dpdk.org>
Cc: "oss-drivers@corigine.com" <oss-drivers@corigine.com>,
	Long Wu <long.wu@corigine.com>,
	Peng Zhang <peng.zhang@corigine.com>
Subject: RE: [PATCH 22.11] net/nfp: fix reconfigure logic of set MAC address
Date: Sat, 16 Dec 2023 00:55:53 +0000	[thread overview]
Message-ID: <DM4PR12MB53735BD013886FF70EB86B5FA192A@DM4PR12MB5373.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20231212031136.1817003-1-chaoyong.he@corigine.com>

Hi Chaoyong,

Patch applied to 22.11 LTS branch, thanks for the backporting!

> -----Original Message-----
> From: Chaoyong He <chaoyong.he@corigine.com>
> Sent: 12/12/2023 11:12
> To: stable@dpdk.org
> Cc: oss-drivers@corigine.com; Chaoyong He <chaoyong.he@corigine.com>; Long
> Wu <long.wu@corigine.com>; Peng Zhang <peng.zhang@corigine.com>
> Subject: [PATCH 22.11] net/nfp: fix reconfigure logic of set MAC address
> 
> [ upstream commit d67022275d3b423850c629036d33fdfadeb874a8 ]
> 
> If the reconfigure API exit abnormally, the value in the config bar will not same
> with the value stored in the data structure.
> 
> Fix this by add a local variable to hold the temporary value and the logic of store it
> when no error happen.
> 
> Fixes: 2fe669f4bcd2 ("net/nfp: support MAC address change")
> 
> Signed-off-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Long Wu <long.wu@corigine.com>
> Reviewed-by: Peng Zhang <peng.zhang@corigine.com>
> ---
>  drivers/net/nfp/nfp_common.c | 12 ++++++++----
>  1 file changed, 8 insertions(+), 4 deletions(-)
> 
> diff --git a/drivers/net/nfp/nfp_common.c b/drivers/net/nfp/nfp_common.c
> index 0fa74a43e4..33613bb2b3 100644
> --- a/drivers/net/nfp/nfp_common.c
> +++ b/drivers/net/nfp/nfp_common.c
> @@ -279,7 +279,7 @@ int
>  nfp_net_set_mac_addr(struct rte_eth_dev *dev, struct rte_ether_addr
> *mac_addr)  {
>  	struct nfp_net_hw *hw;
> -	uint32_t update, ctrl;
> +	uint32_t update, new_ctrl;
> 
>  	hw = NFP_NET_DEV_PRIVATE_TO_HW(dev->data->dev_private);
>  	if ((hw->ctrl & NFP_NET_CFG_CTRL_ENABLE) && @@ -294,14 +294,18
> @@ nfp_net_set_mac_addr(struct rte_eth_dev *dev, struct rte_ether_addr
> *mac_addr)
> 
>  	/* Signal the NIC about the change */
>  	update = NFP_NET_CFG_UPDATE_MACADDR;
> -	ctrl = hw->ctrl;
> +	new_ctrl = hw->ctrl;
>  	if ((hw->ctrl & NFP_NET_CFG_CTRL_ENABLE) &&
>  	    (hw->cap & NFP_NET_CFG_CTRL_LIVE_ADDR))
> -		ctrl |= NFP_NET_CFG_CTRL_LIVE_ADDR;
> -	if (nfp_net_reconfig(hw, ctrl, update) < 0) {
> +		new_ctrl |= NFP_NET_CFG_CTRL_LIVE_ADDR;
> +
> +	if (nfp_net_reconfig(hw, new_ctrl, update) < 0) {
>  		PMD_INIT_LOG(INFO, "MAC address update failed");
>  		return -EIO;
>  	}
> +
> +	hw->ctrl = new_ctrl;
> +
>  	return 0;
>  }
> 
> --
> 2.39.1


      reply	other threads:[~2023-12-16  0:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12  3:11 Chaoyong He
2023-12-16  0:55 ` Xueming(Steven) 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=DM4PR12MB53735BD013886FF70EB86B5FA192A@DM4PR12MB5373.namprd12.prod.outlook.com \
    --to=xuemingl@nvidia.com \
    --cc=chaoyong.he@corigine.com \
    --cc=long.wu@corigine.com \
    --cc=oss-drivers@corigine.com \
    --cc=peng.zhang@corigine.com \
    --cc=stable@dpdk.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;
as well as URLs for NNTP newsgroup(s).