From mboxrd@z Thu Jan 1 00:00:00 1970 From: KOSAKI Motohiro Subject: Re: [PATCH part5 0/7] Arrange hotpluggable memory as ZONE_MOVABLE. Date: Wed, 14 Aug 2013 21:44:19 -0400 Message-ID: <520C3273.10605@gmail.com> References: <520BC950.1030806@gmail.com> <20130814182342.GG28628@htj.dyndns.org> <520BDD2F.2060909@gmail.com> <20130814195541.GH28628@htj.dyndns.org> <520BE891.8090004@gmail.com> <20130814203538.GK28628@htj.dyndns.org> <520BF3E3.5030006@gmail.com> <20130814213637.GO28628@htj.dyndns.org> <520C2A06.5020007@gmail.com> <20130815012133.GQ28628@htj.dyndns.org> <20130815013346.GR28628@htj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20130815013346.GR28628@htj.dyndns.org> Sender: owner-linux-mm@kvack.org To: Tejun Heo Cc: KOSAKI Motohiro , Tang Chen , Tang Chen , robert.moore@intel.com, lv.zheng@intel.com, rjw@sisk.pl, lenb@kernel.org, tglx@linutronix.de, mingo@elte.hu, hpa@zytor.com, akpm@linux-foundation.org, trenn@suse.de, yinghai@kernel.org, jiang.liu@huawei.com, wency@cn.fujitsu.com, laijs@cn.fujitsu.com, isimatu.yasuaki@jp.fujitsu.com, izumi.taku@jp.fujitsu.com, mgorman@suse.de, minchan@kernel.org, mina86@mina86.com, gong.chen@linux.intel.com, vasilis.liaskovitis@profitbricks.com, lwoodman@redhat.com, riel@redhat.com, jweiner@redhat.com, prarit@redhat.com, zhangyanfei@cn.fujitsu.com, yanghy@cn.fujitsu.com, x86@kernel.org, linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-acpi@vger.kernel.org List-Id: linux-acpi@vger.kernel.org (8/14/13 9:33 PM), Tejun Heo wrote: > On Wed, Aug 14, 2013 at 09:21:33PM -0400, Tejun Heo wrote: >>> Secondly, memory hotplug is now maintained I and kamezawa-san. Then, I much likely >>> have a chance to get a hotplug related bug report. For protecting my life, I don't >>> want get a false bug claim. Then, I wouldn't like to aim incomplete fallback. When >>> an admin makes mistake, they should shoot their foot, not me! >> >> Dude, it's not cool to cause users' machine to fail boot because you >> want bug report. You don't do that. There are other ways to achieve >> that. When the kernel can't make all hotpluggable nodes hotpluggable >> (I mean, it's not necessarily node aligned to begin with), generate >> warning and a debug dump with appropriate log levels. >> >> If you think causing users' machine fail boot indetermistically is >> acceptable, you really shouldn't be maintaining anything. What is >> this? Are you nuts? > > This is doubly idiotic because this is all early boot. Most users > don't even have a way to access the debug info if the machine crashes > that early. Developement convenience is something that we consider > too but, seriously, users come first. This is not your personal > playground. Don't frigging crash if you have any other option. Again, the best depend on the purpose and the goal. If someone specify to enable hotplugging, They are sure they need it. Now, any fallback achieve their goal. Their goal is not booting. If they don't have enough machine to achieve their goal, we have only one way, tell them that. If we had an alternative way, I might say an another answer. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: email@kvack.org