From: kernel test robot <lkp@intel.com>
To: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@linux.intel.com>
Cc: kbuild-all@lists.01.org, linux-kernel@vger.kernel.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Tony Luck <tony.luck@intel.com>, Andi Kleen <ak@linux.intel.com>
Subject: [intel-tdx:tdx/guest-rebased 55/133] arch/x86/kernel/tdx.c:224:5: warning: no previous prototype for 'tdx_hcall_set_notify_intr'
Date: Fri, 14 Jan 2022 02:04:09 +0800 [thread overview]
Message-ID: <202201140147.8KQUVLdd-lkp@intel.com> (raw)
tree: https://github.com/intel/tdx.git tdx/guest-rebased
head: e3995864d37c56f431c93fc3dc454d9c65f5e9ea
commit: eff3229d99a6ea4b75fa0656fca38ac6db67ca7d [55/133] x86/tdx: Add SetupEventNotifyInterrupt TDX hypercall support
config: x86_64-allyesconfig (https://download.01.org/0day-ci/archive/20220114/202201140147.8KQUVLdd-lkp@intel.com/config)
compiler: gcc-9 (Debian 9.3.0-22) 9.3.0
reproduce (this is a W=1 build):
# https://github.com/intel/tdx/commit/eff3229d99a6ea4b75fa0656fca38ac6db67ca7d
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx tdx/guest-rebased
git checkout eff3229d99a6ea4b75fa0656fca38ac6db67ca7d
# save the config file to linux build tree
mkdir build_dir
make W=1 O=build_dir ARCH=x86_64 SHELL=/bin/bash arch/x86/kernel/
If you fix the issue, kindly add following tag as appropriate
Reported-by: kernel test robot <lkp@intel.com>
All warnings (new ones prefixed by >>):
>> arch/x86/kernel/tdx.c:224:5: warning: no previous prototype for 'tdx_hcall_set_notify_intr' [-Wmissing-prototypes]
224 | int tdx_hcall_set_notify_intr(u8 vector)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
vim +/tdx_hcall_set_notify_intr +224 arch/x86/kernel/tdx.c
216
217 /*
218 * tdx_hcall_set_notify_intr() - Setup Event Notify Interrupt Vector.
219 *
220 * @vector : Vector address to be used for notification.
221 *
222 * return 0 on success or failure error number.
223 */
> 224 int tdx_hcall_set_notify_intr(u8 vector)
225 {
226 u64 ret;
227
228 /* Minimum vector value allowed is 32 */
229 if (vector < 32)
230 return -EINVAL;
231
232 /*
233 * Register callback vector address with VMM. More details
234 * about the ABI can be found in TDX Guest-Host-Communication
235 * Interface (GHCI), sec 3.5.
236 */
237 ret = _trace_tdx_hypercall(TDVMCALL_SETUP_NOTIFY_INTR, vector, 0, 0, 0,
238 NULL);
239
240 if (ret == TDVMCALL_SUCCESS)
241 return 0;
242 else if (ret == TDCALL_INVALID_OPERAND)
243 return -EINVAL;
244
245 return -EIO;
246 }
247
---
0-DAY CI Kernel Test Service, Intel Corporation
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org
reply other threads:[~2022-01-13 18:05 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=202201140147.8KQUVLdd-lkp@intel.com \
--to=lkp@intel.com \
--cc=ak@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=tony.luck@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
Powered by JetHome