public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Don Zickus <dzickus@redhat.com>, Mike Lykov <combr@yandex.ru>,
	Thomas Gleixner <tglx@linutronix.de>,
	linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
	kirill@shutemov.name
Subject: Re: [BUG?] false positive in soft lockup detector while unlzma initramfs on slow cpu
Date: Thu, 31 Jan 2013 12:18:23 +0100	[thread overview]
Message-ID: <20130131111823.GA4587@gmail.com> (raw)
In-Reply-To: <20130129155917.4ee64214.akpm@linux-foundation.org>


* Andrew Morton <akpm@linux-foundation.org> wrote:

> On Tue, 29 Jan 2013 10:33:48 -0500
> Don Zickus <dzickus@redhat.com> wrote:
> 
> > --- a/kernel/watchdog.c
> > +++ b/kernel/watchdog.c
> > @@ -79,6 +79,14 @@ static int __init softlockup_panic_setup(char *str)
> >  }
> >  __setup("softlockup_panic=", softlockup_panic_setup);
> >  
> > +static int __init watchdog_thresh_setup(char *str)
> > +{
> > +	watchdog_thresh = simple_strtoul(str, NULL, 0);
> > +
> > +	return 1;
> > +}
> > +__setup("watchdog_thresh=", watchdog_thresh_setup);
> 
> I wonder if there's some magical way in which we can set any 
> sysctl from the kernel command line.  Add 
> sys.vm.min_free_kbytes=42 to the command line, walk the 
> hierarchy late in boot...

A facility like that would be totally awesome - we could remove 
a lot of duplicated and outright inconsistent (often missing) 
__setup() hackery that way.

Single source of information and all that.

Thanks,

	Ingo

  reply	other threads:[~2013-01-31 11:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 13:42 [BUG?] false positive in soft lockup detector while unlzma initramfs on slow cpu Mike Lykov
2013-01-29 15:33 ` Don Zickus
2013-01-29 17:18   ` anish kumar
2013-01-30 15:51     ` Don Zickus
2013-01-30 15:59       ` anish kumar
2013-01-29 23:59   ` Andrew Morton
2013-01-31 11:18     ` Ingo Molnar [this message]
2013-01-30  9:39   ` Mike Lykov
2013-01-30 15:40     ` Don Zickus
2013-01-31 11:21       ` Mike Lykov
2013-01-31 14:46         ` Don Zickus
2013-02-01 10:44           ` Mike Lykov
2013-02-01 15:59             ` Don Zickus
2013-02-01 16:43               ` Mike Lykov

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=20130131111823.GA4587@gmail.com \
    --to=mingo@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=combr@yandex.ru \
    --cc=dzickus@redhat.com \
    --cc=kirill@shutemov.name \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-watchdog@vger.kernel.org \
    --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