From: kernel test robot <lkp@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
intel-xe@lists.freedesktop.org,
"Piotr Piórkowski" <piotr.piorkowski@intel.com>
Subject: [drm-xe:drm-xe-next 9/10] drivers/gpu/drm/xe/xe_guc_relay.c:863:52: error: call to undeclared function 'kunit_get_current_test'; ISO C99 and later do not support implicit function declarations
Date: Sun, 7 Jan 2024 00:27:11 +0800 [thread overview]
Message-ID: <202401070036.60pNn4uZ-lkp@intel.com> (raw)
tree: https://gitlab.freedesktop.org/drm/xe/kernel.git drm-xe-next
head: cca0607b6f6a21bee68c092ed7ad9f3322e54523
commit: 27b717bac93fb9a28f37ba17f3f4aa220fedae21 [9/10] drm/xe/kunit: Add GuC Relay kunit tests
config: x86_64-randconfig-006-20240106 (https://download.01.org/0day-ci/archive/20240107/202401070036.60pNn4uZ-lkp@intel.com/config)
compiler: ClangBuiltLinux clang version 17.0.6 (https://github.com/llvm/llvm-project 6009708b4367171ccdbf4b5905cb6a803753fe18)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240107/202401070036.60pNn4uZ-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/202401070036.60pNn4uZ-lkp@intel.com/
Note: the drm-xe/drm-xe-next HEAD cca0607b6f6a21bee68c092ed7ad9f3322e54523 builds fine.
It only hurts bisectability.
All errors (new ones prefixed by >>):
>> drivers/gpu/drm/xe/xe_guc_relay.c:863:52: error: call to undeclared function 'kunit_get_current_test'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
863 | if (unlikely(!IS_SRIOV_VF(relay_to_xe(relay)) && !kunit_get_current_test()))
| ^
drivers/gpu/drm/xe/xe_guc_relay.c:909:52: error: call to undeclared function 'kunit_get_current_test'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
909 | if (unlikely(!IS_SRIOV_PF(relay_to_xe(relay)) && !kunit_get_current_test()))
| ^
2 errors generated.
vim +/kunit_get_current_test +863 drivers/gpu/drm/xe/xe_guc_relay.c
840
841 /**
842 * xe_guc_relay_process_guc2vf - Handle relay notification message from the GuC.
843 * @relay: the &xe_guc_relay which will handle the message
844 * @msg: message to be handled
845 * @len: length of the message (in dwords)
846 *
847 * This function will handle relay messages received from the GuC.
848 *
849 * This function is can only be used if driver is running in SR-IOV mode.
850 *
851 * Return: 0 on success or a negative error code on failure.
852 */
853 int xe_guc_relay_process_guc2vf(struct xe_guc_relay *relay, const u32 *msg, u32 len)
854 {
855 u32 rid;
856
857 relay_assert(relay, len >= GUC_HXG_MSG_MIN_LEN);
858 relay_assert(relay, FIELD_GET(GUC_HXG_MSG_0_ORIGIN, msg[0]) == GUC_HXG_ORIGIN_GUC);
859 relay_assert(relay, FIELD_GET(GUC_HXG_MSG_0_TYPE, msg[0]) == GUC_HXG_TYPE_EVENT);
860 relay_assert(relay, FIELD_GET(GUC_HXG_EVENT_MSG_0_ACTION, msg[0]) ==
861 XE_GUC_ACTION_GUC2VF_RELAY_FROM_PF);
862
> 863 if (unlikely(!IS_SRIOV_VF(relay_to_xe(relay)) && !kunit_get_current_test()))
864 return -EPERM;
865
866 if (unlikely(!relay_is_ready(relay)))
867 return -ENODEV;
868
869 if (unlikely(len < GUC2VF_RELAY_FROM_PF_EVENT_MSG_MIN_LEN))
870 return -EPROTO;
871
872 if (unlikely(len > GUC2VF_RELAY_FROM_PF_EVENT_MSG_MAX_LEN))
873 return -EMSGSIZE;
874
875 if (unlikely(FIELD_GET(GUC_HXG_EVENT_MSG_0_DATA0, msg[0])))
876 return -EPFNOSUPPORT;
877
878 rid = FIELD_GET(GUC2VF_RELAY_FROM_PF_EVENT_MSG_1_RELAY_ID, msg[1]);
879
880 return relay_process_msg(relay, PFID, rid,
881 msg + GUC2VF_RELAY_FROM_PF_EVENT_MSG_MIN_LEN,
882 len - GUC2VF_RELAY_FROM_PF_EVENT_MSG_MIN_LEN);
883 }
884
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2024-01-06 16:27 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=202401070036.60pNn4uZ-lkp@intel.com \
--to=lkp@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=llvm@lists.linux.dev \
--cc=michal.wajdeczko@intel.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=piotr.piorkowski@intel.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