public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dimitri Sivanich <sivanich@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [PATCH] disable softlockup detection at boottime
Date: Tue, 29 Apr 2008 07:44:26 -0500	[thread overview]
Message-ID: <20080429124426.GA20775@sgi.com> (raw)
In-Reply-To: <20080429123522.GK31271@elte.hu>

On Tue, Apr 29, 2008 at 02:35:22PM +0200, Ingo Molnar wrote:
> * Dimitri Sivanich <sivanich@sgi.com> wrote:
> 
> > I'm getting unaligned access errors trying to set it to anything, so 
> > it's not working for me currently (2.6.25):
> > 
> > It's tripping up on the address of 'one', which is an int that is not 
> > properly aligned for the unsigned long comparison in 
> > proc_doulongvec_minmax on my 64 bit machine.  Also, the value '0' is 
> > invalid for softlockup_thresh, correct?
> > 
> > I temporarily got around these issues with the following hack.
> 
> ah, sorry. But ... perhaps using threshold -1 would be the most 
> intuitive setting? (for 'infinite timeout' ==> softlockup detector 
> turned off) That way it all becomes configurable as part of the 
> threshold? No strong opinion though.
>

Having the ability to switch it off dynamically would be nice to have, but
will need a little work yet.  Any solution should also minimize the amount
of time spent in softlockup_tick.

Either '0' or '-1' seems OK to me, but if '-1' turns it off, do we allow
a value of '0'?.

  reply	other threads:[~2008-04-29 12:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-23 20:16 [PATCH] disable softlockup detection at boottime Dimitri Sivanich
2008-04-23 21:55 ` Randy Dunlap
2008-04-23 22:24   ` Dimitri Sivanich
2008-04-28 16:55 ` Ingo Molnar
2008-04-28 18:52   ` Dimitri Sivanich
2008-04-29 12:35     ` Ingo Molnar
2008-04-29 12:44       ` Dimitri Sivanich [this message]
2008-04-29 14:13         ` Ingo Molnar

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=20080429124426.GA20775@sgi.com \
    --to=sivanich@sgi.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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