[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20081218133621.GA4624@elte.hu>
Date: Thu, 18 Dec 2008 14:36:23 +0100
From: Ingo Molnar <mingo@...e.hu>
To: KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com>
Cc: Andrew Morton <akpm@...ux-foundation.org>,
Yinghai Lu <yhlu.kernel@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
linux-next <linux-next@...r.kernel.org>
Subject: Re: [mmotm and linux-next][PATCH] irq: enclose irq_desc_lock_class
in CONFIG_LOCKDEP
* KOSAKI Motohiro <kosaki.motohiro@...fujitsu.com> wrote:
> > >> or, following #ifdef ?
> > >>
> > >> #if defined(CONFIG_SPARSE_IRQ) || defined(CONFIG_TRACE_IRQFLAGS)
> > >>
> > >> /*
> > >> * lockdep: we want to handle all irq_desc locks as a single lock-class:
> > >> */
> > >> static struct lock_class_key irq_desc_lock_class;
> > >
> > > instead of increasing the #ifdef jungle, how about removing some? For
> > > example is this distinction:
> > >
> > >> > #ifndef CONFIG_SPARSE_IRQ
> > >
> > > really needed? We should use symmetric lock class annotations, regardless
> > > of how irq_desc[] is laid out.
> >
> > it seems make much sense. I'll test your idea tommorow.
>
> Ingo, you are right. I confirmed your idea works well.
>
>
> I tested following ten pattern.
>
> o handle.c can compile without any warnings?
>
> SPARSE_IRQ TRACE_IRQ LOCKDEP
> ------------------------------------------
> n n n
> Y n n
> n Y n
> n n Y
> Y Y n
> N Y Y
> Y n Y
> Y Y Y
>
>
> o builded kernel works well? (tested on x86_64)
>
> SPARSE_IRQ TRACE_IRQ LOCKDEP
> ------------------------------------------
> n n n
> Y Y Y
>
>
> ==
> Subject: [PATCH] irq: remove unnecessary ifdef
Applied to tip/irq/sparseirq, thanks!
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists