From: David Marchand <david.marchand@redhat.com>
To: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@amd.com>
Subject: Re: [Bug 1304] l3fwd-power example fails to run with uncore options, -U -u and -i
Date: Wed, 25 Oct 2023 11:53:52 +0200 [thread overview]
Message-ID: <CAJFAV8ziFrOPZyU6qBvhR37w_DnNUG4fYhn46bQgNEw3KQCyCg@mail.gmail.com> (raw)
In-Reply-To: <bug-1304-3@http.bugs.dpdk.org/>
Hello Siva,
On Wed, Oct 25, 2023 at 11:34 AM <bugzilla@dpdk.org> wrote:
>
> Bug ID 1304
> Summary l3fwd-power example fails to run with uncore options, -U -u and -i
> Product DPDK
> Version 23.11
> Hardware All
> OS All
> Status UNCONFIRMED
> Severity normal
> Priority Normal
> Component other
> Assignee dev@dpdk.org
> Reporter karen.kelly@intel.com
> Target Milestone ---
>
> We suspect this particular commit introduces this bug, the sample app will not
> work with the -U -u and -i options.
>
> The options worked when I tried with 23.07. I also tried removing this commit
> and the options worked again.
>
> Result of git show:
>
> commit ac1edcb6621af6ff3c2b01d40e4dd6ed0527a748
> Author: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
> Date: Wed Aug 16 03:09:57 2023 -0700
>
> power: refactor uncore power management API
>
> Currently the uncore power management implementation is vendor specific.
>
> Added new vendor agnostic uncore power interface similar to rte_power
> and rename specific implementations ("rte_power_intel_uncore") to
> "power_intel_uncore" along with functions.
>
> Signed-off-by: Sivaprasad Tummala <sivaprasad.tummala@amd.com>
>
>
> DPDK Version: 23.11-rc1
> Commands:
> ./<build_target>/examples/dpdk-l3fwd-power -c 0x6 -n 1 -- -p 0x1 -P
> --config="(0,0,2)" -U
> ./<build_target>/examples/dpdk-l3fwd-power -c 0x6 -n 1 -- -p 0x1 -P
> --config="(0,0,2)" -u
> ./<build_target>/examples/dpdk-l3fwd-power -c 0x6 -n 1 -- -p 0x1 -P
> --config="(0,0,2)" -i 2
> Error:
> EAL: Error - exiting with code: 1
> Cause: Invalid L3FWD parameters
Please register to dpdk.org bugzilla, and have a look at this report.
Thanks.
--
David Marchand
next prev parent reply other threads:[~2023-10-25 9:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 9:34 bugzilla
2023-10-25 9:53 ` David Marchand [this message]
2023-10-25 11:33 ` Tummala, Sivaprasad
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=CAJFAV8ziFrOPZyU6qBvhR37w_DnNUG4fYhn46bQgNEw3KQCyCg@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=sivaprasad.tummala@amd.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 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).