DPDK usage discussions
 help / color / mirror / Atom feed
From: "Xiaoping Yan (NSB)" <xiaoping.yan@nokia-sbell.com>
To: "users@dpdk.org" <users@dpdk.org>
Subject: rte_power_monitor_multi can not enter C0.2/C0.1 state (RTM transaction abort with 0)
Date: Mon, 27 Feb 2023 13:52:46 +0000	[thread overview]
Message-ID: <cf62d874ecc1443ca76095f12345c132@nokia-sbell.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1456 bytes --]


I'm trying power saving feature in my server with intel sapphire rapid CPU. With "tsx=on" kernel parameter, I have both rtm and waitpkg available in CPU flag.
I tried rte_power_monitor_multi API to monitor on multiple address, but it never enters C0.2/C0.1 state.
To find the reason I patched the code to return the transaction abort code as below:
        /* transaction abort, possible write to one of wait addresses */
        if (rc != RTE_XBEGIN_STARTED)
-               return 0;
+               return rc;
and it turn out that RTM transaction always aborted with 0 (a few times with 4 or 6 also, which I think maybe expected due to memory change of monitored addresses).
I found some explanation of the abort state here:
For abort code 0, it just say one example (CPUID used within transcation), but it seems CPUID is not used within rte_power_monitor_multi.
I also tried rte_power_pause and rte_power_monitor, both works as expected, CPU enters C0.2 state (checked by perf stat --e r20ec -C xx)

Now, I don't know why the RTM transaction aborted with 0 and don't know how to debug it.

Can anyone throw some light on this?

Thank you.

Br, Xiaoping

[-- Attachment #2: Type: text/html, Size: 5626 bytes --]

                 reply	other threads:[~2023-02-27 13:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=cf62d874ecc1443ca76095f12345c132@nokia-sbell.com \
    --to=xiaoping.yan@nokia-sbell.com \
    --cc=users@dpdk.org \


* 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).