Re: [PATCH] memory hotadd fixes [1/5] not-aligned memory hotadd handling fix

> ioresouce handling code in memory hotplug allows not-aligned memory hot add.
> But when memmap and other memory structures are initialized, parameters
> should be aligned. (if not aligned, initialization of mem_map will do wrong,
> it assumes parameters are aligned.) This patch fix it.
> 
> And this patch allows ioresource collision check to handle -EEXIST.
>
> Signed-Off-By: KAMEZAWA Hiroyuki <[email protected]>
> 
> 
>  mm/memory_hotplug.c |   23 ++++++++++++++++-------
>  1 files changed, 16 insertions(+), 7 deletions(-)

This code looks and boots fine for me with x86_64.

 
Acked-by: Keith Mannthey <[email protected]>

-
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/

---

• References:
  • [PATCH] memory hotadd fixes [1/5] not-aligned memory hotadd handling fix
    • From: KAMEZAWA Hiroyuki <[email protected]>

• Prev by Date: Re: [PATCH -rt DO NOT APPLY] Fix for tg3 networking lockup
• Next by Date: Re: [PATCH] memory hotadd fixes [2/5] change find_next_system_ram's return value manner
• Previous by thread: Re: [PATCH] memory hotadd fixes [1/5] not-aligned memory hotadd handling fix
• Next by thread: [PATCH] memory hotadd fixes [2/5] change find_next_system_ram's return value manner
• 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]