patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org, lei.a.yao@intel.com, stable@dpdk.org
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] examples/vm_power: fix app to respect max cpus
Date: Sun, 04 Nov 2018 21:49:37 +0100	[thread overview]
Message-ID: <3183438.eAJMS0E4RF@xps> (raw)
In-Reply-To: <20181031115032.12010-1-david.hunt@intel.com>

31/10/2018 12:50, David Hunt:
> The vm_power_manager app was not respecting the POWER_MGR_MAX_CPUS
> during initialisation, so if there were more CPUs than this value (64),
> it would lead to buffer overruns of there were more then 64 cores in
> the system.
> 
> Added in a check during init and un-init to only initialise up to
> lcore_id 63.
> 
> This raises the question as to why not simply increase the value of
> POWER_MGR_MAX_CPUS. Well, it's not that simple, as many of the APIs take
> a uint64_t as a parameter for the core mask, and this will not work for
> cores greater than 63. So some work needs to be done in the future to
> remove this limitation. For now we'll fix the memory corruption.
> 
> Also, the patch that this fixes says "allow greater than 64 cores" but
> that's not across the entire application, it's only for the out-of-band
> monitoring. I'll add a notice for an API change in the next release to
> clean this up, i.e. depricate any API calls that use masks.
> 
> Fixes: 6453b9284b64 ("examples/vm_power: allow greater than 64 cores")
> 
> Signed-off-by: David Hunt <david.hunt@intel.com>

+ Cc: stable@dpdk.org

Applied, thanks

      reply	other threads:[~2018-11-04 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-31 11:50 [dpdk-stable] " David Hunt
2018-11-04 20:49 ` 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=3183438.eAJMS0E4RF@xps \
    --to=thomas@monjalon.net \
    --cc=david.hunt@intel.com \
    --cc=dev@dpdk.org \
    --cc=lei.a.yao@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).