All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Zickus <dzickus@redhat.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
	John Stultz <johnstul@us.ibm.com>,
	Thomas Gleixner <tglx@linutronix.de>,
	lwoodman@redhat.com, jbaron@redhat.com
Subject: Re: [PATCH] tty, add kref to sysrq handlers
Date: Thu, 19 Jul 2012 10:06:10 -0400	[thread overview]
Message-ID: <20120719140609.GA15158@redhat.com> (raw)
In-Reply-To: <1339514522-1742-1-git-send-email-prarit@redhat.com>

On Tue, Jun 12, 2012 at 11:22:02AM -0400, Prarit Bhargava wrote:
> [This seems to have been missed ... sending again]
> 
> On a large system with a large number of tasks, the output of
> 
> echo t > /proc/sysrq-trigger
> 
> can take a long period of time.  If this period is greater than the period
> of the current clocksource, the clocksource watchdog will mark the
> clocksource as unstable and fail the clocksource over.

A lot of our customers are running into this issue (especially the big
boxes).  This is patch solves their problem nicely.

The approach is a little heavier than the current approach, but it allows
a useful feature like sysrq-t to work reliably.

Acked-by: Don Zickus <dzickus@redhat.com>

  reply	other threads:[~2012-07-19 14:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-12 15:22 [PATCH] tty, add kref to sysrq handlers Prarit Bhargava
2012-07-19 14:06 ` Don Zickus [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-07-27 13:04 Prarit Bhargava
2012-07-27 12:19 Prarit Bhargava
2012-05-14 14:41 Prarit Bhargava

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=20120719140609.GA15158@redhat.com \
    --to=dzickus@redhat.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jbaron@redhat.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lwoodman@redhat.com \
    --cc=prarit@redhat.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.