From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]) by merlin.infradead.org with esmtps (Exim 4.80.1 #2 (Red Hat Linux)) id 1Ud9lA-0004bt-M4 for kexec@lists.infradead.org; Fri, 17 May 2013 01:47:06 +0000 Received: from m4.gw.fujitsu.co.jp (unknown [10.0.50.74]) by fgwmail6.fujitsu.co.jp (Postfix) with ESMTP id D7E833EE0AE for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from smail (m4 [127.0.0.1]) by outgoing.m4.gw.fujitsu.co.jp (Postfix) with ESMTP id CB93E45DE51 for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (s4.gw.fujitsu.co.jp [10.0.50.94]) by m4.gw.fujitsu.co.jp (Postfix) with ESMTP id B523345DE4E for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from s4.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id A14DAE08001 for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from m1000.s.css.fujitsu.com (m1000.s.css.fujitsu.com [10.240.81.136]) by s4.gw.fujitsu.co.jp (Postfix) with ESMTP id 59A491DB802F for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Message-ID: <51958BC0.207@jp.fujitsu.com> Date: Fri, 17 May 2013 10:45:36 +0900 From: HATAYAMA Daisuke MIME-Version: 1.0 Subject: Re: [PATCH v6 0/8] kdump, vmcore: support mmap() on /proc/vmcore References: <20130515090507.28109.28956.stgit@localhost6.localdomain6> <51957469.2000008@zytor.com> In-Reply-To: <51957469.2000008@zytor.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="us-ascii"; Format="flowed" Sender: "kexec" Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: "H. Peter Anvin" Cc: riel@redhat.com, hughd@google.com, jingbai.ma@hp.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, lisa.mitchell@hp.com, linux-mm@kvack.org, kumagai-atsushi@mxc.nes.nec.co.jp, ebiederm@xmission.com, kosaki.motohiro@jp.fujitsu.com, zhangyanfei@cn.fujitsu.com, akpm@linux-foundation.org, walken@google.com, cpw@sgi.com, vgoyal@redhat.com (2013/05/17 9:06), H. Peter Anvin wrote: > On 05/15/2013 02:05 AM, HATAYAMA Daisuke wrote: >> Currently, read to /proc/vmcore is done by read_oldmem() that uses >> ioremap/iounmap per a single page. For example, if memory is 1GB, >> ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144 >> times. This causes big performance degradation. > > read_oldmem() is fundamentally broken and unsafe. It needs to be > unified with the plain /dev/mem code and any missing functionality fixed > instead of "let's just do a whole new driver". > > -hpa Do you mean range_is_allowed should be extended so that it checks according to memory map passed from the 1st kernel? BTW, read request to read_oldmem via read_vmcore and mmap on some part of the 1st kernel, seems safe since it's always restrected to within the memory map. Or is there other missing point? -- Thanks. HATAYAMA, Daisuke _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from psmtp.com (na3sys010amx150.postini.com [74.125.245.150]) by kanga.kvack.org (Postfix) with SMTP id 92FFD6B0032 for ; Thu, 16 May 2013 21:46:41 -0400 (EDT) Received: from m2.gw.fujitsu.co.jp (unknown [10.0.50.72]) by fgwmail5.fujitsu.co.jp (Postfix) with ESMTP id D97953EE0C0 for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from smail (m2 [127.0.0.1]) by outgoing.m2.gw.fujitsu.co.jp (Postfix) with ESMTP id C918845DE54 for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (s2.gw.fujitsu.co.jp [10.0.50.92]) by m2.gw.fujitsu.co.jp (Postfix) with ESMTP id B1D2145DE4D for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from s2.gw.fujitsu.co.jp (localhost.localdomain [127.0.0.1]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id A4DA81DB803C for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Received: from m1000.s.css.fujitsu.com (m1000.s.css.fujitsu.com [10.240.81.136]) by s2.gw.fujitsu.co.jp (Postfix) with ESMTP id 58A921DB8038 for ; Fri, 17 May 2013 10:46:39 +0900 (JST) Message-ID: <51958BC0.207@jp.fujitsu.com> Date: Fri, 17 May 2013 10:45:36 +0900 From: HATAYAMA Daisuke MIME-Version: 1.0 Subject: Re: [PATCH v6 0/8] kdump, vmcore: support mmap() on /proc/vmcore References: <20130515090507.28109.28956.stgit@localhost6.localdomain6> <51957469.2000008@zytor.com> In-Reply-To: <51957469.2000008@zytor.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-linux-mm@kvack.org List-ID: To: "H. Peter Anvin" Cc: vgoyal@redhat.com, ebiederm@xmission.com, akpm@linux-foundation.org, cpw@sgi.com, kumagai-atsushi@mxc.nes.nec.co.jp, lisa.mitchell@hp.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, zhangyanfei@cn.fujitsu.com, jingbai.ma@hp.com, linux-mm@kvack.org, riel@redhat.com, walken@google.com, hughd@google.com, kosaki.motohiro@jp.fujitsu.com (2013/05/17 9:06), H. Peter Anvin wrote: > On 05/15/2013 02:05 AM, HATAYAMA Daisuke wrote: >> Currently, read to /proc/vmcore is done by read_oldmem() that uses >> ioremap/iounmap per a single page. For example, if memory is 1GB, >> ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144 >> times. This causes big performance degradation. > > read_oldmem() is fundamentally broken and unsafe. It needs to be > unified with the plain /dev/mem code and any missing functionality fixed > instead of "let's just do a whole new driver". > > -hpa Do you mean range_is_allowed should be extended so that it checks according to memory map passed from the 1st kernel? BTW, read request to read_oldmem via read_vmcore and mmap on some part of the 1st kernel, seems safe since it's always restrected to within the memory map. Or is there other missing point? -- Thanks. HATAYAMA, Daisuke -- 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752574Ab3EQBqm (ORCPT ); Thu, 16 May 2013 21:46:42 -0400 Received: from fgwmail5.fujitsu.co.jp ([192.51.44.35]:48590 "EHLO fgwmail5.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751498Ab3EQBql (ORCPT ); Thu, 16 May 2013 21:46:41 -0400 X-SecurityPolicyCheck: OK by SHieldMailChecker v1.8.9 X-SHieldMailCheckerPolicyVersion: FJ-ISEC-20120718-2 Message-ID: <51958BC0.207@jp.fujitsu.com> Date: Fri, 17 May 2013 10:45:36 +0900 From: HATAYAMA Daisuke User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: "H. Peter Anvin" CC: vgoyal@redhat.com, ebiederm@xmission.com, akpm@linux-foundation.org, cpw@sgi.com, kumagai-atsushi@mxc.nes.nec.co.jp, lisa.mitchell@hp.com, kexec@lists.infradead.org, linux-kernel@vger.kernel.org, zhangyanfei@cn.fujitsu.com, jingbai.ma@hp.com, linux-mm@kvack.org, riel@redhat.com, walken@google.com, hughd@google.com, kosaki.motohiro@jp.fujitsu.com Subject: Re: [PATCH v6 0/8] kdump, vmcore: support mmap() on /proc/vmcore References: <20130515090507.28109.28956.stgit@localhost6.localdomain6> <51957469.2000008@zytor.com> In-Reply-To: <51957469.2000008@zytor.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 (2013/05/17 9:06), H. Peter Anvin wrote: > On 05/15/2013 02:05 AM, HATAYAMA Daisuke wrote: >> Currently, read to /proc/vmcore is done by read_oldmem() that uses >> ioremap/iounmap per a single page. For example, if memory is 1GB, >> ioremap/iounmap is called (1GB / 4KB)-times, that is, 262144 >> times. This causes big performance degradation. > > read_oldmem() is fundamentally broken and unsafe. It needs to be > unified with the plain /dev/mem code and any missing functionality fixed > instead of "let's just do a whole new driver". > > -hpa Do you mean range_is_allowed should be extended so that it checks according to memory map passed from the 1st kernel? BTW, read request to read_oldmem via read_vmcore and mmap on some part of the 1st kernel, seems safe since it's always restrected to within the memory map. Or is there other missing point? -- Thanks. HATAYAMA, Daisuke