All of lore.kernel.org
 help / color / mirror / Atom feed
From: "lihuisong (C)" <lihuisong@huawei.com>
To: <anatoly.burakov@intel.com>, <sivaprasad.tummala@amd.com>
Cc: <dev@dpdk.org>, <thomas@monjalon.net>,
	<stephen@networkplumber.org>, <fengchengwen@huawei.com>,
	<yangxingui@huawei.com>, <zhanjie9@hisilicon.com>,
	 <lihuisong@huawei.com>
Subject: Re: [PATCH v2 0/5] uncore power improvements and auto-detection
Date: Wed, 10 Jun 2026 09:33:36 +0800	[thread overview]
Message-ID: <e43698eb-e29e-4a91-a1cd-6b520595a07e@huawei.com> (raw)
In-Reply-To: <20260526081138.1434947-1-lihuisong@huawei.com>

Hi Sivaprasad,

Can you take a look at this series?
Currently, uncore core use intel_uncore driver by default on using 
AUTO_DETECT.
This series can support automatic detection of uncore driver.
After this, user don't need modify l3fwd-power to run amd_uncore driver 
on AMD platform.

/Huisong

On 5/26/2026 4:11 PM, Huisong Li wrote:
> This series improves the uncore power management in l3fwd-power
> and adds automatic detection of uncore drivers in the power library.
>
> - Fix uncore deinitialization for non-legacy modes
> - Enable power QoS for all modes (not just legacy)
> - Fix uncore help text and log messages
> - Relocate uncore initialization from arg parsing to init_power_library()
> - Support automatic probing of multiple uncore drivers in AUTO_DETECT
>
> ---
>   v2:
>   - Remove the patch which add global uncore init and deinit interface.
>   - Remove the last patch in l3fwd-power about these new interface.
>     Will send them after this series.
>   - v1 link:
>     https://inbox.dpdk.org/dev/20260512023513.460169-1-lihuisong@huawei.com/
>
> ---
>
> Huisong Li (5):
>    examples/l3fwd-power: fix uncore deinit for non-legacy
>    examples/l3fwd-power: enable power QoS for all modes
>    examples/l3fwd-power: fix uncore help and log info
>    examples/l3fwd-power: relocate uncore initialization
>    power: support automatic detection of uncore driver
>
>   doc/guides/rel_notes/release_26_07.rst        |   6 +
>   .../sample_app_ug/l3_forward_power_man.rst    |   2 +-
>   examples/l3fwd-power/main.c                   | 256 +++++++++---------
>   lib/power/rte_power_uncore.c                  |  46 +++-
>   4 files changed, 178 insertions(+), 132 deletions(-)
>

  parent reply	other threads:[~2026-06-10  1:33 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-26  8:11 [PATCH v2 0/5] uncore power improvements and auto-detection Huisong Li
2026-05-26  8:11 ` [PATCH v2 1/5] examples/l3fwd-power: fix uncore deinit for non-legacy Huisong Li
2026-07-02 11:06   ` Macnamara, Chris
2026-07-03  4:07     ` lihuisong (C)
2026-05-26  8:11 ` [PATCH v2 2/5] examples/l3fwd-power: enable power QoS for all modes Huisong Li
2026-05-26  8:11 ` [PATCH v2 3/5] examples/l3fwd-power: fix uncore help and log info Huisong Li
2026-05-26  8:11 ` [PATCH v2 4/5] examples/l3fwd-power: relocate uncore initialization Huisong Li
2026-05-26  8:11 ` [PATCH v2 5/5] power: support automatic detection of uncore driver Huisong Li
2026-06-10  1:33 ` lihuisong (C) [this message]
2026-06-29  6:23 ` [PATCH v2 0/5] uncore power improvements and auto-detection lihuisong (C)

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=e43698eb-e29e-4a91-a1cd-6b520595a07e@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=anatoly.burakov@intel.com \
    --cc=dev@dpdk.org \
    --cc=fengchengwen@huawei.com \
    --cc=sivaprasad.tummala@amd.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=yangxingui@huawei.com \
    --cc=zhanjie9@hisilicon.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.