From: Thomas Monjalon <thomas@monjalon.net>
To: "Hunt, David" <david.hunt@intel.com>
Cc: dev@dpdk.org, "Yao, Lei A" <lei.a.yao@intel.com>
Subject: Re: [PATCH] examples/power: fix wrong core_id with JSON cmds
Date: Tue, 15 Jan 2019 00:15:51 +0100 [thread overview]
Message-ID: <3764870.CNDs0HdWOl@xps> (raw)
In-Reply-To: <2DBBFF226F7CF64BAFCA79B681719D95496070BB@shsmsx102.ccr.corp.intel.com>
> > >> This patch fixes a bug introduced in the 64-core limtation
> > >> enhancement where the core_id is inadvertently converted from
> > >> virtual to physical even though it may already be a physical
> > >> core_id.
> > >>
> > >> We should be using the core_type field, and only converting via
> > >> hypervisor when core_type is set to CORE_TYPE_VIRTUAL
> > >>
> > >> Fixes: 5776b7a371d1 ("examples/power: allow VM to use lcores over 63")
> > >>
> > >> Signed-off-by: David Hunt <david.hunt@intel.com>
> Reviewed-by: Lei Yao<lei.a.yao@intel.com>
> Tested-by: Lei Yao<lei.a.yao@intel.com>
Applied, thanks
prev parent reply other threads:[~2019-01-14 23:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 11:39 [PATCH] examples/power: fix wrong core_id with JSON cmds David Hunt
2019-01-08 2:02 ` Yao, Lei A
2019-01-08 9:20 ` Hunt, David
2019-01-08 12:47 ` Yao, Lei A
2019-01-14 23:15 ` 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=3764870.CNDs0HdWOl@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@dpdk.org \
--cc=lei.a.yao@intel.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 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.