From: kernel test robot <lkp@intel.com>
To: "Joel Fernandes (Google)" <joel@joelfernandes.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
Suleiman Souhlal <suleiman@google.com>,
Aashish Sharma <shraash@google.com>,
Shin Kawamura <kawasin@google.com>,
Vineeth Remanan Pillai <vineeth@bitbyteword.org>
Subject: Re: [PATCH] dl_server: Reset DL server params when rd changes
Date: Thu, 31 Oct 2024 01:06:10 +0800 [thread overview]
Message-ID: <202410310046.qSHsY4dH-lkp@intel.com> (raw)
In-Reply-To: <20241029225116.3998487-1-joel@joelfernandes.org>
Hi Joel,
kernel test robot noticed the following build errors:
[auto build test ERROR on tip/sched/core]
[also build test ERROR on linus/master v6.12-rc5 next-20241030]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Joel-Fernandes-Google/dl_server-Reset-DL-server-params-when-rd-changes/20241030-065241
base: tip/sched/core
patch link: https://lore.kernel.org/r/20241029225116.3998487-1-joel%40joelfernandes.org
patch subject: [PATCH] dl_server: Reset DL server params when rd changes
config: arm-allnoconfig (https://download.01.org/0day-ci/archive/20241031/202410310046.qSHsY4dH-lkp@intel.com/config)
compiler: clang version 20.0.0git (https://github.com/llvm/llvm-project 639a7ac648f1e50ccd2556e17d401c04f9cce625)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241031/202410310046.qSHsY4dH-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/202410310046.qSHsY4dH-lkp@intel.com/
All errors (new ones prefixed by >>):
In file included from kernel/sched/build_policy.c:19:
In file included from include/linux/sched/isolation.h:5:
In file included from include/linux/cpuset.h:17:
In file included from include/linux/mm.h:2213:
include/linux/vmstat.h:518:36: warning: arithmetic between different enumeration types ('enum node_stat_item' and 'enum lru_list') [-Wenum-enum-conversion]
518 | return node_stat_name(NR_LRU_BASE + lru) + 3; // skip "nr_"
| ~~~~~~~~~~~ ^ ~~~
In file included from kernel/sched/build_policy.c:60:
>> kernel/sched/deadline.c:1631:40: error: no member named 'rd' in 'struct rq'
1631 | struct root_domain *rd = cpu_rq(cpu)->rd;
| ~~~~~~~~~~~ ^
1 warning and 1 error generated.
vim +1631 kernel/sched/deadline.c
1626
1627 void dl_server_start(struct sched_dl_entity *dl_se)
1628 {
1629 struct rq *rq = dl_se->rq;
1630 int cpu = cpu_of(rq);
> 1631 struct root_domain *rd = cpu_rq(cpu)->rd;
1632
1633 /*
1634 * XXX: the apply do not work fine at the init phase for the
1635 * fair server because things are not yet set. We need to improve
1636 * this before getting generic.
1637 */
1638 if (!dl_server(dl_se) || dl_se->last_rd != rd) {
1639 u64 runtime = 50 * NSEC_PER_MSEC;
1640 u64 period = 1000 * NSEC_PER_MSEC;
1641
1642 dl_se->last_rd = rd;
1643 dl_server_apply_params(dl_se, runtime, period, 1);
1644
1645 if (!dl_server(dl_se)) {
1646 dl_se->dl_server = 1;
1647 dl_se->dl_defer = 1;
1648 setup_new_dl_entity(dl_se);
1649 }
1650 }
1651
1652 if (!dl_se->dl_runtime)
1653 return;
1654
1655 enqueue_dl_entity(dl_se, ENQUEUE_WAKEUP);
1656 if (!dl_task(dl_se->rq->curr) || dl_entity_preempt(dl_se, &rq->curr->dl))
1657 resched_curr(dl_se->rq);
1658 }
1659
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
prev parent reply other threads:[~2024-10-30 17:06 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 22:51 [PATCH] dl_server: Reset DL server params when rd changes Joel Fernandes (Google)
2024-10-30 14:30 ` Juri Lelli
2024-10-30 19:50 ` Joel Fernandes
2024-11-04 10:54 ` Juri Lelli
2024-11-04 17:41 ` Joel Fernandes
2024-11-06 16:08 ` Juri Lelli
2024-11-06 18:05 ` Waiman Long
2024-11-08 4:40 ` Waiman Long
2024-11-08 10:40 ` Juri Lelli
2024-11-09 3:30 ` Waiman Long
2024-11-09 18:18 ` Waiman Long
2024-11-11 9:37 ` Juri Lelli
2024-11-11 12:24 ` Juri Lelli
2024-10-30 15:54 ` kernel test robot
2024-10-30 17:06 ` kernel test robot [this message]
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=202410310046.qSHsY4dH-lkp@intel.com \
--to=lkp@intel.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=kawasin@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=shraash@google.com \
--cc=suleiman@google.com \
--cc=vincent.guittot@linaro.org \
--cc=vineeth@bitbyteword.org \
--cc=vschneid@redhat.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