public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: Thomas Gleixner <tglx@linutronix.de>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Julia Lawall <julia@diku.dk>,
	Suresh Siddha <suresh.b.siddha@intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-arch@vger.kernel.org
Subject: Re: [PATCH] irq: Start the transition of irq_chip methods taking a desc
Date: Sun, 21 Mar 2010 15:43:47 +0100 (CET)	[thread overview]
Message-ID: <alpine.LFD.2.00.1003211541120.3147@localhost.localdomain> (raw)
In-Reply-To: <m1eijd3jl7.fsf_-_@fess.ebiederm.org>

Eric,

On Sun, 21 Mar 2010, Eric W. Biederman wrote:
> 
> With SPARSE_IRQ irq_to_desc becomes an unnecessary lookup operation on
> the fast path of dispatching irqs to their handlers.  We can avoid
> this cost by passing an irq_desc pointer instead of using an integer
> irq token to the irq_chip methods.
> 
> A single patch to convert all of the architectures is an unreviewable
> 2000+ line patch.  A gradual transition scenario with two sets of
> irq_chip methods in irq_chip is an unmanageable mess in kernel/irq.
> 
> So instead I define some macros so the generic irq code in kernel/irq/
> can compile either way based on a boolean Kconfig variable
> CONFIG_CHIP_PARAM_DESC.  This allows us to convert one architecture at
> a time, reducing the follow on patches to manageable proportions.  It
> is a little bit ugly but it is much better than the alternatives, and
> as soon as we finish the transition we can kill the macros.
> 
> I introduce the macros CHIP_ARG, CHIP_VAR, and CHIP_PARAM where
> appropriate.  I change a few declarations of irq as int to unsigned
> int.  I normalize the variables names in the functions that call
> chip methods to ensure that I have the variables irq and desc present
> allowing CHIP_ARG to work properly.  Most importantly none of the irq
> logic changes with this patch.

I like that approach very much. Is the output binary equivivalent?

Thanks,

	tglx

  reply	other threads:[~2010-03-21 14:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1267697339-5491-1-git-send-email-yinghai@kernel.org>
     [not found] ` <1267697339-5491-7-git-send-email-yinghai@kernel.org>
     [not found]   ` <alpine.LFD.2.00.1003041142460.2014@localhost.localdomain>
     [not found]     ` <4B900250.8020100@kernel.org>
     [not found]       ` <Pine.LNX.4.64.1003050847170.21768@ask.diku.dk>
     [not found]         ` <m1eije71et.fsf@fess.ebiederm.org>
     [not found]           ` <Pine.LNX.4.64.1003211153470.7805@ask.diku.dk>
2010-03-21 13:11             ` [PATCH] irq: Start the transition of irq_chip methods taking a desc Eric W. Biederman
2010-03-21 14:43               ` Thomas Gleixner [this message]
2010-03-21 18:50                 ` Yinghai Lu
2010-03-22  0:32                 ` Eric W. Biederman

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=alpine.LFD.2.00.1003211541120.3147@localhost.localdomain \
    --to=tglx@linutronix.de \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=hpa@zytor.com \
    --cc=julia@diku.dk \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=suresh.b.siddha@intel.com \
    --cc=yinghai@kernel.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