All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Oleg Nesterov <oleg@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Dave Sullivan <dsulliva@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] hung_task debugging: Add tracepoint to report the hang
Date: Sun, 20 Oct 2013 10:48:37 +0200	[thread overview]
Message-ID: <20131020084837.GB16236@gmail.com> (raw)
In-Reply-To: <20131019161828.GA7439@redhat.com>


* Oleg Nesterov <oleg@redhat.com> wrote:

> Currently check_hung_task() prints a warning if it detects the problem, 
> but it is not convenient to watch the system logs if user-space wants to 
> be notified about the hang.
> 
> Add the new trace_sched_process_hang() into check_hung_task(), this way 
> a user-space monitor can easily wait for the hang and potentially 
> resolve a problem.

I'm wondering, is the data of trace_console() in kernel/printk/printk.c 
not sufficient?

If it's not enough then it might be better to add a higher level printk 
tracepoint instead - that can catch hung_task messages and (much) more.

Thanks,

	Ingo

  reply	other threads:[~2013-10-20  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-19 16:18 [PATCH 0/1] hung_task debugging: Add tracepoint to report the hang Oleg Nesterov
2013-10-19 16:18 ` [PATCH 1/1] " Oleg Nesterov
2013-10-20  8:48   ` Ingo Molnar [this message]
2013-10-29 19:10     ` Oleg Nesterov
2013-10-31 10:53   ` [tip:core/locking] " tip-bot for Oleg Nesterov

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=20131020084837.GB16236@gmail.com \
    --to=mingo@kernel.org \
    --cc=dsulliva@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rostedt@goodmis.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 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.