From: Mike Galbraith <efault@gmx.de>
To: Xiaotian Feng <xtfeng@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org,
Xiaotian Feng <dannyfeng@tencent.com>,
Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] sched, autogroup: fix kernel crashes caused by runtime disable autogroup
Date: Fri, 26 Oct 2012 13:29:31 -0700 [thread overview]
Message-ID: <1351283371.16639.111.camel@maggy.simpson.net> (raw)
In-Reply-To: <1350736696.5123.24.camel@maggy.simpson.net>
On Sat, 2012-10-20 at 08:38 -0400, Mike Galbraith wrote:
> So what I would do is either let the user decide once at boot, in which
> case if off, creating groups would be stupid), or, just rip autogroup
> completely out, since systemd is taking over the known universe anyway.
I'm traveling, but have somewhat functional connectivity ATM, so..
Peter: which would prefer. Simple noautogroup -> autogroup one time
only boottime enable, and autogroup lives on (I like it for my laptop)
with backport for stable, or fix stable as above, and whack it upstream
as annoyance since systemd (one daemon to bind them..) is being adopted
everywhere?
(other?.. fully function on/off switch? revert 800d4d30?)
-Mike
next prev parent reply other threads:[~2012-10-26 20:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 8:36 Xiaotian Feng
2012-10-19 13:42 ` Peter Zijlstra
2012-10-20 6:42 ` Xiaotian Feng
2012-10-20 12:38 ` Mike Galbraith
2012-10-26 20:29 ` Mike Galbraith [this message]
2012-10-27 18:26 ` [PATCH] sched, autogroup: fix crash on reboot when autogroup is disabled Mike Galbraith
2012-10-28 10:25 ` Ingo Molnar
2012-10-28 13:13 ` Mike Galbraith
2012-10-28 13:19 ` Ingo Molnar
2012-10-28 13:33 ` Mike Galbraith
2012-10-28 14:05 ` Ingo Molnar
2012-10-28 14:27 ` Mike Galbraith
2012-10-28 19:19 ` [PATCH] V2 " Mike Galbraith
2012-10-29 2:42 ` Xiaotian Feng
2012-10-29 12:10 ` Mike Galbraith
2012-10-30 12:28 ` [tip:sched/urgent] sched/autogroup: Fix " tip-bot for Mike Galbraith
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=1351283371.16639.111.camel@maggy.simpson.net \
--to=efault@gmx.de \
--cc=dannyfeng@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=xtfeng@gmail.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®