From: Thomas Monjalon <thomas@monjalon.net>
To: Hajkowski <marcinx.hajkowski@intel.com>
Cc: dev@dpdk.org, david.hunt@intel.com, stable@dpdk.org,
Anatoly Burakov <anatoly.burakov@intel.com>
Subject: Re: [dpdk-dev] [PATCH] power: fix non thread-safe power env modification
Date: Mon, 22 Apr 2019 22:22:46 +0200 [thread overview]
Message-ID: <4859003.QxBCNikWM7@xps> (raw)
In-Reply-To: <20190405143535.2028-1-marcinx.hajkowski@intel.com>
05/04/2019 16:35, Hajkowski:
> From: Marcin Hajkowski <marcinx.hajkowski@intel.com>
>
> Due to lack of thread safety in exisiting solution
> use spinlock mechanism for atomic
> modification of power environment related data.
>
> Fixes: 445c6528b5 ("power: common interface for guest and host")
> Cc: stable@dpdk.org
>
> Signed-off-by: Marcin Hajkowski <marcinx.hajkowski@intel.com>
> Acked-by: Anatoly Burakov <anatoly.burakov@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-04-22 20:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 11:56 [PATCH v2 1/4] power: fix non thread-safe power env modification Hajkowski
2019-03-18 11:56 ` [PATCH v2 2/4] power: return error in set env when power env already set Hajkowski
2019-03-19 10:57 ` Burakov, Anatoly
2019-03-18 11:56 ` [PATCH v2 3/4] power: reset function pointers on unset env Hajkowski
2019-03-19 10:58 ` Burakov, Anatoly
2019-03-18 11:56 ` [PATCH v2 4/4] power: add UTs for all power env types Hajkowski
2019-03-19 11:58 ` Burakov, Anatoly
2019-03-18 15:01 ` [PATCH v2 1/4] power: fix non thread-safe power env modification Stephen Hemminger
2019-03-19 10:57 ` Burakov, Anatoly
2019-03-29 14:14 ` [dpdk-stable] " Thomas Monjalon
2019-03-29 15:09 ` Burakov, Anatoly
2020-10-25 18:22 ` [dpdk-dev] " Thomas Monjalon
2020-10-28 13:53 ` David Hunt
2020-10-28 14:16 ` Thomas Monjalon
2019-04-05 14:35 ` [dpdk-dev] [PATCH] " Hajkowski
2019-04-22 20:22 ` Thomas Monjalon [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=4859003.QxBCNikWM7@xps \
--to=thomas@monjalon.net \
--cc=anatoly.burakov@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.