[dpdk-test-report] |WARNING| pw92217 [PATCH v2 31/33] event/cnxk: add timer stats get and reset

automatic DPDK test reports
 help / color / mirror / Atom feed

From: checkpatch@dpdk.org
To: test-report@dpdk.org
Cc: <pbhagavatula@marvell.com>
Subject: [dpdk-test-report] |WARNING| pw92217 [PATCH v2 31/33] event/cnxk: add timer stats get and reset
Date: Mon, 26 Apr 2021 19:49:46 +0200 (CEST)	[thread overview]
Message-ID: <20210426174946.BCFE4121158@dpdk.org> (raw)
In-Reply-To: <20210426174441.2302-32-pbhagavatula@marvell.com>

Test-Label: checkpatch
Test-Status: WARNING
http://dpdk.org/patch/92217

_coding style issues_


WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#84: 
	--dev "0002:1e:00.0,tim_stats_ena=1"

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#105: FILE: doc/guides/eventdevs/cnxk.rst:118:
+- ``TIM enable arm/cancel statistics``

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#107: FILE: doc/guides/eventdevs/cnxk.rst:120:
+  The ``tim_stats_ena`` devargs can be used to enable arm and cancel stats of

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#112: FILE: doc/guides/eventdevs/cnxk.rst:125:
+    -a 0002:0e:00.0,tim_stats_ena=1

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#126: FILE: drivers/event/cnxk/cn10k_eventdev.c:508:
+			      CNXK_TIM_RINGS_LMT "=<int>"

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#127: FILE: drivers/event/cnxk/cn10k_eventdev.c:509:
+			      CNXK_TIM_STATS_ENA "=1");

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#137: FILE: drivers/event/cnxk/cn9k_eventdev.c:577:
+			      CNXK_TIM_RINGS_LMT "=<int>"

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#138: FILE: drivers/event/cnxk/cn9k_eventdev.c:578:
+			      CNXK_TIM_STATS_ENA "=1");

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#153: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:87:
+	[_f3][_f2][_f1] = cnxk_tim_arm_burst_##_name,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#162: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:94:
+	[_f2][_f1] = cnxk_tim_arm_tmo_tick_burst_##_name,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#169: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:99:
+	cnxk_tim_ops.arm_burst =

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#170: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:100:
+		arm_burst[tim_ring->enable_stats][tim_ring->ena_dfb][prod_flag];

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#170: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:100:
+		arm_burst[tim_ring->enable_stats][tim_ring->ena_dfb][prod_flag];

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#171: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:101:
+	cnxk_tim_ops.arm_tmo_tick_burst =

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#172: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:102:
+		arm_tmo_burst[tim_ring->enable_stats][tim_ring->ena_dfb];

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#172: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:102:
+		arm_tmo_burst[tim_ring->enable_stats][tim_ring->ena_dfb];

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#180: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:166:
+	tim_ring->enable_stats = dev->enable_stats;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#189: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:250:
+cnxk_tim_stats_get(const struct rte_event_timer_adapter *adapter,

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#192: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:253:
+	struct cnxk_tim_ring *tim_ring = adapter->data->adapter_priv;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#192: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:253:
+	struct cnxk_tim_ring *tim_ring = adapter->data->adapter_priv;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#193: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:254:
+	uint64_t bkt_cyc = cnxk_tim_cntvct() - tim_ring->ring_start_cyc;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#193: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:254:
+	uint64_t bkt_cyc = cnxk_tim_cntvct() - tim_ring->ring_start_cyc;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#196: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:257:
+		__atomic_load_n(&tim_ring->arm_cnt, __ATOMIC_RELAXED);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#199: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:260:
+		rte_reciprocal_divide_u64(bkt_cyc, &tim_ring->fast_div);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#204: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:265:
+cnxk_tim_stats_reset(const struct rte_event_timer_adapter *adapter)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#206: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:267:
+	struct cnxk_tim_ring *tim_ring = adapter->data->adapter_priv;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#206: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:267:
+	struct cnxk_tim_ring *tim_ring = adapter->data->adapter_priv;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#208: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:269:
+	__atomic_store_n(&tim_ring->arm_cnt, 0, __ATOMIC_RELAXED);

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#220: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:291:
+		cnxk_tim_ops.stats_get = cnxk_tim_stats_get;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#220: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:291:
+		cnxk_tim_ops.stats_get = cnxk_tim_stats_get;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#221: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:292:
+		cnxk_tim_ops.stats_reset = cnxk_tim_stats_reset;

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#221: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:292:
+		cnxk_tim_ops.stats_reset = cnxk_tim_stats_reset;

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#231: FILE: drivers/event/cnxk/cnxk_tim_evdev.c:318:
+	rte_kvargs_process(kvlist, CNXK_TIM_STATS_ENA, &parse_kvargs_flag,

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#244: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:39:
+#define CNXK_TIM_STATS_ENA   "tim_stats_ena"

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#244: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:39:
+#define CNXK_TIM_STATS_ENA   "tim_stats_ena"

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#251: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:42:
+#define CNXK_TIM_SP	   0x1

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#252: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:43:
+#define CNXK_TIM_MP	   0x2

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#253: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:44:
+#define CNXK_TIM_ENA_FB	   0x10

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#254: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:45:
+#define CNXK_TIM_ENA_DFB   0x20

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#255: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:46:
+#define CNXK_TIM_ENA_STATS 0x40

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#283: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:219:
+	FP(sp, 0, 0, 0, CNXK_TIM_ENA_DFB | CNXK_TIM_SP)                        \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#283: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:219:
+	FP(sp, 0, 0, 0, CNXK_TIM_ENA_DFB | CNXK_TIM_SP)                        \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#284: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:220:
+	FP(mp, 0, 0, 1, CNXK_TIM_ENA_DFB | CNXK_TIM_MP)                        \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#284: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:220:
+	FP(mp, 0, 0, 1, CNXK_TIM_ENA_DFB | CNXK_TIM_MP)                        \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#285: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:221:
+	FP(fb_sp, 0, 1, 0, CNXK_TIM_ENA_FB | CNXK_TIM_SP)                      \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#285: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:221:
+	FP(fb_sp, 0, 1, 0, CNXK_TIM_ENA_FB | CNXK_TIM_SP)                      \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#286: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:222:
+	FP(fb_mp, 0, 1, 1, CNXK_TIM_ENA_FB | CNXK_TIM_MP)                      \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#286: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:222:
+	FP(fb_mp, 0, 1, 1, CNXK_TIM_ENA_FB | CNXK_TIM_MP)                      \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#288: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:224:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB | CNXK_TIM_SP)                \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#288: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:224:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB | CNXK_TIM_SP)                \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#288: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:224:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB | CNXK_TIM_SP)                \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#290: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:226:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB | CNXK_TIM_MP)                \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#290: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:226:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB | CNXK_TIM_MP)                \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#290: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:226:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB | CNXK_TIM_MP)                \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#292: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:228:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB | CNXK_TIM_SP)                 \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#292: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:228:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB | CNXK_TIM_SP)                 \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#292: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:228:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB | CNXK_TIM_SP)                 \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#294: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:230:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB | CNXK_TIM_MP)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#294: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:230:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB | CNXK_TIM_MP)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#294: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:230:
+	   CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB | CNXK_TIM_MP)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#299: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:233:
+	FP(dfb, 0, 0, CNXK_TIM_ENA_DFB)                                        \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#300: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:234:
+	FP(fb, 0, 1, CNXK_TIM_ENA_FB)                                          \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#301: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:235:
+	FP(stats_dfb, 1, 0, CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB)             \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#301: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:235:
+	FP(stats_dfb, 1, 0, CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_DFB)             \

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#302: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:236:
+	FP(stats_fb, 1, 1, CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB)

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#302: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:236:
+	FP(stats_fb, 1, 1, CNXK_TIM_ENA_STATS | CNXK_TIM_ENA_FB)

WARNING:TRAILING_SEMICOLON: macros should not use a trailing semicolon
#305: FILE: drivers/event/cnxk/cnxk_tim_evdev.h:238:
+#define FP(_name, _f3, _f2, _f1, flags)                                        \
 	uint16_t cnxk_tim_arm_burst_##_name(                                   \
 		const struct rte_event_timer_adapter *adptr,                   \
 		struct rte_event_timer **tim, const uint16_t nb_timers);

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#325: FILE: drivers/event/cnxk/cnxk_tim_worker.c:89:
+	if (flags & CNXK_TIM_ENA_STATS)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#326: FILE: drivers/event/cnxk/cnxk_tim_worker.c:90:
+		__atomic_fetch_add(&tim_ring->arm_cnt, index, __ATOMIC_RELAXED);

WARNING:TYPO_SPELLING: 'TIM' may be misspelled - perhaps 'TIME'?
#340: FILE: drivers/event/cnxk/cnxk_tim_worker.c:144:
+	if (flags & CNXK_TIM_ENA_STATS)

WARNING:TYPO_SPELLING: 'tim' may be misspelled - perhaps 'time'?
#341: FILE: drivers/event/cnxk/cnxk_tim_worker.c:145:
+		__atomic_fetch_add(&tim_ring->arm_cnt, set_timers,

total: 0 errors, 71 warnings, 217 lines checked

          parent reply	other threads:[~2021-04-26 17:49 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20210426174441.2302-32-pbhagavatula@marvell.com>]

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=20210426174946.BCFE4121158@dpdk.org \
    --to=checkpatch@dpdk.org \
    --cc=pbhagavatula@marvell.com \
    --cc=test-report@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).