linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH/WIP] Remove 'irq' argument from all IRQ handlers
Date: Fri, 01 Jun 2007 14:08:55 -0600	[thread overview]
Message-ID: <m18xb3zbc8.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <464E9739.40909@garzik.org> (Jeff Garzik's message of "Sat, 19 May 2007 02:20:41 -0400")

Jeff Garzik <jeff@garzik.org> writes:

> Attached is the patch and description that represents a current
> work-in-progress, removal of the 'irq' argument passed to all driver IRQ
> handlers.
>
> As this patch demonstrates, the 'irq' argument is useless and practically
> unused.  The vast majority of drivers have this information elsewhere (struct
> pci_dev or private struct).  The cases where it is actually used are as follows:
>
> * a couple Mac drivers have multiple IRQs, and use the irq argument for
> disambiguation purposes.  This can easily be remedied by moving that information
> into the info passed in the normal void* pointer.
>
> * Several ancient ISA drivers, which mainly use it for printk-in-irq-handler
> purposes.  A couple use the irq argument as an index into a structure, which is
> a buggy approach.  I fixed up these.
>
> This can be found in the 'hacking-irq-remove' branch of
> git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/misc-2.6.git
>
>
> Before I will even consider submitting this upstream, this patchset needs
>
> * non-x86[-64] build fixes, and testing
> * update the Mac drivers
> * one more review pass, to make sure everything is kosher
>
> so IOW, not anytime soon :)
>
> Jeff Garzik (12):
>       [irq-remove] Update core irq handling code to omit 'irq' parameter
>       [irq-remove] update sound drivers for new irq handler function sig
>       [irq-remove] update SCSI, ATA, IDE drivers for new irq handler function
> sig
>       [irq-remove] update net drivers for new irq handler function sig
>       driver irq handler arg removal: acorn, atm, block, bluetooth, cdrom
>       driver irq handler arg removal: arch-specific code
>       driver irq handler arg removal: acpi, char, dma, fc4
>       driver irq handler arg removal: i2c, ieee1394, infiniband, input, isdn
>       driver irq handler arg removal: macintosh, media, message, mfd, misc, mmc
>       driver irq handler arg removal: serial, video
>       driver irq handler arg removal: the rest
>       irq-remove: build and warning fixes for 2.6.21

Looks reasonable to me.  In my nefarious plans to make everything use
a struct irq pointer this would certainly help.

The get_irqfunc_irq() function to get the irq for the functions that
still need it looks like a very useful migration path.

Eric

      parent reply	other threads:[~2007-06-01 20:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-19  6:20 [PATCH/WIP] Remove 'irq' argument from all IRQ handlers Jeff Garzik
2007-05-19  9:03 ` Benjamin Herrenschmidt
2007-06-01 20:08 ` Eric W. Biederman [this message]

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=m18xb3zbc8.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=benh@kernel.crashing.org \
    --cc=jeff@garzik.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=paulus@samba.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).