From: kernel test robot <lkp@intel.com>
To: cros-kernel-buildreports@googlegroups.com
Cc: oe-kbuild-all@lists.linux.dev
Subject: [android-common:android14-kiwi-6.1 216/216] arch/arm64/kvm/hyp_events.c:25:20: warning: no previous prototype for 'hyp_event_trace_host_hcall'
Date: Mon, 17 Aug 2026 05:51:06 +0800 [thread overview]
Message-ID: <202608170540.5ZOV9Mna-lkp@intel.com> (raw)
Hi Vincent,
FYI, the error/warning still remains.
tree: https://android.googlesource.com/kernel/common android14-kiwi-6.1
head: 2926f30a02021448f3d5484967f2d01a4249e0c7
commit: 508af69a745a81d6fedd161b4d5d614a9d1f9788 [216/216] ANDROID: KVM: arm64: Add EL2 wakeup cause hyp events
config: arm64-randconfig-004-20260816 (https://download.01.org/0day-ci/archive/20260817/202608170540.5ZOV9Mna-lkp@intel.com/config)
compiler: aarch64-linux-gcc (GCC) 10.5.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20260817/202608170540.5ZOV9Mna-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/202608170540.5ZOV9Mna-lkp@intel.com/
All warnings (new ones prefixed by >>):
arch/arm64/kvm/hyp_events.c:25:20: warning: no previous prototype for 'hyp_event_trace_hyp_enter' [-Wmissing-prototypes]
25 | enum print_line_t hyp_event_trace_##__name(struct trace_iterator *iter, \
| ^~~~~~~~~~~~~~~~
arch/arm64/include/asm/kvm_hypevents.h:14:1: note: in expansion of macro 'HYP_EVENT'
14 | HYP_EVENT(hyp_enter,
| ^~~~~~~~~
arch/arm64/kvm/hyp_events.c:25:20: warning: no previous prototype for 'hyp_event_trace_hyp_exit' [-Wmissing-prototypes]
25 | enum print_line_t hyp_event_trace_##__name(struct trace_iterator *iter, \
| ^~~~~~~~~~~~~~~~
arch/arm64/include/asm/kvm_hypevents.h:23:1: note: in expansion of macro 'HYP_EVENT'
23 | HYP_EVENT(hyp_exit,
| ^~~~~~~~~
>> arch/arm64/kvm/hyp_events.c:25:20: warning: no previous prototype for 'hyp_event_trace_host_hcall' [-Wmissing-prototypes]
25 | enum print_line_t hyp_event_trace_##__name(struct trace_iterator *iter, \
| ^~~~~~~~~~~~~~~~
arch/arm64/include/asm/kvm_hypevents.h:32:1: note: in expansion of macro 'HYP_EVENT'
32 | HYP_EVENT(host_hcall,
| ^~~~~~~~~
>> arch/arm64/kvm/hyp_events.c:25:20: warning: no previous prototype for 'hyp_event_trace_host_smc' [-Wmissing-prototypes]
25 | enum print_line_t hyp_event_trace_##__name(struct trace_iterator *iter, \
| ^~~~~~~~~~~~~~~~
arch/arm64/include/asm/kvm_hypevents.h:46:1: note: in expansion of macro 'HYP_EVENT'
46 | HYP_EVENT(host_smc,
| ^~~~~~~~~
>> arch/arm64/kvm/hyp_events.c:25:20: warning: no previous prototype for 'hyp_event_trace_host_mem_abort' [-Wmissing-prototypes]
25 | enum print_line_t hyp_event_trace_##__name(struct trace_iterator *iter, \
| ^~~~~~~~~~~~~~~~
arch/arm64/include/asm/kvm_hypevents.h:61:1: note: in expansion of macro 'HYP_EVENT'
61 | HYP_EVENT(host_mem_abort,
| ^~~~~~~~~
arch/arm64/kvm/hyp_events.c:249:6: warning: no previous prototype for 'kvm_hyp_events_enable_early' [-Wmissing-prototypes]
249 | bool kvm_hyp_events_enable_early(void)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/arm64/kvm/hyp_events.c:284:6: warning: no previous prototype for 'kvm_hyp_init_events_tracefs' [-Wmissing-prototypes]
284 | void kvm_hyp_init_events_tracefs(struct dentry *parent)
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~
arch/arm64/kvm/hyp_events.c:323:5: warning: no previous prototype for 'kvm_hyp_init_events' [-Wmissing-prototypes]
323 | int kvm_hyp_init_events(void)
| ^~~~~~~~~~~~~~~~~~~
vim +/hyp_event_trace_host_hcall +25 arch/arm64/kvm/hyp_events.c
09014fb1f2df192 Vincent Donnefort 2023-01-26 22
09014fb1f2df192 Vincent Donnefort 2023-01-26 23 #define HYP_EVENT(__name, __proto, __struct, __assign, __printk) \
09014fb1f2df192 Vincent Donnefort 2023-01-26 24 HYP_EVENT_FORMAT(__name, __struct); \
09014fb1f2df192 Vincent Donnefort 2023-01-26 @25 enum print_line_t hyp_event_trace_##__name(struct trace_iterator *iter, \
09014fb1f2df192 Vincent Donnefort 2023-01-26 26 int flags, struct trace_event *event) \
09014fb1f2df192 Vincent Donnefort 2023-01-26 27 { \
09014fb1f2df192 Vincent Donnefort 2023-01-26 28 struct ht_iterator *ht_iter = (struct ht_iterator *)iter; \
09014fb1f2df192 Vincent Donnefort 2023-01-26 29 struct trace_hyp_format_##__name __maybe_unused *__entry = \
09014fb1f2df192 Vincent Donnefort 2023-01-26 30 (struct trace_hyp_format_##__name *)ht_iter->ent; \
09014fb1f2df192 Vincent Donnefort 2023-01-26 31 trace_seq_puts(&ht_iter->seq, #__name); \
09014fb1f2df192 Vincent Donnefort 2023-01-26 32 trace_seq_putc(&ht_iter->seq, ' '); \
09014fb1f2df192 Vincent Donnefort 2023-01-26 33 trace_seq_printf(&ht_iter->seq, __printk); \
09014fb1f2df192 Vincent Donnefort 2023-01-26 34 trace_seq_putc(&ht_iter->seq, '\n'); \
09014fb1f2df192 Vincent Donnefort 2023-01-26 35 return TRACE_TYPE_HANDLED; \
09014fb1f2df192 Vincent Donnefort 2023-01-26 36 }
09014fb1f2df192 Vincent Donnefort 2023-01-26 37 #include <asm/kvm_hypevents.h>
09014fb1f2df192 Vincent Donnefort 2023-01-26 38
:::::: The code at line 25 was first introduced by commit
:::::: 09014fb1f2df192b186cd253fa990925f262f308 ANDROID: KVM: arm64: Add support for nVHE hyp events
:::::: TO: Vincent Donnefort <vdonnefort@google.com>
:::::: CC: Vincent Donnefort <vdonnefort@google.com>
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2026-08-16 21:51 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=202608170540.5ZOV9Mna-lkp@intel.com \
--to=lkp@intel.com \
--cc=cros-kernel-buildreports@googlegroups.com \
--cc=oe-kbuild-all@lists.linux.dev \
/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.