public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: Mandeep Singh Baines <msb@chromium.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Don Zickus <dzickus@redhat.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Michal Hocko <mhocko@suse.cz>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH] watchdog: Make sure the watchdog thread gets CPU on loaded system
Date: Thu, 15 Mar 2012 12:00:39 +0100	[thread overview]
Message-ID: <1331809239.18960.168.camel@twins> (raw)
In-Reply-To: <20120315014511.GT27051@google.com>

On Wed, 2012-03-14 at 18:45 -0700, Mandeep Singh Baines wrote:
> You could make MAX_RT_PRIO greater than MAX_USER_RT_PRIO but that
> might
> have some impact on real-time applications. A simple one-line patch:
> 
> - #define MAX_RT_PRIO           MAX_USER_RT_PRIO
> + #define MAX_RT_PRIO           (MAX_USER_RT_PRIO + 1)
> 
> would prevent user-space from causing a false lockup detection.

We're so not going to muck with the fifo priorities just for this stupid
soft watchdog,.. I already hate that I can't disable the piece of crap,
making it more involved is just really not going to happen.



  reply	other threads:[~2012-03-15 11:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14 20:38 [PATCH] watchdog: Make sure the watchdog thread gets CPU on loaded system Don Zickus
2012-03-14 20:59 ` Mandeep Singh Baines
2012-03-14 23:19 ` Andrew Morton
2012-03-15  1:45   ` Mandeep Singh Baines
2012-03-15 11:00     ` Peter Zijlstra [this message]
2012-03-15 11:06       ` Peter Zijlstra
2012-03-15 12:42         ` Ingo Molnar
2012-03-15 14:00           ` Peter Zijlstra
2012-03-15 14:35             ` Don Zickus
2012-03-15 15:39               ` Mandeep Singh Baines
2012-03-15 16:10                 ` Peter Zijlstra
2012-03-15 16:11                   ` Peter Zijlstra
2012-03-15 16:16                     ` Peter Zijlstra
2012-03-15 17:04                       ` Mandeep Singh Baines
2012-03-15  8:02   ` Michal Hocko
2012-03-15 15:54     ` Don Zickus
2012-03-15 16:04       ` Peter Zijlstra
2012-03-19 22:00         ` Andrew Morton
2012-03-15 16:14       ` Michal Hocko
2012-03-15 17:14         ` Don Zickus
  -- strict thread matches above, loose matches on Subject: below --
2012-03-13  9:45 [PATCH] watchdog: make " Michal Hocko
2012-03-13 13:42 ` Don Zickus

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=1331809239.18960.168.camel@twins \
    --to=a.p.zijlstra@chello.nl \
    --cc=akpm@linux-foundation.org \
    --cc=dzickus@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhocko@suse.cz \
    --cc=mingo@elte.hu \
    --cc=msb@chromium.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