From: Peter Zijlstra <peterz@infradead•org>
To: mingo@kernel•org, will@kernel•org, tglx@linutronix•de
Cc: linux-s390@vger•kernel.org, peterz@infradead•org,
bigeasy@linutronix•de, x86@kernel•org, heiko.carstens@de•ibm.com,
linux-kernel@vger•kernel.org, rostedt@goodmis•org,
a.darwish@linutronix•de, sparclinux@vger•kernel.org,
linuxppc-dev@lists•ozlabs.org, davem@davemloft•net
Subject: [PATCH v3 0/5] lockdep: Change IRQ state tracking to use per-cpu variables
Date: Fri, 29 May 2020 23:35:50 +0200 [thread overview]
Message-ID: <20200529213550.683440625@infradead.org> (raw)
Ahmed and Sebastian wanted additional lockdep_assert*() macros and ran
into header hell.
Move the IRQ state into per-cpu variables, which removes the dependency on
task_struct, which is what generated the header-hell.
These patches are intended to go on top of:
https://lkml.kernel.org/r/20200529212728.795169701@infradead.org
but should apply on current tip/master without much difficulty.
There are a few build fixes for Sparc64, PowerPC64 and s390. Especially the
Sparc one I'm not sure about.
next reply other threads:[~2020-05-29 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 21:35 Peter Zijlstra [this message]
2020-05-29 21:35 ` [RFC][PATCH v3 1/5] sparc64: Fix asm/percpu.h build error Peter Zijlstra
2020-05-29 23:29 ` David Miller
2020-06-04 16:57 ` Peter Zijlstra
2020-06-04 20:41 ` Peter Zijlstra
2020-05-29 21:35 ` [PATCH v3 2/5] powerpc64: Break asm/percpu.h vs spinlock_types.h dependency Peter Zijlstra
2020-05-29 21:35 ` [PATCH v3 3/5] s390: Break cyclic percpu include Peter Zijlstra
2020-05-29 21:35 ` [PATCH v3 4/5] lockdep: Change hardirq{s_enabled, _context} to per-cpu variables Peter Zijlstra
2020-05-29 21:35 ` [PATCH v3 5/5] lockdep: Remove lockdep_hardirq{s_enabled, _context}() argument Peter Zijlstra
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=20200529213550.683440625@infradead.org \
--to=peterz@infradead$(echo .)org \
--cc=a.darwish@linutronix$(echo .)de \
--cc=bigeasy@linutronix$(echo .)de \
--cc=davem@davemloft$(echo .)net \
--cc=heiko.carstens@de$(echo .)ibm.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-s390@vger$(echo .)kernel.org \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=mingo@kernel$(echo .)org \
--cc=rostedt@goodmis$(echo .)org \
--cc=sparclinux@vger$(echo .)kernel.org \
--cc=tglx@linutronix$(echo .)de \
--cc=will@kernel$(echo .)org \
--cc=x86@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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