From: kernel test robot <lkp@intel.com>
To: Ronak Doshi <ronak.doshi@broadcom.com>, netdev@vger.kernel.org
Cc: oe-kbuild-all@lists.linux.dev,
Ronak Doshi <ronak.doshi@broadcom.com>,
Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next 2/4] vmxnet3: add latency measurement support in vmxnet3
Date: Thu, 16 May 2024 07:02:46 +0800 [thread overview]
Message-ID: <202405160624.WdmYFkNm-lkp@intel.com> (raw)
In-Reply-To: <20240514182050.20931-3-ronak.doshi@broadcom.com>
Hi Ronak,
kernel test robot noticed the following build errors:
[auto build test ERROR on net-next/main]
url: https://github.com/intel-lab-lkp/linux/commits/Ronak-Doshi/vmxnet3-prepare-for-version-9-changes/20240515-023833
base: net-next/main
patch link: https://lore.kernel.org/r/20240514182050.20931-3-ronak.doshi%40broadcom.com
patch subject: [PATCH net-next 2/4] vmxnet3: add latency measurement support in vmxnet3
config: csky-randconfig-r081-20240516 (https://download.01.org/0day-ci/archive/20240516/202405160624.WdmYFkNm-lkp@intel.com/config)
compiler: csky-linux-gcc (GCC) 13.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240516/202405160624.WdmYFkNm-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202405160624.WdmYFkNm-lkp@intel.com/
All errors (new ones prefixed by >>):
In function 'vmxnet3_get_cycles',
inlined from 'vmxnet3_rq_rx_complete' at drivers/net/vmxnet3/vmxnet3_drv.c:1675:25:
>> drivers/net/vmxnet3/vmxnet3_drv.c:151:9: error: impossible constraint in 'asm'
151 | asm volatile("rdpmc" : "=a" (low), "=d" (high) : "c" (pmc));
| ^~~
vim +/asm +151 drivers/net/vmxnet3/vmxnet3_drv.c
145
146 static u64
147 vmxnet3_get_cycles(int pmc)
148 {
149 u32 low, high;
150
> 151 asm volatile("rdpmc" : "=a" (low), "=d" (high) : "c" (pmc));
152 return (low | ((u_int64_t)high << 32));
153 }
154
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-05-15 23:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-14 18:20 [PATCH net-next 0/4] vmxnet3: upgrade to version 9 Ronak Doshi
2024-05-14 18:20 ` [PATCH net-next 1/4] vmxnet3: prepare for version 9 changes Ronak Doshi
2024-05-14 18:20 ` [PATCH net-next 2/4] vmxnet3: add latency measurement support in vmxnet3 Ronak Doshi
2024-05-15 10:46 ` Simon Horman
[not found] ` <CAP1Q3XRYGySJQaWe8dvasUGmpZGcYy_g_Xgft2u=hg9R_eqEsQ@mail.gmail.com>
2024-05-20 19:19 ` Ronak Doshi
2024-05-20 20:06 ` Simon Horman
2024-05-15 23:02 ` kernel test robot [this message]
2024-05-16 1:59 ` kernel test robot
2024-05-16 3:31 ` kernel test robot
2024-05-14 18:20 ` [PATCH net-next 3/4] vmxnet3: add command to allow disabling of offloads Ronak Doshi
2024-05-15 10:47 ` Simon Horman
2024-05-14 18:20 ` [PATCH net-next 4/4] vmxnet3: update to version 9 Ronak Doshi
2024-05-15 10:49 ` Simon Horman
2024-05-15 10:52 ` [PATCH net-next 0/4] vmxnet3: upgrade " Simon Horman
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=202405160624.WdmYFkNm-lkp@intel.com \
--to=lkp@intel.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pabeni@redhat.com \
--cc=ronak.doshi@broadcom.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 read-only IMAP folder(s) and NNTP newsgroup(s).