From: kernel test robot <lkp@intel.com>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: oe-kbuild-all@lists.linux.dev
Subject: [glemco:staging_rv_hybrid_automata 21/21] kernel/trace/rv/monitors/boost/boost.c:143:13: error: conflicting types for 'handle_syscall'; have 'void(void *, struct pt_regs *, long int)'
Date: Sat, 6 Dec 2025 14:44:22 +0800 [thread overview]
Message-ID: <202512061442.QCS58bku-lkp@intel.com> (raw)
tree: https://git.kernel.org/pub/scm/linux/kernel/git/gmonaco/linux.git staging_rv_hybrid_automata
head: b0f3d844e192c90aac9dc773e82b8ee2b00e431b
commit: b0f3d844e192c90aac9dc773e82b8ee2b00e431b [21/21] rv: Add dl_server specific monitors
config: um-allyesconfig (https://download.01.org/0day-ci/archive/20251206/202512061442.QCS58bku-lkp@intel.com/config)
compiler: gcc-14 (Debian 14.2.0-19) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20251206/202512061442.QCS58bku-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/202512061442.QCS58bku-lkp@intel.com/
All errors (new ones prefixed by >>):
>> kernel/trace/rv/monitors/boost/boost.c:143:13: error: conflicting types for 'handle_syscall'; have 'void(void *, struct pt_regs *, long int)'
143 | static void handle_syscall(void *data, struct pt_regs *regs, long id)
| ^~~~~~~~~~~~~~
In file included from arch/x86/um/asm/elf.h:9,
from arch/um/include/asm/uaccess.h:10,
from include/linux/uaccess.h:13,
from include/linux/sched/task.h:13,
from include/linux/sched/signal.h:9,
from include/linux/rcuwait.h:6,
from include/linux/mm.h:36,
from include/linux/kallsyms.h:13,
from include/linux/ftrace.h:13,
from kernel/trace/rv/monitors/boost/boost.c:2:
arch/um/include/shared/skas/skas.h:14:13: note: previous declaration of 'handle_syscall' with type 'void(struct uml_pt_regs *)'
14 | extern void handle_syscall(struct uml_pt_regs *regs);
| ^~~~~~~~~~~~~~
vim +143 kernel/trace/rv/monitors/boost/boost.c
142
> 143 static void handle_syscall(void *data, struct pt_regs *regs, long id)
144 {
145 struct sched_dl_entity *dl_se;
146 struct task_struct *p;
147 int new_policy = -1;
148
149 new_policy = extract_params(regs, id, &p);
150 if (new_policy < 0 || new_policy == p->policy)
151 return;
152 dl_se = get_fair_server(p);
153 if (!dl_se || !p->on_rq)
154 return;
155 /*
156 * Note: this attaches to the syscall entry and is unstable:
157 * - the syscall may fail
158 * - the task may be preempted before changing the policy
159 * A more robust solution can be written using enqueue/dequeue events.
160 */
161 if (p->policy == SCHED_NORMAL)
162 da_handle_event(EXPAND_ID(dl_se, task_cpu(p)), sched_switch_out_boost);
163 else if (new_policy == SCHED_NORMAL)
164 da_handle_event(EXPAND_ID(dl_se, task_cpu(p)), dl_server_resume_boost);
165 }
166
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
reply other threads:[~2025-12-06 6:44 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=202512061442.QCS58bku-lkp@intel.com \
--to=lkp@intel.com \
--cc=gmonaco@redhat.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.