Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753436Ab0ALBxx (ORCPT ); Mon, 11 Jan 2010 20:53:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752883Ab0ALBxv (ORCPT ); Mon, 11 Jan 2010 20:53:51 -0500 Received: from fgwmail6.fujitsu.co.jp ([192.51.44.36]:49661 "EHLO fgwmail6.fujitsu.co.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751743Ab0ALBxu (ORCPT ); Mon, 11 Jan 2010 20:53:50 -0500 X-SecurityPolicyCheck-FJ: OK by FujitsuOutboundMailChecker v1.3.1 Date: Tue, 12 Jan 2010 10:50:12 +0900 From: KAMEZAWA Hiroyuki To: KAMEZAWA Hiroyuki Cc: Andi Kleen , Wu Fengguang , "Zheng, Shaohui" , "linux-mm@kvack.org" , "akpm@linux-foundation.org" , "linux-kernel@vger.kernel.org" , "y-goto@jp.fujitsu.com" , Dave Hansen , "x86@kernel.org" Subject: Re: [PATCH - resend] Memory-Hotplug: Fix the bug on interface /dev/mem for 64-bit kernel(v1) Message-Id: <20100112105012.4a210a1c.kamezawa.hiroyu@jp.fujitsu.com> In-Reply-To: <20100112103944.a9b1db76.kamezawa.hiroyu@jp.fujitsu.com> References: <20100108124851.GB6153@localhost> <20100111124303.GA21408@localhost> <20100112093031.0fc6877f.kamezawa.hiroyu@jp.fujitsu.com> <4B4BD281.4080009@linux.intel.com> <20100112103944.a9b1db76.kamezawa.hiroyu@jp.fujitsu.com> Organization: FUJITSU Co. LTD. X-Mailer: Sylpheed 2.7.1 (GTK+ 2.10.14; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1079 Lines: 37 On Tue, 12 Jan 2010 10:39:44 +0900 KAMEZAWA Hiroyuki wrote: > On Tue, 12 Jan 2010 02:38:09 +0100 > Andi Kleen wrote: > > > > > > Hmmm....could you rewrite /dev/mem to use kernel/resource.c other than > > > modifing e820 maps. ? > > > > Sorry but responding to bug fixes with "could you please rewrite ..." is > > not considered fair. Shaohui is just trying to fix a bug here, not redesigning > > a subsystem. > > > Quick hack for bug fix is okay to me. > Just an information. We already check kenerke/resource.c's resource information, here. read_mem() -> range_is_allowed() -> devmem_is_allowd() -> iomem_is_exclusive() extra calls of page_is_ram() to ask architecture's map seems redundunt. But, I know PPC guys doesn't use ioresource.c, hehe. Thanks, -Kame -- 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/