xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>, xen-devel@lists.xen.org
Cc: Ian Campbell <Ian.Campbell@eu.citrix.com>,
	Jan Beulich <jbeulich@suse.com>,
	Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: [PATCH] irq: Remove irqaction.free_on_release
Date: Tue, 09 Oct 2012 12:44:56 +0100	[thread overview]
Message-ID: <CC99CCC8.4E6A2%keir@xen.org> (raw)
In-Reply-To: <37f1afbec80b0f052aec.1349701772@andrewcoop.uk.xensource.com>

But reasoning behind c/s 20153, which introduced it, still applies? Callers
using setup_irq() don't want their passed-in irqaction to be xfree()ed?

 -- Keir

On 08/10/2012 14:09, "Andrew Cooper" <andrew.cooper3@citrix.com> wrote:

> It is always set to 1, and only checked on some of the codepaths which free an
> irqaction.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
> 
> --
> This patch does touch common code as well as x86 and arm architectures,
> so probably needs quite a few acks.
> 
> diff -r 5fbdbf585f5f -r 37f1afbec80b xen/arch/arm/gic.c
> --- a/xen/arch/arm/gic.c
> +++ b/xen/arch/arm/gic.c
> @@ -373,7 +373,7 @@ void __init release_irq(unsigned int irq
>      /* Wait to make sure it's not being used on another CPU */
>      do { smp_mb(); } while ( desc->status & IRQ_INPROGRESS );
>  
> -    if (action && action->free_on_release)
> +    if ( action )
>          xfree(action);
>  }
>  
> diff -r 5fbdbf585f5f -r 37f1afbec80b xen/arch/arm/irq.c
> --- a/xen/arch/arm/irq.c
> +++ b/xen/arch/arm/irq.c
> @@ -97,7 +97,6 @@ int __init request_irq(unsigned int irq,
>      action->handler = handler;
>      action->name = devname;
>      action->dev_id = dev_id;
> -    action->free_on_release = 1;
>  
>      retval = setup_irq(irq, action);
>      if (retval)
> diff -r 5fbdbf585f5f -r 37f1afbec80b xen/arch/x86/irq.c
> --- a/xen/arch/x86/irq.c
> +++ b/xen/arch/x86/irq.c
> @@ -952,7 +952,6 @@ int __init request_irq(unsigned int irq,
>      action->handler = handler;
>      action->name = devname;
>      action->dev_id = dev_id;
> -    action->free_on_release = 1;
>  
>      retval = setup_irq(irq, action);
>      if (retval)
> @@ -979,7 +978,7 @@ void __init release_irq(unsigned int irq
>      /* Wait to make sure it's not being used on another CPU */
>      do { smp_mb(); } while ( desc->status & IRQ_INPROGRESS );
>  
> -    if (action && action->free_on_release)
> +    if ( action )
>          xfree(action);
>  }
>  
> diff -r 5fbdbf585f5f -r 37f1afbec80b xen/include/xen/irq.h
> --- a/xen/include/xen/irq.h
> +++ b/xen/include/xen/irq.h
> @@ -13,7 +13,6 @@ struct irqaction {
>      void (*handler)(int, void *, struct cpu_user_regs *);
>      const char *name;
>      void *dev_id;
> -    bool_t free_on_release;
>  };
>  
>  /*

  reply	other threads:[~2012-10-09 11:44 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-08 13:09 [PATCH] irq: Remove irqaction.free_on_release Andrew Cooper
2012-10-09 11:44 ` Keir Fraser [this message]
2012-10-09 14:38   ` Andrew Cooper

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=CC99CCC8.4E6A2%keir@xen.org \
    --to=keir@xen.org \
    --cc=Ian.Campbell@eu.citrix.com \
    --cc=Stefano.Stabellini@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=xen-devel@lists.xen.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).