Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262384AbVBCKKh (ORCPT ); Thu, 3 Feb 2005 05:10:37 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262474AbVBCKKe (ORCPT ); Thu, 3 Feb 2005 05:10:34 -0500 Received: from ebiederm.dsl.xmission.com ([166.70.28.69]:30850 "EHLO ebiederm.dsl.xmission.com") by vger.kernel.org with ESMTP id S262363AbVBCKKC (ORCPT ); Thu, 3 Feb 2005 05:10:02 -0500 To: Hirokazu Takahashi Cc: vgoyal@in.ibm.com, akpm@osdl.org, fastboot@lists.osdl.org, linux-kernel@vger.kernel.org, maneesh@in.ibm.com, hari@in.ibm.com, suparna@in.ibm.com Subject: Re: [Fastboot] [PATCH] Reserving backup region for kexec based crashdumps. References: <1106833527.15652.146.camel@2fwv946.in.ibm.com> <20050203.160252.104031714.taka@valinux.co.jp> <1107421303.11609.183.camel@2fwv946.in.ibm.com> <20050203.183747.85413533.taka@valinux.co.jp> From: ebiederm@xmission.com (Eric W. Biederman) Date: 03 Feb 2005 03:07:58 -0700 In-Reply-To: <20050203.183747.85413533.taka@valinux.co.jp> Message-ID: User-Agent: Gnus/5.0808 (Gnus v5.8.8) Emacs/21.2 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1477 Lines: 35 Hirokazu Takahashi writes: > Hi Vivek, > > > > Hi Vivek and Eric, > > > > > > IMHO, why don't we swap not only the contents of the top 640K > > > but also kernel working memory for kdump kernel? > > > > > > Initial patches of kdump had adopted the same approach but given the > > fact devices are not stopped during transition to new kernel after a > > panic, it carried inherent risk of some DMA going on and corrupting the > > new kernel/data structures. Hence the idea of running the kernel from a > > reserved location came up. This should be DMA safe as long as DMA is not > > misdirected. > > I see, that makes sense. > But I'm not sure yet that it's safe to access the top of 640MB. 640K? > I wonder how kmalloc(GFP_DMA) works in a kdump kernel. All that happens there is a one line change to vmlinux.lds.S that causes the kernel to live at a different physical and virtual address. So everything works as normal. I do agree that it is risky to use the first 640K for normal work. But on the list of things to fix it is a minor war, and even if we back up that region of memory we don't need to use it. There are still remain a lot of code reviews to ensure the code is generally safe. Eric - 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/