public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Corey Minyard <minyard@acm.org>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Fixes for IPMI use of timers
Date: Fri, 20 May 2005 18:14:16 -0700	[thread overview]
Message-ID: <428E8B68.6040909@mvista.com> (raw)
In-Reply-To: <428D2181.2080106@acm.org>

Corey Minyard wrote:
> 
> 
> ------------------------------------------------------------------------
> 
> Fix some problems with the high-res timer support.
> 
> Signed-off-by: Corey Minyard <minyard@acm.org>
> 
> Index: linux-2.6.12-rc4/drivers/char/ipmi/ipmi_si_intf.c
> ===================================================================
> --- linux-2.6.12-rc4.orig/drivers/char/ipmi/ipmi_si_intf.c
> +++ linux-2.6.12-rc4/drivers/char/ipmi/ipmi_si_intf.c
> @@ -769,10 +769,11 @@
>  
>  		/* We already have irqsave on, so no need for it
>                     here. */
> -		read_lock(&xtime_lock);
> +		read_lock_irqsave(&xtime_lock, flags);

I rather hope this fails to compile :)  xtime_lock is a sequence lock in the 2.6 
kernel.

>  		jiffies_now = jiffies;
>  		smi_info->si_timer.expires = jiffies_now;
>  		smi_info->si_timer.sub_expires = get_arch_cycles(jiffies_now);
> +		read_unlock_irqrestore(&xtime_lock, flags);
>  
>  		add_usec_to_timer(&smi_info->si_timer, SI_SHORT_TIMEOUT_USEC);
>  
> @@ -830,11 +831,11 @@
>  		smi_info->short_timeouts++;
>  		spin_unlock_irqrestore(&smi_info->count_lock, flags);
>  #if defined(CONFIG_HIGH_RES_TIMERS)
> -		read_lock(&xtime_lock);
> +		read_lock_irqsave(&xtime_lock, flags);
>                  smi_info->si_timer.expires = jiffies;
>                  smi_info->si_timer.sub_expires
>                          = get_arch_cycles(smi_info->si_timer.expires);
> -                read_unlock(&xtime_lock);
> +		read_unlock_irqrestore(&xtime_lock, flags);
>  		add_usec_to_timer(&smi_info->si_timer, SI_SHORT_TIMEOUT_USEC);
>  #else
>  		smi_info->si_timer.expires = jiffies + 1;

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/

  parent reply	other threads:[~2005-05-21  1:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-19 23:30 [PATCH] Fixes for IPMI use of timers Corey Minyard
2005-05-19 23:51 ` Lee Revell
2005-05-20  2:20   ` Corey Minyard
2005-05-21  1:14 ` George Anzinger [this message]
2005-05-21  1:30   ` Lee Revell
2005-05-21  2:00     ` Corey Minyard

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=428E8B68.6040909@mvista.com \
    --to=george@mvista.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=minyard@acm.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