Re: [PATCH] lockdep: Simplify a bit hardirq <-> softirq transitions

2013-11-21 Thread Peter Zijlstra
On Wed, Nov 20, 2013 at 01:07:34AM +0100, Frederic Weisbecker wrote: > Instead of saving the hardirq state on a per CPU variable, which require > an explicit call before the softirq handling and some complication, > just save and restore the hardirq tracing state through functions > return values a

Re: [PATCH] lockdep: Simplify a bit hardirq <-> softirq transitions

2013-11-19 Thread Frederic Weisbecker
On Wed, Nov 20, 2013 at 01:07:34AM +0100, Frederic Weisbecker wrote: > Instead of saving the hardirq state on a per CPU variable, which require > an explicit call before the softirq handling and some complication, > just save and restore the hardirq tracing state through functions > return values a

[PATCH] lockdep: Simplify a bit hardirq <-> softirq transitions

2013-11-19 Thread Frederic Weisbecker
Instead of saving the hardirq state on a per CPU variable, which require an explicit call before the softirq handling and some complication, just save and restore the hardirq tracing state through functions return values and parameters. It simplifies a bit the black magic that works around the fac