All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [PATCH 2/3] restart debug: add final process tree status
Date: Wed, 30 Sep 2009 21:57:52 -0400	[thread overview]
Message-ID: <4AC40CA0.8020305@librato.com> (raw)
In-Reply-To: <20090929165402.GA10114-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>



Serge E. Hallyn wrote:
> Have tasks in sys_restart keep some status in a list off
> of checkpoint_ctx, and print this info when the checkpoint_ctx
> is freed.
> 
> This is mostly an RFC - in particular the error tracking is
> pretty half-hearted so far.  But the info it does spit out
> helped me to figured out the coordinator syncing problem
> fixed by the previous patch.
> 
> Sample dmesg output:
> [4568:4568:c/r:free_per_task_status:200] 4 tasks registered, nr_tasks was 0 nr_total 0
> [4568:4568:c/r:free_per_task_status:202] active pid was 1, ctx->errno 0
> [4568:4568:c/r:free_per_task_status:204] kflags 6 uflags 0 oflags 1
> [4568:4568:c/r:free_per_task_status:206] task 0 to run was 4568
> [4568:4568:c/r:free_per_task_status:209] pid 4566
> [4568:4568:c/r:free_per_task_status:211] it was coordinator
> [4568:4568:c/r:free_per_task_status:219] it was running
> [4568:4568:c/r:free_per_task_status:209] pid 4570
> [4568:4568:c/r:free_per_task_status:213] it was a ghost
> [4568:4568:c/r:free_per_task_status:209] pid 4569
> [4568:4568:c/r:free_per_task_status:213] it was a ghost
> [4568:4568:c/r:free_per_task_status:209] pid 4568
> [4568:4568:c/r:free_per_task_status:215] it was the root task
> [4568:4568:c/r:free_per_task_status:221] it was a normal task
> 
> So, when one task died before hitting sys_restart, the first line would
> show '3 tasks registered'.
> 
> Signed-off-by: Serge E. Hallyn <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

[...]

This looks pretty useful. Any chance you can you make it work on top
of the 5-patch series I posted ... ?

Thanks,

Oren.

  parent reply	other threads:[~2009-10-01  1:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-29 16:53 [PATCH 1/3] restart: make sure all tasks are in sys_restart Serge E. Hallyn
     [not found] ` <20090929165342.GA10076-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-09-29 16:54   ` [PATCH 2/3] restart debug: add final process tree status Serge E. Hallyn
     [not found]     ` <20090929165402.GA10114-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-01  1:57       ` Oren Laadan [this message]
     [not found]         ` <4AC40CA0.8020305-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-10-01 15:33           ` Serge E. Hallyn
     [not found]             ` <20091001153356.GA20565-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-01 23:29               ` Oren Laadan
2009-09-29 16:54   ` [PATCH 3/3] restart debug: splatter more ckpt_debugs about Serge E. Hallyn
     [not found]     ` <20090929165415.GB10114-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-10-01  1:54       ` Oren Laadan
2009-10-01  1:53   ` [PATCH 1/3] restart: make sure all tasks are in sys_restart Oren Laadan

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=4AC40CA0.8020305@librato.com \
    --to=orenl-rdfvbdnroixbdgjk7y7tuq@public.gmane.org \
    --cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.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.