public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Li Zefan <lizf@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: akpm@linux-foundation.org, containers@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/4] Move the cgroup debug subsys into cgroup.c to access internal state
Date: Thu, 23 Jul 2009 14:21:05 +0800	[thread overview]
Message-ID: <4A680151.9010502@cn.fujitsu.com> (raw)
In-Reply-To: <20090722195035.7481.85657.stgit@menage.mtv.corp.google.com>

Paul Menage wrote:
> Move the cgroup debug subsys into cgroup.c to access internal state
> 
> While it's architecturally clean to have the cgroup debug subsystem be
> completely independent of the cgroups framework, it limits its
> usefulness for debugging the contents of internal data structures.
> Move the debug subsystem code into the scope of all the cgroups data
> structures to make more detailed debugging possible.
> 
> Signed-off-by: Paul Menage <menage@google.com>
> 

Reviewed-by: Li Zefan <lizf@cn.fujitsu.com>

...

> +static u64 current_css_set_read(struct cgroup *cont, struct cftype *cft)
> +{
> +	return (u64)(long)current->cgroups;

I think it should be (unsigned long), otherwise:

 # cat debug.current_css_set
 18446744072653386208

That is: ffffffffc10c31e0

> +}

  reply	other threads:[~2009-07-23  6:22 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-22 19:50 [PATCH 0/4] CGroup: Support for named and empty hierarchies Paul Menage
2009-07-22 19:50 ` [PATCH 1/4] Support named cgroups hierarchies Paul Menage
2009-07-23  6:20   ` Li Zefan
2009-07-23  6:27     ` Paul Menage
2009-07-23  6:50       ` Li Zefan
2009-07-28 23:17         ` Paul Menage
2009-07-23  6:47   ` KAMEZAWA Hiroyuki
2009-07-22 19:50 ` [PATCH 2/4] Move the cgroup debug subsys into cgroup.c to access internal state Paul Menage
2009-07-23  6:21   ` Li Zefan [this message]
2009-07-23  6:51   ` KAMEZAWA Hiroyuki
2009-07-22 19:50 ` [PATCH 3/4] Add a back-pointer from struct cg_cgroup_link to struct cgroup Paul Menage
2009-07-23  6:44   ` Li Zefan
2009-07-23 14:31     ` Paul Menage
2009-07-22 19:50 ` [PATCH 4/4] Allow cgroup hierarchies to be created with no bound subsystems Paul Menage
2009-07-23  8:19   ` KAMEZAWA Hiroyuki
2009-07-23  8:32     ` Li Zefan
2009-07-24  5:21   ` Li Zefan
2009-07-23  5:13 ` [PATCH 0/4] CGroup: Support for named and empty hierarchies KAMEZAWA Hiroyuki
2009-07-23  5:37   ` Paul Menage
2009-07-23  5:45     ` KAMEZAWA Hiroyuki
  -- strict thread matches above, loose matches on Subject: below --
2009-07-28 23:26 Paul Menage
2009-07-28 23:26 ` [PATCH 2/4] Move the cgroup debug subsys into cgroup.c to access internal state Paul Menage

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=4A680151.9010502@cn.fujitsu.com \
    --to=lizf@cn.fujitsu.com \
    --cc=akpm@linux-foundation.org \
    --cc=containers@lists.linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=menage@google.com \
    /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