mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Chris Wedgwood <cw@f00f.org>
To: blaisorblade@yahoo.it
Cc: akpm@osdl.org, jdike@addtoit.com, linux-kernel@vger.kernel.org,
	user-mode-linux-devel@lists.sourceforge.net, mingo@redhat.com
Subject: Re: [patch 1/1] [RFC] uml: add and use generic hw_controller_type->release
Date: Thu, 26 May 2005 19:11:42 -0700	[thread overview]
Message-ID: <c915b004e775ff68517f3be2c95c6f93.IBX@taniwha.stupidest.org> (raw)
In-Reply-To: <20050527003926.1FD861AEE92@zion.home.lan>

On Fri, May 27, 2005 at 02:39:26AM +0200, blaisorblade@yahoo.it wrote:

> From: Paolo 'Blaisorblade' Giarrusso <blaisorblade@yahoo.it>, Chris Wedgwood <cw@f00f.org>
> CC: Ingo Molnar <mingo@redhat.com>

[...]

> This is heavily based on some work by Chris Wedgwood, which however
> didn't get the patch merged for something I'd call a
> "misunderstanding" (the need for this patch wasn't cleanly
> explained, thus adding the generic hook was felt as undesirable).

Looks very reasonable to me and your explaination is much better than
mine was :-)

> diff -puN kernel/irq/manage.c~uml-gen-irq-release kernel/irq/manage.c
> --- linux-2.6.git/kernel/irq/manage.c~uml-gen-irq-release	2005-05-25 01:15:46.000000000 +0200
> +++ linux-2.6.git-paolo/kernel/irq/manage.c	2005-05-25 01:15:46.000000000 +0200
> @@ -255,6 +255,10 @@ void free_irq(unsigned int irq, void *de
>  
>  			/* Found it - now remove it from the list of entries */
>  			*pp = action->next;
> +
> +			if (desc->handler->release)
> +				desc->handler->release(irq, dev_id);
> +

Because right now we know the *only* port that needs a release method
is UML I wonder if we could do save a couple of bytes & cycles for
everyone else by doing something like #ifdef CONFIG_IRQ_HAS_RELEASE,
#endif around that and then letting the Kconfig magic set
CONFIG_IRQ_HAS_RELEASE as required?  If other arches need it thay can
do the same and if eventually almost everyone does we can kill the
#ifdef crud?

Longer term I wonder if some of the irq mechanics in UML couldn't end
up being a bit more like the s390 stuff too?

  reply	other threads:[~2005-05-27  2:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-27  0:39 blaisorblade
2005-05-27  2:11 ` Chris Wedgwood [this message]
2005-05-28 11:26   ` Blaisorblade
2005-05-28 17:22     ` Chris Wedgwood

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=c915b004e775ff68517f3be2c95c6f93.IBX@taniwha.stupidest.org \
    --to=cw@f00f.org \
    --cc=akpm@osdl.org \
    --cc=blaisorblade@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®