mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	linux-kernel@vger.kernel.org,
	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>,
	Daniel Bristot de Oliveira <bristot@redhat.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Borislav Petkov <bp@alien8.de>,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [GIT PULL] scheduler updates for v5.18
Date: Mon, 21 Mar 2022 08:44:52 -0700	[thread overview]
Message-ID: <YjiddAnoCCz7Tbt3@dev-arch.thelio-3990X> (raw)
In-Reply-To: <YjhZUezhnamHAl0H@gmail.com>

Hi Ingo,

On Mon, Mar 21, 2022 at 11:54:09AM +0100, Ingo Molnar wrote:
> Ingo Molnar (17):
>       sched/headers: Fix header to build standalone: <linux/sched_clock.h>
>       sched/headers: Add header guard to kernel/sched/sched.h
>       sched/headers: Add header guard to kernel/sched/stats.h and kernel/sched/autogroup.h
>       sched/headers: sched/clock: Mark all functions 'notrace', remove CC_FLAGS_FTRACE build asymmetry
>       sched/headers: Add initial new headers as identity mappings
>       sched/headers: Fix comment typo in kernel/sched/cpudeadline.c
>       sched/headers: Make the <linux/sched/deadline.h> header build standalone
>       sched/headers: Introduce kernel/sched/build_utility.c and build multiple .c files there
>       sched/headers: Introduce kernel/sched/build_policy.c and build multiple .c files there
>       sched/headers: Standardize kernel/sched/sched.h header dependencies
>       sched/headers: Reorganize, clean up and optimize kernel/sched/core.c dependencies
>       sched/headers: Reorganize, clean up and optimize kernel/sched/fair.c dependencies
>       sched/headers: Reorganize, clean up and optimize kernel/sched/build_policy.c dependencies
>       sched/headers: Reorganize, clean up and optimize kernel/sched/build_utility.c dependencies
>       sched/headers: Reorganize, clean up and optimize kernel/sched/sched.h dependencies
>       sched/headers: Only include <linux/entry-common.h> when CONFIG_GENERIC_ENTRY=y
>       headers/prep: Fix header to build standalone: <linux/psi.h>

This series regresses ARCH=arm allmodconfig:

$ make -skj"$(nproc)" ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- mrproper allmodconfig kernel/sched/
In file included from kernel/sched/fair.c:52:
kernel/sched/sched.h:87:11: fatal error: asm/paravirt_api_clock.h: No such file or directory
   87 | # include <asm/paravirt_api_clock.h>
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.build:288: kernel/sched/fair.o] Error 1
In file included from kernel/sched/core.c:81:
kernel/sched/sched.h:87:11: fatal error: asm/paravirt_api_clock.h: No such file or directory
   87 | # include <asm/paravirt_api_clock.h>
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.build:288: kernel/sched/core.o] Error 1
In file included from kernel/sched/build_policy.c:33:
kernel/sched/sched.h:87:11: fatal error: asm/paravirt_api_clock.h: No such file or directory
   87 | # include <asm/paravirt_api_clock.h>
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.build:288: kernel/sched/build_policy.o] Error 1
In file included from kernel/sched/build_utility.c:52:
kernel/sched/sched.h:87:11: fatal error: asm/paravirt_api_clock.h: No such file or directory
   87 | # include <asm/paravirt_api_clock.h>
      |           ^~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
make[3]: *** [scripts/Makefile.build:288: kernel/sched/build_utility.o] Error 1
make[3]: Target '__build' not remade because of errors.
make[2]: *** [scripts/Makefile.build:550: kernel/sched] Error 2

Randy Dunlap has sent a patch that fixes it, which I just reviewed:

https://lore.kernel.org/r/20220316204146.14000-1-rdunlap@infradead.org/

It would be nice if this could be taken with the pull (or submitted with
the pull in a v2 as I see Qian's comment) to avoid regressing the build.

Cheers,
Nathan

  parent reply	other threads:[~2022-03-21 15:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-21 10:54 Ingo Molnar
2022-03-21 13:13 ` Qian Cai
2022-03-21 23:59   ` Huang, Ying
2022-03-22  0:18   ` Linus Torvalds
2022-03-22  0:54     ` Huang, Ying
2022-03-22  1:08       ` Linus Torvalds
2022-03-22  7:35     ` Ingo Molnar
2022-03-22  7:48       ` Ingo Molnar
2022-03-22  8:18         ` Huang, Ying
2022-03-22 11:07           ` Ingo Molnar
2022-03-21 15:44 ` Nathan Chancellor [this message]
2022-03-22  7:54   ` Ingo Molnar
2022-03-22 15:32     ` Nathan Chancellor
2022-03-22 15:39       ` Randy Dunlap
2022-03-22 11:10 ` [GIT PULL -v2] " Ingo Molnar
2022-03-22 23:27   ` pr-tracker-bot
2022-03-22 23:27 ` [GIT PULL] " pr-tracker-bot

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=YjiddAnoCCz7Tbt3@dev-arch.thelio-3990X \
    --to=nathan@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=bp@alien8.de \
    --cc=bristot@redhat.com \
    --cc=bsegall@google.com \
    --cc=dietmar.eggemann@arm.com \
    --cc=juri.lelli@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgorman@suse.de \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.org \
    --cc=vincent.guittot@linaro.org \
    /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

Powered by JetHome