From: kernel test robot <lkp@intel.com>
To: Saravana Kannan <saravanak@google.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Len Brown <len.brown@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.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: oe-kbuild-all@lists.linux.dev,
Saravana Kannan <saravanak@google.com>,
Geert Uytterhoeven <geert@linux-m68k.org>,
Marek Vasut <marex@denx.de>,
Bird@google.com, Tim <Tim.Bird@sony.com>,
kernel-team@android.com, linux-pm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 5/5] PM: sleep: Spread out async kworker threads during dpm_resume*() phases
Date: Sun, 17 Nov 2024 08:34:31 +0800 [thread overview]
Message-ID: <202411170802.SnHuptE7-lkp@intel.com> (raw)
In-Reply-To: <20241114220921.2529905-6-saravanak@google.com>
Hi Saravana,
kernel test robot noticed the following build errors:
[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on rafael-pm/bleeding-edge tip/sched/core amd-pstate/linux-next amd-pstate/bleeding-edge linus/master v6.12-rc7 next-20241115]
[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/Saravana-Kannan/PM-sleep-Fix-runtime-PM-issue-in-dpm_resume/20241115-183855
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20241114220921.2529905-6-saravanak%40google.com
patch subject: [PATCH v1 5/5] PM: sleep: Spread out async kworker threads during dpm_resume*() phases
config: arm-s3c6400_defconfig (https://download.01.org/0day-ci/archive/20241117/202411170802.SnHuptE7-lkp@intel.com/config)
compiler: arm-linux-gnueabi-gcc (GCC) 14.2.0
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20241117/202411170802.SnHuptE7-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/202411170802.SnHuptE7-lkp@intel.com/
All errors (new ones prefixed by >>):
arm-linux-gnueabi-ld: kernel/power/suspend.o: in function `suspend_enter':
>> kernel/power/suspend.c:485:(.text+0x2f4): undefined reference to `sched_set_energy_aware'
>> arm-linux-gnueabi-ld: kernel/power/suspend.c:485:(.text+0x48c): undefined reference to `sched_set_energy_aware'
arm-linux-gnueabi-ld: kernel/power/suspend.c:485:(.text+0x4c0): undefined reference to `sched_set_energy_aware'
arm-linux-gnueabi-ld: kernel/power/suspend.c:485:(.text+0x4d0): undefined reference to `sched_set_energy_aware'
arm-linux-gnueabi-ld: kernel/power/suspend.o: in function `suspend_devices_and_enter':
kernel/power/suspend.c:538:(.text+0x748): undefined reference to `sched_set_energy_aware'
vim +485 kernel/power/suspend.c
401
402 /**
403 * suspend_enter - Make the system enter the given sleep state.
404 * @state: System sleep state to enter.
405 * @wakeup: Returns information that the sleep state should not be re-entered.
406 *
407 * This function should be called after devices have been suspended.
408 */
409 static int suspend_enter(suspend_state_t state, bool *wakeup)
410 {
411 int error;
412
413 error = platform_suspend_prepare(state);
414 if (error)
415 goto Platform_finish;
416
417 error = dpm_suspend_late(PMSG_SUSPEND);
418 if (error) {
419 pr_err("late suspend of devices failed\n");
420 goto Platform_finish;
421 }
422 error = platform_suspend_prepare_late(state);
423 if (error)
424 goto Devices_early_resume;
425
426 error = dpm_suspend_noirq(PMSG_SUSPEND);
427 if (error) {
428 pr_err("noirq suspend of devices failed\n");
429 goto Platform_early_resume;
430 }
431 error = platform_suspend_prepare_noirq(state);
432 if (error)
433 goto Platform_wake;
434
435 if (suspend_test(TEST_PLATFORM))
436 goto Platform_wake;
437
438 if (state == PM_SUSPEND_TO_IDLE) {
439 s2idle_loop();
440 goto Platform_wake;
441 }
442
443 error = pm_sleep_disable_secondary_cpus();
444 if (error || suspend_test(TEST_CPUS))
445 goto Enable_cpus;
446
447 arch_suspend_disable_irqs();
448 BUG_ON(!irqs_disabled());
449
450 system_state = SYSTEM_SUSPEND;
451
452 error = syscore_suspend();
453 if (!error) {
454 *wakeup = pm_wakeup_pending();
455 if (!(suspend_test(TEST_CORE) || *wakeup)) {
456 trace_suspend_resume(TPS("machine_suspend"),
457 state, true);
458 error = suspend_ops->enter(state);
459 trace_suspend_resume(TPS("machine_suspend"),
460 state, false);
461 } else if (*wakeup) {
462 error = -EBUSY;
463 }
464 syscore_resume();
465 }
466
467 system_state = SYSTEM_RUNNING;
468
469 arch_suspend_enable_irqs();
470 BUG_ON(irqs_disabled());
471
472 Enable_cpus:
473 pm_sleep_enable_secondary_cpus();
474
475 Platform_wake:
476 platform_resume_noirq(state);
477 /*
478 * We do this only for resume instead of suspend and resume for these
479 * reasons:
480 * - Performance is more important than power for resume.
481 * - Power spent entering suspend is more important for suspend. Also,
482 * stangely, disabling EAS was making suspent a few milliseconds
483 * slower in my testing.
484 */
> 485 sched_set_energy_aware(0);
486 dpm_resume_noirq(PMSG_RESUME);
487
488 Platform_early_resume:
489 platform_resume_early(state);
490
491 Devices_early_resume:
492 dpm_resume_early(PMSG_RESUME);
493
494 Platform_finish:
495 platform_resume_finish(state);
496 return error;
497 }
498
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2024-11-17 0:35 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 22:09 [PATCH v1 0/5] Optimize async device suspend/resume Saravana Kannan
2024-11-14 22:09 ` [PATCH v1 1/5] PM: sleep: Fix runtime PM issue in dpm_resume() Saravana Kannan
2024-11-16 7:43 ` Greg Kroah-Hartman
2024-11-16 21:06 ` Saravana Kannan
2024-12-04 12:53 ` Rafael J. Wysocki
2025-03-11 10:47 ` Rafael J. Wysocki
2025-03-13 1:49 ` Saravana Kannan
2025-03-13 10:58 ` Rafael J. Wysocki
2025-03-14 20:47 ` Pavel Machek
2025-03-14 20:49 ` Saravana Kannan
2024-11-14 22:09 ` [PATCH v1 2/5] PM: sleep: Remove unnecessary mutex lock when waiting on parent Saravana Kannan
2024-12-02 20:11 ` Rafael J. Wysocki
2024-12-02 20:16 ` Rafael J. Wysocki
2024-12-02 20:46 ` Saravana Kannan
2024-12-02 21:14 ` Rafael J. Wysocki
2024-12-02 23:27 ` Saravana Kannan
2024-12-04 12:21 ` Rafael J. Wysocki
2024-11-14 22:09 ` [PATCH v1 3/5] PM: sleep: Add helper functions to loop through superior/subordinate devs Saravana Kannan
2024-11-14 22:09 ` [PATCH v1 4/5] PM: sleep: Do breadth first suspend/resume for async suspend/resume Saravana Kannan
2025-03-11 11:25 ` Geert Uytterhoeven
2024-11-14 22:09 ` [PATCH v1 5/5] PM: sleep: Spread out async kworker threads during dpm_resume*() phases Saravana Kannan
2024-11-15 5:25 ` Saravana Kannan
2024-11-15 9:25 ` Geert Uytterhoeven
2024-11-15 15:30 ` Vincent Guittot
2024-11-15 16:12 ` Vincent Guittot
2024-11-15 18:33 ` Saravana Kannan
2024-11-17 0:34 ` kernel test robot [this message]
2024-11-17 1:17 ` kernel test robot
2024-11-17 13:34 ` kernel test robot
2024-11-18 9:52 ` Christian Loehle
2024-11-18 17:18 ` Saravana Kannan
2024-11-19 4:04 ` [PATCH v1 0/5] Optimize async device suspend/resume Saravana Kannan
2024-11-19 9:51 ` Greg Kroah-Hartman
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=202411170802.SnHuptE7-lkp@intel.com \
--to=lkp@intel.com \
--cc=Bird@google.com \
--cc=Tim.Bird@sony.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@android.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=marex@denx.de \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=pavel@ucw.cz \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=rostedt@goodmis.org \
--cc=saravanak@google.com \
--cc=vincent.guittot@linaro.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