linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Kari Argillander <kari.argillander@stargateuniverse.net>,
	Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Nathan Chancellor <nathan@kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Ard Biesheuvel <ardb@kernel.org>,
	Josh Poimboeuf <jpoimboe@redhat.com>,
	Jonathan Corbet <corbet@lwn.net>,
	kari.argillander@gmail.com
Subject: Re: [TREE] "Fast Kernel Headers" Tree -v3
Date: Tue, 22 Mar 2022 08:37:07 -0700	[thread overview]
Message-ID: <b8095bf8-961f-827c-2bd6-2ffa6298b730@infradead.org> (raw)
In-Reply-To: <CAKBF=pvWzuPx0JB3XZ-v+i7KGbhMQTgH6xtii_Bed+qKRFx+ww@mail.gmail.com>

Hi Kari,

On 3/22/22 00:59, Kari Argillander wrote:
> 15.3.2022 12.35 Ingo Molnar (mingo@kernel.org) wrote:
>>
>> This is -v3 of the "Fast Kernel Headers" tree, which is an ongoing rework
>> of the Linux kernel's header hierarchy & header dependencies, with the dual
>> goals of:
>>
>>  - speeding up the kernel build (both absolute and incremental build times)
>>
>>  - decoupling subsystem type & API definitions from each other
>>
>> The fast-headers tree consists of over 25 sub-trees internally, spanning
>> over 2,300 commits, which can be found at:
>>
>>     git://git.kernel.org/pub/scm/linux/kernel/git/mingo/tip.git master
> 
> I have had problems to build master branch (defconfig) with gcc9
>     gcc (Ubuntu 9.4.0-1ubuntu1~20.04) 9.4.0
> 
> I did also test v2 and problems where there too. I have no problem with gcc10 or
> Clang11. Error I get is:
> 
> In file included from ./include/linux/rcuwait_api.h:7,
>                  from ./include/linux/rcuwait.h:6,
>                  from ./include/linux/irq_work.h:7,
>                  from ./include/linux/perf_event_types.h:44,
>                  from ./include/linux/perf_event_api.h:17,
>                  from arch/x86/kernel/kprobes/opt.c:8:
> ./include/linux/rcuwait_api.h: In function ‘rcuwait_active’:
> ./include/linux/rcupdate.h:328:9: error: dereferencing pointer to
> incomplete type ‘struct task_struct’
>   328 |  typeof(*p) *local = (typeof(*p) *__force)READ_ONCE(p); \
>       |         ^
> ./include/linux/rcupdate.h:439:31: note: in expansion of macro
> ‘__rcu_access_pointer’
>   439 | #define rcu_access_pointer(p) __rcu_access_pointer((p),
> __UNIQUE_ID(rcu), __rcu)
>       |                               ^~~~~~~~~~~~~~~~~~~~
> ./include/linux/rcuwait_api.h:15:11: note: in expansion of macro
> ‘rcu_access_pointer’
>    15 |  return !!rcu_access_pointer(w->task);
> 
>     Argillander

You could try the patch here:
https://lore.kernel.org/all/917e9ce0-c8cf-61b2-d1ba-ebf25bbd979d@infradead.org/

although the build error that it fixes doesn't look exactly the same
as yours.

>> There's various changes in -v3, and it's now ported to the latest kernel
>> (v5.17-rc8).
>>
>> Diffstat difference:
>>
>>  -v2: 25332 files changed, 178498 insertions(+), 74790 deletions(-)
>>  -v3: 25513 files changed, 180947 insertions(+), 74572 deletions(-)


-- 
~Randy

  reply	other threads:[~2022-03-22 15:37 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-08 16:26 [ANNOUNCE] "Fast Kernel Headers" Tree -v2 Ingo Molnar
2022-01-10 22:03 ` Arnd Bergmann
2022-01-11 16:23   ` Arnd Bergmann
2022-01-11 17:08     ` David Laight
2022-01-13  8:27     ` Ingo Molnar
2022-01-13  9:20       ` Arnd Bergmann
2022-01-19 12:31         ` Ingo Molnar
2022-01-19 17:20           ` Arnd Bergmann
2022-01-22  9:18             ` Ingo Molnar
2022-01-13  8:57   ` Ingo Molnar
2022-01-13 10:16     ` Arnd Bergmann
2022-03-15 10:35 ` [TREE] "Fast Kernel Headers" Tree -v3 Ingo Molnar
2022-03-22  7:59   ` Kari Argillander
2022-03-22 15:37     ` Randy Dunlap [this message]
2022-03-22 16:22       ` Kari Argillander
2022-03-22 19:03         ` Kari Argillander
2023-11-04  9:07           ` Lucas Tanure

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=b8095bf8-961f-827c-2bd6-2ffa6298b730@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=akpm@linux-foundation.org \
    --cc=ardb@kernel.org \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jpoimboe@redhat.com \
    --cc=kari.argillander@gmail.com \
    --cc=kari.argillander@stargateuniverse.net \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.org \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).