linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>
Subject: Re: [RFC] PMU: don't lock_kernel()
Date: Mon, 12 Nov 2007 07:54:50 +1100	[thread overview]
Message-ID: <1194814490.6510.18.camel@pasglop> (raw)
In-Reply-To: <1194523283.6294.9.camel@johannes.berg>


On Thu, 2007-11-08 at 13:01 +0100, Johannes Berg wrote:
> I see nothing that this lock_kernel() actually protects against
> so remove it.
> 
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>

Acked-by: Benjamin Herrenschmidt <benh@kernel.crashing.org>

> ---
>  drivers/macintosh/via-pmu.c |    3 ---
>  1 file changed, 3 deletions(-)
> 
> --- everything.orig/drivers/macintosh/via-pmu.c	2007-11-08 11:48:37.192845813 +0100
> +++ everything/drivers/macintosh/via-pmu.c	2007-11-08 11:48:48.292846681 +0100
> @@ -33,7 +33,6 @@
>  #include <linux/adb.h>
>  #include <linux/pmu.h>
>  #include <linux/cuda.h>
> -#include <linux/smp_lock.h>
>  #include <linux/module.h>
>  #include <linux/spinlock.h>
>  #include <linux/pm.h>
> @@ -2436,7 +2435,6 @@ pmu_release(struct inode *inode, struct 
>  	struct pmu_private *pp = file->private_data;
>  	unsigned long flags;
>  
> -	lock_kernel();
>  	if (pp != 0) {
>  		file->private_data = NULL;
>  		spin_lock_irqsave(&all_pvt_lock, flags);
> @@ -2450,7 +2448,6 @@ pmu_release(struct inode *inode, struct 
>  
>  		kfree(pp);
>  	}
> -	unlock_kernel();
>  	return 0;
>  }
>  
> 

      reply	other threads:[~2007-11-11 20:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-08 12:01 [RFC] PMU: don't lock_kernel() Johannes Berg
2007-11-11 20:54 ` Benjamin Herrenschmidt [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=1194814490.6510.18.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=johannes@sipsolutions.net \
    --cc=linuxppc-dev@ozlabs.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).