Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1757829Ab2K0GVt (ORCPT ); Tue, 27 Nov 2012 01:21:49 -0500 Received: from terminus.zytor.com ([198.137.202.10]:47331 "EHLO mail.zytor.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754499Ab2K0GVs (ORCPT ); Tue, 27 Nov 2012 01:21:48 -0500 Message-ID: <50B45BBA.3090300@zytor.com> Date: Mon, 26 Nov 2012 22:20:42 -0800 From: "H. Peter Anvin" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/17.0 Thunderbird/17.0 MIME-Version: 1.0 To: Tang Chen CC: wujianguo , akpm@linux-foundation.org, rob@landley.net, isimatu.yasuaki@jp.fujitsu.com, laijs@cn.fujitsu.com, wency@cn.fujitsu.com, linfeng@cn.fujitsu.com, jiang.liu@huawei.com, yinghai@kernel.org, kosaki.motohiro@jp.fujitsu.com, minchan.kim@gmail.com, mgorman@suse.de, rientjes@google.com, rusty@rustcorp.com.au, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-doc@vger.kernel.org Subject: Re: [PATCH v2 0/5] Add movablecore_map boot option References: <1353667445-7593-1-git-send-email-tangchen@cn.fujitsu.com> <50B42F32.4050107@gmail.com> <50B45318.3020605@cn.fujitsu.com> In-Reply-To: <50B45318.3020605@cn.fujitsu.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 702 Lines: 22 On 11/26/2012 09:43 PM, Tang Chen wrote: > > And about how to fix it, as you said, we can handle the situation if > user specified DMA address as movable. But how to handle "too little > memory for kernel to start" case ? Is there any info about how much > at least memory kernel needs ? > Not really, and it depends on so many variables. -hpa -- H. Peter Anvin, Intel Open Source Technology Center I work for Intel. I don't speak on their behalf. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/