From: kernel test robot <lkp@intel.com>
To: Hen Alon <halon@habana.ai>
Cc: oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Oded Gabbay <ogabbay@kernel.org>
Subject: [linux-next:master 5393/6975] drivers/accel/habanalabs/common/habanalabs_ioctl.c:323:30: error: implicit declaration of function 'rdtsc'
Date: Thu, 21 Sep 2023 16:20:49 +0800 [thread overview]
Message-ID: <202309211608.K2NtoA7e-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
head: 940fcc189c51032dd0282cbee4497542c982ac59
commit: 809a1971ce613ec22314ecfeb3ebccc7ee3a97c3 [5393/6975] accel/habanalabs: add tsc clock sampling to clock sync info
config: um-randconfig-r005-20230815 (https://download.01.org/0day-ci/archive/20230921/202309211608.K2NtoA7e-lkp@intel.com/config)
compiler: gcc-11 (Debian 11.3.0-12) 11.3.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230921/202309211608.K2NtoA7e-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/202309211608.K2NtoA7e-lkp@intel.com/
All errors (new ones prefixed by >>):
drivers/accel/habanalabs/common/habanalabs_ioctl.c: In function 'time_sync_info':
>> drivers/accel/habanalabs/common/habanalabs_ioctl.c:323:30: error: implicit declaration of function 'rdtsc' [-Werror=implicit-function-declaration]
323 | time_sync.tsc_time = rdtsc();
| ^~~~~
cc1: some warnings being treated as errors
vim +/rdtsc +323 drivers/accel/habanalabs/common/habanalabs_ioctl.c
311
312 static int time_sync_info(struct hl_device *hdev, struct hl_info_args *args)
313 {
314 struct hl_info_time_sync time_sync = {0};
315 u32 max_size = args->return_size;
316 void __user *out = (void __user *) (uintptr_t) args->return_pointer;
317
318 if ((!max_size) || (!out))
319 return -EINVAL;
320
321 time_sync.device_time = hdev->asic_funcs->get_device_time(hdev);
322 time_sync.host_time = ktime_get_raw_ns();
> 323 time_sync.tsc_time = rdtsc();
324
325 return copy_to_user(out, &time_sync,
326 min((size_t) max_size, sizeof(time_sync))) ? -EFAULT : 0;
327 }
328
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2023-09-21 8:21 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:
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=202309211608.K2NtoA7e-lkp@intel.com \
--to=lkp@intel.com \
--cc=halon@habana.ai \
--cc=linux-mm@kvack.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=ogabbay@kernel.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).