From: Balbir Singh <balbir@linux.vnet.ibm.com>
To: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Cc: Jiri Slaby <jirislaby@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linux kernel mailing list <linux-kernel@vger.kernel.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>,
Li Zefan <lizf@cn.fujitsu.com>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>
Subject: Re: memory-controller patch fails to boot in qemu [mmotm]
Date: Sun, 2 Aug 2009 21:57:32 +0530 [thread overview]
Message-ID: <20090802162732.GE8514@balbir.in.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0908021704300.3945@sister.anvils>
* Hugh Dickins <hugh.dickins@tiscali.co.uk> [2009-08-02 17:12:53]:
> On Sun, 2 Aug 2009, Balbir Singh wrote:
> > * Hugh Dickins <hugh.dickins@tiscali.co.uk> [2009-08-01 23:09:09]:
> > >
> > > Hmm, this a weird function, passed an argument just to tell it to do
> > > nothing. Perhaps a placeholder for something more sensible to come?
> >
> > The argument is passed a result of a function, It no-ops quite
> > frequently for the root cgroup.
>
> The more often it no-ops, the sillier it is to be called in
> the first place: here's an updated patch which fixes that too.
>
>
> [PATCH mmotm] memory controller: soft limit organize cgroups v9 fix
>
> CONFIG_CGROUP_MEM_RES_CTLR=y CONFIG_PREEMPT=y mmotm fails to boot:
> Kernel panic - not syncing: No init found; after lots of scheduling
> while atomics, starting from when async_thread does sd_probe_async.
>
> mem_cgroup_soft_limit_check() was doing an unbalanced get_cpu():
> don't get_cpu if we won't need it, and put_cpu if we did get_cpu.
>
> And fix the silliness of passing it an "over_soft_limit" argument
> that just tells it to return false when false.
>
> Signed-off-by: Hugh Dickins <hugh.dickins@tiscali.co.uk>
Fair enough (I guess my intention of keeping if blocks outside for
each call site, does not pay sufficiently enough), Thanks for the cleanup
Reviewed-by: Balbir Singh <balbir@linux.vnet.ibm.com>
--
Balbir
next prev parent reply other threads:[~2009-08-02 16:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 14:07 Jiri Slaby
2009-08-01 14:08 ` Jiri Slaby
2009-08-01 20:02 ` Balbir Singh
2009-08-01 22:09 ` Hugh Dickins
2009-08-01 22:26 ` Balbir Singh
2009-08-02 16:12 ` Hugh Dickins
2009-08-02 16:18 ` KAMEZAWA Hiroyuki
2009-08-02 16:27 ` Balbir Singh [this message]
2009-08-01 22:44 ` Balbir Singh
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=20090802162732.GE8514@balbir.in.ibm.com \
--to=balbir@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=hugh.dickins@tiscali.co.uk \
--cc=jirislaby@gmail.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.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
all inboxes | Powered by JetHome®