From: kernel test robot <lkp@intel.com>
To: Srujana Challa <schalla@marvell.com>,
herbert@gondor.apana.org.au, davem@davemloft.net
Cc: kbuild-all@lists.01.org, netdev@vger.kernel.org,
linux-crypto@vger.kernel.org, kuba@kernel.org,
sgoutham@marvell.com, gakula@marvell.com, sbhatta@marvell.com,
schandran@marvell.com, pathreya@marvell.com
Subject: Re: [PATCH v8,net-next,03/12] octeontx2-af: add debugfs entries for CPT block
Date: Tue, 20 Oct 2020 02:46:18 +0800 [thread overview]
Message-ID: <202010200218.cJZv2mjr-lkp@intel.com> (raw)
In-Reply-To: <20201019114157.4347-4-schalla@marvell.com>
[-- Attachment #1: Type: text/plain, Size: 11531 bytes --]
Hi Srujana,
I love your patch! Yet something to improve:
[auto build test ERROR on ipvs/master]
[also build test ERROR on linus/master v5.9 next-20201016]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch]
url: https://github.com/0day-ci/linux/commits/Srujana-Challa/octeontx2-af-add-debugfs-entries-for-CPT-block/20201019-195132
base: https://git.kernel.org/pub/scm/linux/kernel/git/horms/ipvs.git master
config: ia64-allmodconfig (attached as .config)
compiler: ia64-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross
chmod +x ~/bin/make.cross
# https://github.com/0day-ci/linux/commit/4db4fc3ee5a5608c1ae16cc905c7ad97eecc9ded
git remote add linux-review https://github.com/0day-ci/linux
git fetch --no-tags linux-review Srujana-Challa/octeontx2-af-add-debugfs-entries-for-CPT-block/20201019-195132
git checkout 4db4fc3ee5a5608c1ae16cc905c7ad97eecc9ded
# save the attached .config to linux build tree
COMPILER_INSTALL_PATH=$HOME/0day COMPILER=gcc-9.3.0 make.cross ARCH=ia64
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All errors (new ones prefixed by >>):
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c: In function 'rvu_dbg_cpt_ae_sts_display':
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1693:33: error: 'CPT_AF_CONSTANTS1' undeclared (first use in this function); did you mean 'CPT_AF_CONSTANTS0'?
1693 | reg = rvu_read64(rvu, blkaddr, CPT_AF_CONSTANTS1);
| ^~~~~~~~~~~~~~~~~
| CPT_AF_CONSTANTS0
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1693:33: note: each undeclared identifier is reported only once for each function it appears in
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1702:34: error: implicit declaration of function 'CPT_AF_EXEX_STS' [-Werror=implicit-function-declaration]
1702 | reg = rvu_read64(rvu, blkaddr, CPT_AF_EXEX_STS(e));
| ^~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c: In function 'rvu_dbg_cpt_se_sts_display':
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1730:33: error: 'CPT_AF_CONSTANTS1' undeclared (first use in this function); did you mean 'CPT_AF_CONSTANTS0'?
1730 | reg = rvu_read64(rvu, blkaddr, CPT_AF_CONSTANTS1);
| ^~~~~~~~~~~~~~~~~
| CPT_AF_CONSTANTS0
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c: In function 'rvu_dbg_cpt_ie_sts_display':
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1765:33: error: 'CPT_AF_CONSTANTS1' undeclared (first use in this function); did you mean 'CPT_AF_CONSTANTS0'?
1765 | reg = rvu_read64(rvu, blkaddr, CPT_AF_CONSTANTS1);
| ^~~~~~~~~~~~~~~~~
| CPT_AF_CONSTANTS0
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c: In function 'rvu_dbg_cpt_engines_info_display':
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1800:33: error: 'CPT_AF_CONSTANTS1' undeclared (first use in this function); did you mean 'CPT_AF_CONSTANTS0'?
1800 | reg = rvu_read64(rvu, blkaddr, CPT_AF_CONSTANTS1);
| ^~~~~~~~~~~~~~~~~
| CPT_AF_CONSTANTS0
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1809:34: error: implicit declaration of function 'CPT_AF_EXEX_CTL2' [-Werror=implicit-function-declaration]
1809 | reg = rvu_read64(rvu, blkaddr, CPT_AF_EXEX_CTL2(e));
| ^~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1812:34: error: implicit declaration of function 'CPT_AF_EXEX_ACTIVE' [-Werror=implicit-function-declaration]
1812 | reg = rvu_read64(rvu, blkaddr, CPT_AF_EXEX_ACTIVE(e));
| ^~~~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1815:34: error: implicit declaration of function 'CPT_AF_EXEX_CTL' [-Werror=implicit-function-declaration]
1815 | reg = rvu_read64(rvu, blkaddr, CPT_AF_EXEX_CTL(e));
| ^~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c: In function 'rvu_dbg_cpt_lfs_info_display':
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1844:34: error: implicit declaration of function 'CPT_AF_LFX_CTL'; did you mean 'CPT_AF_LF_RST'? [-Werror=implicit-function-declaration]
1844 | reg = rvu_read64(rvu, blkaddr, CPT_AF_LFX_CTL(lf));
| ^~~~~~~~~~~~~~
| CPT_AF_LF_RST
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1846:34: error: implicit declaration of function 'CPT_AF_LFX_CTL2'; did you mean 'CPT_AF_LF_RST'? [-Werror=implicit-function-declaration]
1846 | reg = rvu_read64(rvu, blkaddr, CPT_AF_LFX_CTL2(lf));
| ^~~~~~~~~~~~~~~
| CPT_AF_LF_RST
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1848:34: error: implicit declaration of function 'CPT_AF_LFX_PTR_CTL'; did you mean 'CPT_AF_LF_RST'? [-Werror=implicit-function-declaration]
1848 | reg = rvu_read64(rvu, blkaddr, CPT_AF_LFX_PTR_CTL(lf));
| ^~~~~~~~~~~~~~~~~~
| CPT_AF_LF_RST
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c: In function 'rvu_dbg_cpt_err_info_display':
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1870:34: error: implicit declaration of function 'CPT_AF_FLTX_INT'; did you mean 'CPT_AF_BLK_RST'? [-Werror=implicit-function-declaration]
1870 | reg0 = rvu_read64(rvu, blkaddr, CPT_AF_FLTX_INT(0));
| ^~~~~~~~~~~~~~~
| CPT_AF_BLK_RST
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1873:34: error: implicit declaration of function 'CPT_AF_PSNX_EXE' [-Werror=implicit-function-declaration]
1873 | reg0 = rvu_read64(rvu, blkaddr, CPT_AF_PSNX_EXE(0));
| ^~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1876:34: error: implicit declaration of function 'CPT_AF_PSNX_LF' [-Werror=implicit-function-declaration]
1876 | reg0 = rvu_read64(rvu, blkaddr, CPT_AF_PSNX_LF(0));
| ^~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1878:34: error: 'CPT_AF_RVU_INT' undeclared (first use in this function); did you mean 'NPA_AF_RVU_INT'?
1878 | reg0 = rvu_read64(rvu, blkaddr, CPT_AF_RVU_INT);
| ^~~~~~~~~~~~~~
| NPA_AF_RVU_INT
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1880:34: error: 'CPT_AF_RAS_INT' undeclared (first use in this function); did you mean 'NPA_AF_RVU_INT'?
1880 | reg0 = rvu_read64(rvu, blkaddr, CPT_AF_RAS_INT);
| ^~~~~~~~~~~~~~
| NPA_AF_RVU_INT
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1882:34: error: 'CPT_AF_EXE_ERR_INFO' undeclared (first use in this function)
1882 | reg0 = rvu_read64(rvu, blkaddr, CPT_AF_EXE_ERR_INFO);
| ^~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c: In function 'rvu_dbg_cpt_pc_display':
>> drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1901:33: error: 'CPT_AF_INST_REQ_PC' undeclared (first use in this function)
1901 | reg = rvu_read64(rvu, blkaddr, CPT_AF_INST_REQ_PC);
| ^~~~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1903:33: error: 'CPT_AF_INST_LATENCY_PC' undeclared (first use in this function)
1903 | reg = rvu_read64(rvu, blkaddr, CPT_AF_INST_LATENCY_PC);
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1905:33: error: 'CPT_AF_RD_REQ_PC' undeclared (first use in this function)
1905 | reg = rvu_read64(rvu, blkaddr, CPT_AF_RD_REQ_PC);
| ^~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1907:33: error: 'CPT_AF_RD_LATENCY_PC' undeclared (first use in this function)
1907 | reg = rvu_read64(rvu, blkaddr, CPT_AF_RD_LATENCY_PC);
| ^~~~~~~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1909:33: error: 'CPT_AF_RD_UC_PC' undeclared (first use in this function)
1909 | reg = rvu_read64(rvu, blkaddr, CPT_AF_RD_UC_PC);
| ^~~~~~~~~~~~~~~
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1911:33: error: 'CPT_AF_ACTIVE_CYCLES_PC' undeclared (first use in this function); did you mean 'NPA_AF_ACTIVE_CYCLES_PC'?
1911 | reg = rvu_read64(rvu, blkaddr, CPT_AF_ACTIVE_CYCLES_PC);
| ^~~~~~~~~~~~~~~~~~~~~~~
| NPA_AF_ACTIVE_CYCLES_PC
drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c:1913:33: error: 'CPT_AF_CPTCLK_CNT' undeclared (first use in this function); did you mean 'CPT_AF_BLK_RST'?
1913 | reg = rvu_read64(rvu, blkaddr, CPT_AF_CPTCLK_CNT);
| ^~~~~~~~~~~~~~~~~
| CPT_AF_BLK_RST
cc1: some warnings being treated as errors
vim +/CPT_AF_INST_REQ_PC +1901 drivers/net/ethernet/marvell/octeontx2/af/rvu_debugfs.c
1889
1890 static int rvu_dbg_cpt_pc_display(struct seq_file *filp, void *unused)
1891 {
1892 struct rvu *rvu;
1893 int blkaddr;
1894 u64 reg;
1895
1896 rvu = filp->private;
1897 blkaddr = rvu_get_blkaddr(rvu, BLKTYPE_CPT, 0);
1898 if (blkaddr < 0)
1899 return -ENODEV;
1900
> 1901 reg = rvu_read64(rvu, blkaddr, CPT_AF_INST_REQ_PC);
1902 seq_printf(filp, "CPT instruction requests %llu\n", reg);
1903 reg = rvu_read64(rvu, blkaddr, CPT_AF_INST_LATENCY_PC);
1904 seq_printf(filp, "CPT instruction latency %llu\n", reg);
1905 reg = rvu_read64(rvu, blkaddr, CPT_AF_RD_REQ_PC);
1906 seq_printf(filp, "CPT NCB read requests %llu\n", reg);
1907 reg = rvu_read64(rvu, blkaddr, CPT_AF_RD_LATENCY_PC);
1908 seq_printf(filp, "CPT NCB read latency %llu\n", reg);
1909 reg = rvu_read64(rvu, blkaddr, CPT_AF_RD_UC_PC);
1910 seq_printf(filp, "CPT read requests caused by UC fills %llu\n", reg);
1911 reg = rvu_read64(rvu, blkaddr, CPT_AF_ACTIVE_CYCLES_PC);
1912 seq_printf(filp, "CPT active cycles pc %llu\n", reg);
1913 reg = rvu_read64(rvu, blkaddr, CPT_AF_CPTCLK_CNT);
1914 seq_printf(filp, "CPT clock count pc %llu\n", reg);
1915
1916 return 0;
1917 }
1918
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
[-- Attachment #2: .config.gz --]
[-- Type: application/gzip, Size: 61603 bytes --]
next prev parent reply other threads:[~2020-10-19 18:46 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-19 11:41 [PATCH v8,net-next,00/12] Add Support for Marvell OcteonTX2 Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,01/12] octeontx2-pf: move lmt flush to include/linux/soc Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,02/12] octeontx2-af: add mailbox interface for CPT Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,03/12] octeontx2-af: add debugfs entries for CPT block Srujana Challa
2020-10-19 18:46 ` kernel test robot [this message]
2020-10-19 19:07 ` kernel test robot
2020-10-19 11:41 ` [PATCH v8,net-next,04/12] drivers: crypto: add Marvell OcteonTX2 CPT PF driver Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,05/12] crypto: octeontx2: add mailbox communication with AF Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,06/12] crypto: octeontx2: enable SR-IOV and mailbox communication with VF Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,07/12] crypto: octeontx2: load microcode and create engine groups Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,08/12] crypto: octeontx2: add LF framework Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,09/12] crypto: octeontx2: add support to get engine capabilities Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,10/12] crypto: octeontx2: add virtual function driver support Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,11/12] crypto: octeontx2: add support to process the crypto request Srujana Challa
2020-10-19 11:41 ` [PATCH v8,net-next,12/12] crypto: octeontx2: register with linux crypto framework Srujana Challa
2020-10-19 17:56 ` [PATCH v8,net-next,00/12] Add Support for Marvell OcteonTX2 Jakub Kicinski
-- strict thread matches above, loose matches on Subject: below --
2020-10-28 14:50 Srujana Challa
2020-10-28 14:50 ` [PATCH v8,net-next,03/12] octeontx2-af: add debugfs entries for CPT block Srujana Challa
2020-10-30 16:09 ` Willem de Bruijn
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=202010200218.cJZv2mjr-lkp@intel.com \
--to=lkp@intel.com \
--cc=davem@davemloft.net \
--cc=gakula@marvell.com \
--cc=herbert@gondor.apana.org.au \
--cc=kbuild-all@lists.01.org \
--cc=kuba@kernel.org \
--cc=linux-crypto@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pathreya@marvell.com \
--cc=sbhatta@marvell.com \
--cc=schalla@marvell.com \
--cc=schandran@marvell.com \
--cc=sgoutham@marvell.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).