From: "Zhang, RobinX" <robinx.zhang@intel.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>,
"Andrew Rybchenko" <andrew.rybchenko@oktetlabs.ru>,
"Liu, KevinX" <kevinx.liu@intel.com>
Subject: RE: [PATCH v7 5/5] ethdev: format module EEPROM for SFF-8636
Date: Wed, 25 May 2022 02:43:01 +0000 [thread overview]
Message-ID: <BN9PR11MB5529CB8FA9329E88985F4ED29BD69@BN9PR11MB5529.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAJFAV8y8SEYFYZx=16+3xBXRTM5WoUJxqy05g7TZAb_NxduK9Q@mail.gmail.com>
Hi, David
This is a good suggestion and I will adopt it, send v8. Thanks!
> -----Original Message-----
> From: David Marchand <david.marchand@redhat.com>
> Sent: Tuesday, May 24, 2022 5:04 PM
> To: Zhang, RobinX <robinx.zhang@intel.com>
> Cc: dev <dev@dpdk.org>; Thomas Monjalon <thomas@monjalon.net>;
> Andrew Rybchenko <andrew.rybchenko@oktetlabs.ru>; Liu, KevinX
> <kevinx.liu@intel.com>
> Subject: Re: [PATCH v7 5/5] ethdev: format module EEPROM for SFF-8636
>
> Hello,
>
> I see a lot of switch / case where tables could do the job.
> In any case, I'll focus only on one part of the code, that triggers a build
> warning witch clang 14 (+ ASan):
>
> On Tue, May 24, 2022 at 8:31 AM Robin Zhang <robinx.zhang@intel.com>
> wrote:
> > + /* Channel Specific Data */
> > + for (i = 0; i < MAX_CHANNEL_NUM; i++) {
> > + uint8_t rx_power_offset, tx_bias_offset;
> > + uint8_t tx_power_offset;
> > +
> > + switch (i) {
> > + case 0:
> > + rx_power_offset = SFF_8636_RX_PWR_1_OFFSET;
> > + tx_power_offset = SFF_8636_TX_PWR_1_OFFSET;
> > + tx_bias_offset = SFF_8636_TX_BIAS_1_OFFSET;
> > + break;
> > + case 1:
> > + rx_power_offset = SFF_8636_RX_PWR_2_OFFSET;
> > + tx_power_offset = SFF_8636_TX_PWR_2_OFFSET;
> > + tx_bias_offset = SFF_8636_TX_BIAS_2_OFFSET;
> > + break;
> > + case 2:
> > + rx_power_offset = SFF_8636_RX_PWR_3_OFFSET;
> > + tx_power_offset = SFF_8636_TX_PWR_3_OFFSET;
> > + tx_bias_offset = SFF_8636_TX_BIAS_3_OFFSET;
> > + break;
> > + case 3:
> > + rx_power_offset = SFF_8636_RX_PWR_4_OFFSET;
> > + tx_power_offset = SFF_8636_TX_PWR_4_OFFSET;
> > + tx_bias_offset = SFF_8636_TX_BIAS_4_OFFSET;
> > + break;
> > + }
> > + sd->scd[i].bias_cur = OFFSET_TO_U16(tx_bias_offset);
> > + sd->scd[i].rx_power = OFFSET_TO_U16(rx_power_offset);
> > + sd->scd[i].tx_power = OFFSET_TO_U16(tx_power_offset);
> > + }
>
> [15/442] Compiling C object lib/librte_ethdev.a.p/ethdev_sff_8636.c.o
> In file included from ../lib/ethdev/sff_8636.c:13:
> ../lib/ethdev/sff_common.h: In function ‘sff_8636_show_all’:
> ../lib/ethdev/sff_common.h:101:22: warning: ‘tx_power_offset’ may be
> used uninitialized [-Wmaybe-uninitialized]
> 101 | (data[offset] << 8 | data[(offset) + 1])
> | ^
> ../lib/ethdev/sff_8636.c:621:25: note: ‘tx_power_offset’ was declared here
> 621 | uint8_t tx_power_offset;
> | ^~~~~~~~~~~~~~~
> ../lib/ethdev/sff_common.h:101:22: warning: ‘tx_bias_offset’ may be used
> uninitialized [-Wmaybe-uninitialized]
> 101 | (data[offset] << 8 | data[(offset) + 1])
> | ^
> ../lib/ethdev/sff_8636.c:620:42: note: ‘tx_bias_offset’ was declared here
> 620 | uint8_t rx_power_offset, tx_bias_offset;
> | ^~~~~~~~~~~~~~
> ../lib/ethdev/sff_common.h:101:22: warning: ‘rx_power_offset’ may be
> used uninitialized [-Wmaybe-uninitialized]
> 101 | (data[offset] << 8 | data[(offset) + 1])
> | ^
> ../lib/ethdev/sff_8636.c:620:25: note: ‘rx_power_offset’ was declared here
> 620 | uint8_t rx_power_offset, tx_bias_offset;
> | ^~~~~~~~~~~~~~~
> [268/268] Linking target app/test/dpdk-test
>
>
> This is a false positive.
> This can be avoided using some tables:
>
> + const uint8_t rx_power_offset[MAX_CHANNEL_NUM] = {
> + SFF_8636_RX_PWR_1_OFFSET,
> + SFF_8636_RX_PWR_2_OFFSET,
> + SFF_8636_RX_PWR_3_OFFSET,
> + SFF_8636_RX_PWR_4_OFFSET,
> + };
> + const uint8_t tx_power_offset[MAX_CHANNEL_NUM] = {
> + SFF_8636_TX_PWR_1_OFFSET,
> + SFF_8636_TX_PWR_2_OFFSET,
> + SFF_8636_TX_PWR_3_OFFSET,
> + SFF_8636_TX_PWR_4_OFFSET,
> + };
> + const uint8_t tx_bias_offset[MAX_CHANNEL_NUM] = {
> + SFF_8636_TX_BIAS_1_OFFSET,
> + SFF_8636_TX_BIAS_2_OFFSET,
> + SFF_8636_TX_BIAS_3_OFFSET,
> + SFF_8636_TX_BIAS_4_OFFSET,
> + };
> + sd->scd[i].bias_cur = OFFSET_TO_U16(tx_bias_offset[i]);
> + sd->scd[i].rx_power = OFFSET_TO_U16(rx_power_offset[i]);
> + sd->scd[i].tx_power = OFFSET_TO_U16(tx_power_offset[i]);
>
>
> --
> David Marchand
next prev parent reply other threads:[~2022-05-25 2:43 UTC|newest]
Thread overview: 77+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-15 10:18 [PATCH] app/testpmd: format dump information of module EEPROM Robin Zhang
2022-02-15 13:28 ` Ferruh Yigit
2022-02-15 15:07 ` Thomas Monjalon
2022-02-16 2:26 ` Zhang, RobinX
2022-02-16 8:03 ` David Marchand
2022-02-16 8:45 ` Thomas Monjalon
2022-02-16 9:30 ` Bruce Richardson
2022-02-16 9:41 ` David Marchand
2022-02-16 10:02 ` Bruce Richardson
2022-02-16 10:15 ` David Marchand
2022-04-08 10:23 ` [PATCH v2] common/sff_module: add telemetry command to dump " Robin Zhang
2022-04-08 10:33 ` Bruce Richardson
2022-04-08 10:55 ` Zhang, RobinX
2022-04-08 11:00 ` Bruce Richardson
2022-04-08 11:20 ` Zhang, RobinX
2022-04-08 11:26 ` Bruce Richardson
2022-04-11 8:13 ` Zhang, RobinX
2022-04-11 9:13 ` Bruce Richardson
2022-04-13 12:13 ` Thomas Monjalon
2022-04-14 7:41 ` David Marchand
2022-04-20 7:00 ` [PATCH v3 0/5] add telemetry command for show " Robin Zhang
2022-04-20 7:00 ` [PATCH v3 1/5] ethdev: add telemetry command for " Robin Zhang
2022-04-20 9:16 ` Andrew Rybchenko
2022-04-20 7:00 ` [PATCH v3 2/5] ethdev: common utilities for different SFF specs Robin Zhang
2022-04-20 7:00 ` [PATCH v3 3/5] ethdev: format module EEPROM for SFF-8079 Robin Zhang
2022-04-20 7:00 ` [PATCH v3 4/5] ethdev: format module EEPROM for SFF-8472 Robin Zhang
2022-04-20 7:00 ` [PATCH v3 5/5] ethdev: format module EEPROM for SFF-8636 Robin Zhang
2022-04-20 8:49 ` [PATCH v3 0/5] add telemetry command for show module EEPROM Morten Brørup
2022-04-25 5:34 ` [PATCH v4 " Robin Zhang
2022-04-25 5:34 ` [PATCH v4 1/5] ethdev: add telemetry command for " Robin Zhang
2022-04-25 5:34 ` [PATCH v4 2/5] ethdev: common utilities for different SFF specs Robin Zhang
2022-04-25 5:34 ` [PATCH v4 3/5] ethdev: format module EEPROM for SFF-8079 Robin Zhang
2022-04-25 5:34 ` [PATCH v4 4/5] ethdev: format module EEPROM for SFF-8472 Robin Zhang
2022-04-25 5:34 ` [PATCH v4 5/5] ethdev: format module EEPROM for SFF-8636 Robin Zhang
2022-04-26 2:43 ` [PATCH v5 0/5] add telemetry command for show module EEPROM Robin Zhang
2022-04-26 2:43 ` [PATCH v5 1/5] ethdev: add telemetry command for " Robin Zhang
2022-05-04 10:16 ` Andrew Rybchenko
2022-04-26 2:43 ` [PATCH v5 2/5] ethdev: common utilities for different SFF specs Robin Zhang
2022-04-26 2:43 ` [PATCH v5 3/5] ethdev: format module EEPROM for SFF-8079 Robin Zhang
2022-04-26 2:43 ` [PATCH v5 4/5] ethdev: format module EEPROM for SFF-8472 Robin Zhang
2022-04-26 2:43 ` [PATCH v5 5/5] ethdev: format module EEPROM for SFF-8636 Robin Zhang
2022-05-04 8:13 ` [PATCH v5 0/5] add telemetry command for show module EEPROM Andrew Rybchenko
2022-05-11 2:14 ` [PATCH v6 " Robin Zhang
2022-05-11 2:14 ` [PATCH v6 1/5] ethdev: add telemetry command for " Robin Zhang
2022-05-11 2:14 ` [PATCH v6 2/5] ethdev: common utilities for different SFF specs Robin Zhang
2022-05-11 2:14 ` [PATCH v6 3/5] ethdev: format module EEPROM for SFF-8079 Robin Zhang
2022-05-11 2:14 ` [PATCH v6 4/5] ethdev: format module EEPROM for SFF-8472 Robin Zhang
2022-05-19 8:33 ` Andrew Rybchenko
2022-05-11 2:14 ` [PATCH v6 5/5] ethdev: format module EEPROM for SFF-8636 Robin Zhang
2022-05-24 6:24 ` [PATCH v7 0/5] add telemetry command for show module EEPROM Robin Zhang
2022-05-24 6:24 ` [PATCH v7 1/5] ethdev: add telemetry command for " Robin Zhang
2022-05-24 6:24 ` [PATCH v7 2/5] ethdev: common utilities for different SFF specs Robin Zhang
2022-05-24 6:24 ` [PATCH v7 3/5] ethdev: format module EEPROM for SFF-8079 Robin Zhang
2022-05-24 6:24 ` [PATCH v7 4/5] ethdev: format module EEPROM for SFF-8472 Robin Zhang
2022-05-24 6:24 ` [PATCH v7 5/5] ethdev: format module EEPROM for SFF-8636 Robin Zhang
2022-05-24 9:03 ` David Marchand
2022-05-25 2:43 ` Zhang, RobinX [this message]
2022-05-25 3:14 ` [PATCH v8 0/5] add telemetry command for show module EEPROM Robin Zhang
2022-05-25 3:14 ` [PATCH v8 1/5] ethdev: add telemetry command for " Robin Zhang
2022-05-25 9:24 ` Andrew Rybchenko
2022-05-25 3:14 ` [PATCH v8 2/5] ethdev: common utilities for different SFF specs Robin Zhang
2022-05-25 8:51 ` Andrew Rybchenko
2022-05-25 9:40 ` Andrew Rybchenko
2022-05-25 3:14 ` [PATCH v8 3/5] ethdev: format module EEPROM for SFF-8079 Robin Zhang
2022-05-25 9:55 ` Andrew Rybchenko
2022-05-25 3:14 ` [PATCH v8 4/5] ethdev: format module EEPROM for SFF-8472 Robin Zhang
2022-05-25 11:58 ` Andrew Rybchenko
2022-05-25 3:14 ` [PATCH v8 5/5] ethdev: format module EEPROM for SFF-8636 Robin Zhang
2022-05-25 9:01 ` Andrew Rybchenko
2022-05-25 12:01 ` Andrew Rybchenko
2022-05-26 7:32 ` [PATCH v9 0/5] add telemetry command for show module EEPROM Robin Zhang
2022-05-26 7:32 ` [PATCH v9 1/5] ethdev: add telemetry command for " Robin Zhang
2022-05-26 7:32 ` [PATCH v9 2/5] ethdev: add common code for different SFF specs Robin Zhang
2022-05-26 7:32 ` [PATCH v9 3/5] ethdev: support SFF-8079 module information telemetry Robin Zhang
2022-05-26 7:32 ` [PATCH v9 4/5] ethdev: support SFF-8472 " Robin Zhang
2022-05-26 7:32 ` [PATCH v9 5/5] ethdev: support SFF-8636 " Robin Zhang
2022-05-31 14:43 ` [PATCH v9 0/5] add telemetry command for show module EEPROM Andrew Rybchenko
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=BN9PR11MB5529CB8FA9329E88985F4ED29BD69@BN9PR11MB5529.namprd11.prod.outlook.com \
--to=robinx.zhang@intel.com \
--cc=andrew.rybchenko@oktetlabs.ru \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=kevinx.liu@intel.com \
--cc=thomas@monjalon.net \
/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).