Content-Type: multipart/mixed; boundary="===============5187508702511346657==" MIME-Version: 1.0 From: Steven Rostedt To: kbuild-all@lists.01.org Subject: Re: [tip:sched/fifo 44/45] ERROR: modpost: "sched_setscheduler" undefined! Date: Tue, 21 Jul 2020 09:30:10 -0400 Message-ID: <20200721093010.1c8bd787@oasis.local.home> In-Reply-To: <20200721083643.GG119549@hirez.programming.kicks-ass.net> List-Id: --===============5187508702511346657== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable On Tue, 21 Jul 2020 10:36:43 +0200 peterz(a)infradead.org wrote: > > Yeah, that's fine. You don't have any sched_fifo_high() ? = > = > Thanks! and no. > = > I'll go write a Changelog and add it to tip/sched/fifo, so that > hopefully, sfr can stop complaining about this build fail ;-) > = > I've even argued we should rename fifo_low() to something else, but > failed to come up with a sensible name. The intended case is for when > you want something above normal but don't particularly care about RT at > all. > = > The thing is, once you start adding priorities, even low,med,high, we're > back to where we were. And the whole argument is that the kernel cannot > set priorities in any sensible fashion. Actually, I was wondering about a "sched_fifo_benchmark()" used specifically for internal testing, where you *want* to disrupt the system. Perhaps have it depend on CONFIG_DEBUG to at least scare people away from using it for normal production code. Or make it print a nasty banner like trace_printk() does. That worked pretty well at keeping people from using it ;-) -- Steve --===============5187508702511346657==--