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,
Tony Luck <tony.luck@intel.com>, Andi Kleen <ak@linux.intel.com>
Subject: [intel-tdx:guest 62/136] arch/x86/kernel/tdx.c:225:5: error: no previous prototype for 'tdx_hcall_set_notify_intr'
Date: Wed, 27 Oct 2021 22:04:31 +0800 [thread overview]
Message-ID: <202110272220.mKxh48KY-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2192 bytes --]
tree: https://github.com/intel/tdx.git guest
head: 12f4800ff5dbe89a642744796008f89f23b2e446
commit: 2c0498d3a27b537d428cc081fe9578605111569e [62/136] x86/tdx: Add SetupEventNotifyInterrupt TDX hypercall support
config: x86_64-allyesconfig (attached as .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/2c0498d3a27b537d428cc081fe9578605111569e
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest
git checkout 2c0498d3a27b537d428cc081fe9578605111569e
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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 >>):
>> arch/x86/kernel/tdx.c:225:5: error: no previous prototype for 'tdx_hcall_set_notify_intr' [-Werror=missing-prototypes]
225 | int tdx_hcall_set_notify_intr(u8 vector)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/tdx_hcall_set_notify_intr +225 arch/x86/kernel/tdx.c
217
218 /*
219 * tdx_hcall_set_notify_intr() - Setup Event Notify Interrupt Vector.
220 *
221 * @vector : Vector address to be used for notification.
222 *
223 * return 0 on success or failure error number.
224 */
> 225 int tdx_hcall_set_notify_intr(u8 vector)
226 {
227 u64 ret;
228
229 /* Minimum vector value allowed is 32 */
230 if (vector < 32)
231 return -EINVAL;
232
233 /*
234 * Register callback vector address with VMM. More details
235 * about the ABI can be found in TDX Guest-Host-Communication
236 * Interface (GHCI), sec 3.5.
237 */
238 ret = _trace_tdx_hypercall(TDVMCALL_SETUP_NOTIFY_INTR, vector, 0, 0, 0,
239 NULL);
240
241 if (ret == TDVMCALL_SUCCESS)
242 return 0;
243 else if (ret == TDCALL_INVALID_OPERAND)
244 return -EINVAL;
245
246 return -EIO;
247 }
248
---
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: 66447 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [intel-tdx:guest 62/136] arch/x86/kernel/tdx.c:225:5: error: no previous prototype for 'tdx_hcall_set_notify_intr'
Date: Wed, 27 Oct 2021 22:04:31 +0800 [thread overview]
Message-ID: <202110272220.mKxh48KY-lkp@intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2254 bytes --]
tree: https://github.com/intel/tdx.git guest
head: 12f4800ff5dbe89a642744796008f89f23b2e446
commit: 2c0498d3a27b537d428cc081fe9578605111569e [62/136] x86/tdx: Add SetupEventNotifyInterrupt TDX hypercall support
config: x86_64-allyesconfig (attached as .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/2c0498d3a27b537d428cc081fe9578605111569e
git remote add intel-tdx https://github.com/intel/tdx.git
git fetch --no-tags intel-tdx guest
git checkout 2c0498d3a27b537d428cc081fe9578605111569e
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
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 >>):
>> arch/x86/kernel/tdx.c:225:5: error: no previous prototype for 'tdx_hcall_set_notify_intr' [-Werror=missing-prototypes]
225 | int tdx_hcall_set_notify_intr(u8 vector)
| ^~~~~~~~~~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
vim +/tdx_hcall_set_notify_intr +225 arch/x86/kernel/tdx.c
217
218 /*
219 * tdx_hcall_set_notify_intr() - Setup Event Notify Interrupt Vector.
220 *
221 * @vector : Vector address to be used for notification.
222 *
223 * return 0 on success or failure error number.
224 */
> 225 int tdx_hcall_set_notify_intr(u8 vector)
226 {
227 u64 ret;
228
229 /* Minimum vector value allowed is 32 */
230 if (vector < 32)
231 return -EINVAL;
232
233 /*
234 * Register callback vector address with VMM. More details
235 * about the ABI can be found in TDX Guest-Host-Communication
236 * Interface (GHCI), sec 3.5.
237 */
238 ret = _trace_tdx_hypercall(TDVMCALL_SETUP_NOTIFY_INTR, vector, 0, 0, 0,
239 NULL);
240
241 if (ret == TDVMCALL_SUCCESS)
242 return 0;
243 else if (ret == TDCALL_INVALID_OPERAND)
244 return -EINVAL;
245
246 return -EIO;
247 }
248
---
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: 66447 bytes --]
next reply other threads:[~2021-10-27 14:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 14:04 kernel test robot [this message]
2021-10-27 14:04 ` [intel-tdx:guest 62/136] arch/x86/kernel/tdx.c:225:5: error: no previous prototype for 'tdx_hcall_set_notify_intr' kernel test robot
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=202110272220.mKxh48KY-lkp@intel.com \
--to=lkp@intel.com \
--cc=ak@linux.intel.com \
--cc=kbuild-all@lists.01.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.