Re: [PATCH] register hot-added memory to iomem resource

KAMEZAWA Hiroyuki <[email protected]> wrote:
>
> This patch registers hot-added memory to iomem_resource.
> By this, /proc/iomem can show hot-added memory.
> This patch is against 2.6.17-rc2-mm1.
> 
> Note: kdump uses /proc/iomem to catch memory range when it is installed.
>       So, kdump should be re-installed after /proc/iomem change.
> 

What do you mean by "kdump should be reinstalled"?  The kdump userspace
tools need to re-run kexec_load()?

If so, why?

And how is kdump to know that memory was hot-added?  Do we generate a
hotplug event?

Thanks.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [Lhms-devel] Re: [PATCH] register hot-added memory to iomem resource
    • From: KAMEZAWA Hiroyuki <[email protected]>

• References:
  • [PATCH] register hot-added memory to iomem resource
    • From: KAMEZAWA Hiroyuki <[email protected]>

• Prev by Date: Re: [PATCH 10/16] ehca: event queue
• Next by Date: Re: [PATCH 1/2 (repost)] mm: serialize OOM kill operations
• Previous by thread: Re: [Lhms-devel] [PATCH] register hot-added memory to iomem resource
• Next by thread: Re: [Lhms-devel] Re: [PATCH] register hot-added memory to iomem resource
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]