From: Thomas Monjalon <thomas@monjalon.net>
To: David Hunt <david.hunt@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2 0/3] Core capabilities query
Date: Sun, 27 Oct 2019 21:16:07 +0100 [thread overview]
Message-ID: <5759818.UJqPuM4Ka9@xps> (raw)
In-Reply-To: <20190930130043.2885-1-david.hunt@intel.com>
30/09/2019 15:00, David Hunt:
> Extend guest channel and sample apps to query CPU capabilities. Useful
> when a guest wants to see if there is a high frequency/priority
> core available for heavier workloads, i.e. Intel SST-BF.
>
> The guest_cli implements an example of this via the query_cpu_caps cmd.
Applied, thanks
next prev parent reply other threads:[~2019-10-27 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 16:15 [dpdk-dev] [PATCH " Hajkowski
2019-05-30 16:15 ` [dpdk-dev] [PATCH 1/3] power: add new packet type for capabilities Hajkowski
2019-09-30 10:55 ` Daly, Lee
2019-09-30 13:00 ` [dpdk-dev] [PATCH v2 0/3] Core capabilities query David Hunt
2019-09-30 13:00 ` [dpdk-dev] [PATCH v2 1/3] power: add new packet type for capabilities David Hunt
2019-09-30 13:00 ` [dpdk-dev] [PATCH v2 2/3] examples/power_manager: send cpu capabilities on vm request David Hunt
2019-09-30 13:00 ` [dpdk-dev] [PATCH v2 3/3] examples/power_guest: send request for specified core capabilities David Hunt
2019-09-30 13:04 ` Hunt, David
2019-10-27 20:16 ` Thomas Monjalon [this message]
2019-05-30 16:15 ` [dpdk-dev] [PATCH 2/3] examples/power_manager: send cpu capabilities on vm request Hajkowski
2019-09-30 10:56 ` Daly, Lee
2019-05-30 16:15 ` [dpdk-dev] [PATCH 3/3] examples/power_guest: send request for specified core capabilities Hajkowski
2019-09-30 10:54 ` Daly, Lee
2019-09-30 12:54 ` Daly, Lee
2019-07-04 19:58 ` [dpdk-dev] [PATCH 0/3] Core capabilities query Thomas Monjalon
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=5759818.UJqPuM4Ka9@xps \
--to=thomas@monjalon.net \
--cc=david.hunt@intel.com \
--cc=dev@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).