Hello.
Is /proc/iomem updated upon memory hotplug event.
Yes. I just checked that (yesterday).
I think it would make sense to extend /sys/firmware/memmap on
hot-plugging. Just because on reboot, the firmware will see that
memory, too, and report it. However, we need a way
* Vivek Goyal [2008-07-21 09:39]:
But the point is, if /sys/devices/system/memory also represents all
the physical memory present in the system then it might be not be
justified to create another similar interface. (Until and unless there
is something unique about /sys/firmware/memmap).
But
On Mon, Jul 21, 2008 at 03:47:33PM +0200, Bernhard Walle wrote:
* Vivek Goyal [2008-07-21 09:39]:
But the point is, if /sys/devices/system/memory also represents all
the physical memory present in the system then it might be not be
justified to create another similar interface. (Until
On Sun, 2008-07-20 at 01:11 +0200, Vegard Nossum wrote:
Maybe the firmware memmap code can simply run a little later in the
boot sequence?
Heh, I'm catching up on this thread...
It is possible that it could run later. But, I do know that there are
at least a couple of these tables (on various
Am Sonntag, den 20.07.2008, 02:01 -0700 schrieb Dave Hansen:
On Sun, 2008-07-20 at 01:11 +0200, Vegard Nossum wrote:
Maybe the firmware memmap code can simply run a little later in the
boot sequence?
Heh, I'm catching up on this thread...
On that thread?
* Dave Hansen [EMAIL PROTECTED] [2008-07-20 02:01]:
It is possible that it could run later. But, I do know that there are
at least a couple of these tables (on various arches) that we toss out
of memory or become unavailable later in boot.
I do this this:
sysfs: add
* Bernhard Walle [EMAIL PROTECTED] [2008-07-20 15:03]:
Because I didn't know that interface. And because I don't see that
interface on my two systems that I just checked. i386 and x86-64. What
do I have to do to enable that interface?
That interface depends on CONFIG_MEMORY_HOTPLUG. But
