DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Chas Williams <3chas3@gmail.com>, dev@dpdk.org
Cc: harish.patil@qlogic.com
Subject: Re: [dpdk-dev] [PATCH v2 07/10] bnx2x: Serialize access to pf2vf mailbox
Date: Fri, 30 Sep 2016 11:45:17 +0100	[thread overview]
Message-ID: <c89f141a-d607-5683-75e9-99cf1162c8b6@intel.com> (raw)
In-Reply-To: <1475144449-22176-7-git-send-email-3chas3@gmail.com>

On 9/29/2016 11:20 AM, Chas Williams wrote:
> The pf2vf mailbox can only be used by one thread at a time.
> 
> Fixes: 540a211084a7 ("bnx2x: driver core")
> 
> Signed-off-by: Chas Williams <3chas3@gmail.com>
> ---
>  drivers/net/bnx2x/bnx2x.h        |  12 +++--
>  drivers/net/bnx2x/bnx2x_ethdev.c |   2 +
>  drivers/net/bnx2x/bnx2x_vfpf.c   | 113 +++++++++++++++++++++++++++------------
>  3 files changed, 88 insertions(+), 39 deletions(-)

<...>

>  void
> @@ -379,9 +406,9 @@ bnx2x_vf_unload(struct bnx2x_softc *sc)
>  	if (vf_id > 0) {
>  		FOR_EACH_QUEUE(sc, i) {
>  			query_op = &sc->vf2pf_mbox->query[0].q_op;
> -			bnx2x_init_first_tlv(sc, &query_op->first_tlv,
> -					BNX2X_VF_TLV_TEARDOWN_Q,
> -					sizeof(*query_op));
> +			bnx2x_vf_prep(sc, &query_op->first_tlv,
> +				      BNX2X_VF_TLV_TEARDOWN_Q,
> +				      sizeof(*query_op));
>  
>  			query_op->vf_qid = i;
>  
> @@ -394,13 +421,15 @@ bnx2x_vf_unload(struct bnx2x_softc *sc)
>  			if (reply->status != BNX2X_VF_STATUS_SUCCESS)
>  				PMD_DRV_LOG(ERR,
>  					    "Bad reply for vf_q %d teardown", i);
> +
> +			bnx2x_vf_finalize(sc, &query->first_tlv);

This cause a compilation error with clang, seem a valid error:

.../drivers/net/bnx2x/bnx2x_vfpf.c(412):
	error #3656: variable "query" may be used before its value is set
        bnx2x_vf_finalize(sc, &query->first_tlv);
                               ^

  reply	other threads:[~2016-09-30 10:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-29 10:20 [dpdk-dev] [PATCH v2 01/10] bnx2x: Set cache line based on build configuration Chas Williams
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 02/10] bnx2x: Remove unused preprocessor symbols and code Chas Williams
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 03/10] bnx2x: Remove delay during device startup Chas Williams
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 04/10] bnx2x: Remove unused RX queue code Chas Williams
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 05/10] bnx2x: Restrict RX mask flags sent to the PF Chas Williams
2016-09-30 10:45   ` Ferruh Yigit
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 06/10] bnx2x: Replace macro with static function Chas Williams
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 07/10] bnx2x: Serialize access to pf2vf mailbox Chas Williams
2016-09-30 10:45   ` Ferruh Yigit [this message]
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 08/10] bnx2x: Check return codes during VF mailbox operation Chas Williams
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 09/10] bnx2x: Don't return structs Chas Williams
2016-09-29 10:20 ` [dpdk-dev] [PATCH v2 10/10] bnx2x: Merge debug register operations into headers Chas Williams
2016-09-30 18:16   ` Harish Patil
2016-09-30 10:53 ` [dpdk-dev] [PATCH v2 01/10] bnx2x: Set cache line based on build configuration Ferruh Yigit

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=c89f141a-d607-5683-75e9-99cf1162c8b6@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=3chas3@gmail.com \
    --cc=dev@dpdk.org \
    --cc=harish.patil@qlogic.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).