patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Maxime Coquelin <maxime.coquelin@redhat.com>
To: Hajkowski <marcinx.hajkowski@intel.com>, david.hunt@intel.com
Cc: dev@dpdk.org, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH v3 1/4] power: fix invalid socket indicator value
Date: Fri, 22 Mar 2019 11:56:10 +0100	[thread overview]
Message-ID: <b90eb774-7e22-2a9b-0d30-ea1fac3da707@redhat.com> (raw)
In-Reply-To: <20190321105506.6656-2-marcinx.hajkowski@intel.com>



On 3/21/19 11:55 AM, Hajkowski wrote:
> From: Marcin Hajkowski <marcinx.hajkowski@intel.com>
> 
> Currently 0 is being used for not connected slot indication.
> This is not consistent with linux doc which identifies 0 as valid
> (connected) slot, thus modification was done to change it.
> 
> Fixes: cd0d5547 ("power: vm communication channels in guest")
> Cc: stable@dpdk.org
> 
> Signed-off-by: Marcin Hajkowski <marcinx.hajkowski@intel.com>
> ---
>   lib/librte_power/guest_channel.c | 12 ++++++------
>   1 file changed, 6 insertions(+), 6 deletions(-)
> 
> diff --git a/lib/librte_power/guest_channel.c b/lib/librte_power/guest_channel.c
> index c17ea46b4..9cf7d2cb2 100644
> --- a/lib/librte_power/guest_channel.c
> +++ b/lib/librte_power/guest_channel.c
> @@ -19,7 +19,7 @@
>   
>   #define RTE_LOGTYPE_GUEST_CHANNEL RTE_LOGTYPE_USER1
>   
> -static int global_fds[RTE_MAX_LCORE];
> +static int global_fds[RTE_MAX_LCORE] = { [0 ... RTE_MAX_LCORE-1] = -1 };
>   
>   int
>   guest_channel_host_connect(const char *path, unsigned int lcore_id)
> @@ -35,7 +35,7 @@ guest_channel_host_connect(const char *path, unsigned int lcore_id)
>   		return -1;
>   	}
>   	/* check if path is already open */
> -	if (global_fds[lcore_id] != 0) {
> +	if (global_fds[lcore_id] != -1) {
>   		RTE_LOG(ERR, GUEST_CHANNEL, "Channel(%u) is already open with fd %d\n",
>   				lcore_id, global_fds[lcore_id]);
>   		return -1;
> @@ -84,7 +84,7 @@ guest_channel_host_connect(const char *path, unsigned int lcore_id)
>   	return 0;
>   error:
>   	close(fd);
> -	global_fds[lcore_id] = 0;
> +	global_fds[lcore_id] = -1;
>   	return -1;
>   }
>   
> @@ -100,7 +100,7 @@ guest_channel_send_msg(struct channel_packet *pkt, unsigned int lcore_id)
>   		return -1;
>   	}
>   
> -	if (global_fds[lcore_id] == 0) {
> +	if (global_fds[lcore_id] < 0) {
>   		RTE_LOG(ERR, GUEST_CHANNEL, "Channel is not connected\n");
>   		return -1;
>   	}
> @@ -134,8 +134,8 @@ guest_channel_host_disconnect(unsigned int lcore_id)
>   				lcore_id, RTE_MAX_LCORE-1);
>   		return;
>   	}
> -	if (global_fds[lcore_id] == 0)
> +	if (global_fds[lcore_id] < 0)
>   		return;
>   	close(global_fds[lcore_id]);
> -	global_fds[lcore_id] = 0;
> +	global_fds[lcore_id] = -1;
>   }
> 

Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>

  reply	other threads:[~2019-03-22 10:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20190321105506.6656-1-marcinx.hajkowski@intel.com>
2019-03-21 10:55 ` [dpdk-stable] " Hajkowski
2019-03-22 10:56   ` Maxime Coquelin [this message]
2019-03-27 14:03   ` [dpdk-stable] [dpdk-dev] " Burakov, Anatoly
     [not found] ` <20190402082121.5472-1-marcinx.hajkowski@intel.com>
2019-04-02  8:21   ` [dpdk-stable] [PATCH v4 " Hajkowski

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=b90eb774-7e22-2a9b-0d30-ea1fac3da707@redhat.com \
    --to=maxime.coquelin@redhat.com \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=marcinx.hajkowski@intel.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).