Re: [RFC] hotplug memory remove - walk_memory_resource for ppc64

2007-10-31 Thread Badari Pulavarty
On Wed, 2007-10-31 at 14:28 +0900, KAMEZAWA Hiroyuki wrote: On Tue, 30 Oct 2007 11:19:11 -0800 Badari Pulavarty [EMAIL PROTECTED] wrote: Hi KAME, As I mentioned while ago, ppc64 does not export information about system RAM in /proc/iomem. Looking at the code and usage scenerios I am

Re: [RFC] hotplug memory remove - walk_memory_resource for ppc64

2007-10-31 Thread KAMEZAWA Hiroyuki
On Wed, 31 Oct 2007 08:02:40 -0800 Badari Pulavarty [EMAIL PROTECTED] wrote: Paul's concern is, since we didn't need it so far - why we need this for hotplug memory remove to work ? It might break API for *unknown* applications. Its unfortunate that, hotplug memory add updates /proc/iomem. We

[RFC] hotplug memory remove - walk_memory_resource for ppc64

2007-10-30 Thread Badari Pulavarty
Hi KAME, As I mentioned while ago, ppc64 does not export information about system RAM in /proc/iomem. Looking at the code and usage scenerios I am not sure what its really serving. Could you explain what its purpose how the range can be invalid ? At least on ppc64, all the memory ranges we get

Re: [RFC] hotplug memory remove - walk_memory_resource for ppc64

2007-10-30 Thread KAMEZAWA Hiroyuki
On Wed, 31 Oct 2007 14:28:46 +0900 KAMEZAWA Hiroyuki [EMAIL PROTECTED] wrote: ioresource was good structure for remembering which memory is conventional memory and i386/x86_64/ia64 registered conventional memory as System RAM, when I posted patch. (just say System Ram is not for memory