Re: [Lhms-devel] Re: [PATCH] ACPI based Memory Hotplug Driver Patch

[Dave Hansen <haveblue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>]

On Mon, 2004-09-13 at 19:58, Keiichiro Tokunaga wrote:
> Creating links from one to the other sounds fine.  But I don't think a
> physical start address of an ACPI memory object can be detemined
> from the memsections that belong to that object.  This is because
> there is no gurantee that an ACPI memory object and a memsection
> that belongs to the object always have the same start address.  So,
> I think the interface to show physical memory range is necessary in
> both the ACPI and memsection directory.

I agree.  It's very possible that ACPI memory areas will be able to span
multiple memory sections, as the inverse.  

Although, I do wonder if we can have memory laid out in the firmware/
directory in some kind of firmware-agnostic way.  

What I want is to make sure that any hotplug memory application that is
written can use the same directories no matter whether it is a ppc
machine using OpenFirmware or an x86/ia64 machine using ACPI.  

Instead of just laying thing out in firmware/acpi, can we have another
directory that mirrors this information in the system/devices/
directory, but is identical across architectures?  

ppc64 guys, what do you think?

-- Dave



-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php