lkml.org 
[lkml]   [2010]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH 2/4] tracing/sched: Fix task states in sched switch event

* Steven Rostedt <rostedt@goodmis.org> wrote:

> +#define TASK_STATE_X(num) TASK_STATE_##num " (" DESCR_TASK_STATE_##num ")"
> static const char *task_state_array[] = {
> - "R (running)", /* 0 */
> - "S (sleeping)", /* 1 */
> - "D (disk sleep)", /* 2 */
> - "T (stopped)", /* 4 */
> - "t (tracing stop)", /* 8 */
> - "Z (zombie)", /* 16 */
> - "X (dead)", /* 32 */
> - "x (dead)", /* 64 */
> - "K (wakekill)", /* 128 */
> - "W (waking)", /* 256 */
> + TASK_STATE_X(0),
> + TASK_STATE_X(1),
> + TASK_STATE_X(2),
> + TASK_STATE_X(4),
> + TASK_STATE_X(8),
> + TASK_STATE_X(16),
> + TASK_STATE_X(32),
> + TASK_STATE_X(64),
> + TASK_STATE_X(128),
> + TASK_STATE_X(256)

Hm, this is totally unreadable. What does 'TASK_STATE_X' mean??

Ingo


\
 
 \ /
  Last update: 2010-05-13 08:17    [W:0.042 / U:0.420 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site