All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: mark.rutland@arm.com, linux-mm@kvack.org, geoff@infradead.org,
	kexec@lists.infradead.org, will.deacon@arm.com,
	AKASHI Takahiro <takahiro.akashi@linaro.org>,
	james.morse@arm.com, bauerman@linux.vnet.ibm.com,
	dyoung@redhat.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v28 1/9] memblock: add memblock_cap_memory_range()
Date: Thu, 24 Nov 2016 10:26:21 +0000	[thread overview]
Message-ID: <20161124102619.GC78338@MBP.local> (raw)
In-Reply-To: <20161124095717.7037-1-takahiro.akashi@linaro.org>

Hi Andrew,

On Thu, Nov 24, 2016 at 06:57:17PM +0900, AKASHI Takahiro wrote:
> Add memblock_cap_memory_range() which will remove all the memblock regions
> except the memory range specified in the arguments. In addition, rework is
> done on memblock_mem_limit_remove_map() to re-implement it using
> memblock_cap_memory_range().
> 
> This function, like memblock_mem_limit_remove_map(), will not remove
> memblocks with MEMMAP_NOMAP attribute as they may be mapped and accessed
> later as "device memory."
> See the commit a571d4eb55d8 ("mm/memblock.c: add new infrastructure to
> address the mem limit issue").
> 
> This function is used, in a succeeding patch in the series of arm64 kdump
> suuport, to limit the range of usable memory, or System RAM, on crash dump
> kernel.
> (Please note that "mem=" parameter is of little use for this purpose.)
> 
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> Reviewed-by: Will Deacon <will.deacon@arm.com>
> Cc: linux-mm@kvack.org
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
>  include/linux/memblock.h |  1 +
>  mm/memblock.c            | 44 +++++++++++++++++++++++++++++---------------
>  2 files changed, 30 insertions(+), 15 deletions(-)

Are you OK with this patch to go in via the arm64 tree (together with
the other patches in this series)?

Thanks.

-- 
Catalin

_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

WARNING: multiple messages have this Message-ID (diff)
From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v28 1/9] memblock: add memblock_cap_memory_range()
Date: Thu, 24 Nov 2016 10:26:21 +0000	[thread overview]
Message-ID: <20161124102619.GC78338@MBP.local> (raw)
In-Reply-To: <20161124095717.7037-1-takahiro.akashi@linaro.org>

Hi Andrew,

On Thu, Nov 24, 2016 at 06:57:17PM +0900, AKASHI Takahiro wrote:
> Add memblock_cap_memory_range() which will remove all the memblock regions
> except the memory range specified in the arguments. In addition, rework is
> done on memblock_mem_limit_remove_map() to re-implement it using
> memblock_cap_memory_range().
> 
> This function, like memblock_mem_limit_remove_map(), will not remove
> memblocks with MEMMAP_NOMAP attribute as they may be mapped and accessed
> later as "device memory."
> See the commit a571d4eb55d8 ("mm/memblock.c: add new infrastructure to
> address the mem limit issue").
> 
> This function is used, in a succeeding patch in the series of arm64 kdump
> suuport, to limit the range of usable memory, or System RAM, on crash dump
> kernel.
> (Please note that "mem=" parameter is of little use for this purpose.)
> 
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> Reviewed-by: Will Deacon <will.deacon@arm.com>
> Cc: linux-mm at kvack.org
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
>  include/linux/memblock.h |  1 +
>  mm/memblock.c            | 44 +++++++++++++++++++++++++++++---------------
>  2 files changed, 30 insertions(+), 15 deletions(-)

Are you OK with this patch to go in via the arm64 tree (together with
the other patches in this series)?

Thanks.

-- 
Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: AKASHI Takahiro <takahiro.akashi@linaro.org>,
	will.deacon@arm.com, mark.rutland@arm.com, geoff@infradead.org,
	kexec@lists.infradead.org, linux-mm@kvack.org,
	james.morse@arm.com, bauerman@linux.vnet.ibm.com,
	dyoung@redhat.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v28 1/9] memblock: add memblock_cap_memory_range()
Date: Thu, 24 Nov 2016 10:26:21 +0000	[thread overview]
Message-ID: <20161124102619.GC78338@MBP.local> (raw)
In-Reply-To: <20161124095717.7037-1-takahiro.akashi@linaro.org>

Hi Andrew,

On Thu, Nov 24, 2016 at 06:57:17PM +0900, AKASHI Takahiro wrote:
> Add memblock_cap_memory_range() which will remove all the memblock regions
> except the memory range specified in the arguments. In addition, rework is
> done on memblock_mem_limit_remove_map() to re-implement it using
> memblock_cap_memory_range().
> 
> This function, like memblock_mem_limit_remove_map(), will not remove
> memblocks with MEMMAP_NOMAP attribute as they may be mapped and accessed
> later as "device memory."
> See the commit a571d4eb55d8 ("mm/memblock.c: add new infrastructure to
> address the mem limit issue").
> 
> This function is used, in a succeeding patch in the series of arm64 kdump
> suuport, to limit the range of usable memory, or System RAM, on crash dump
> kernel.
> (Please note that "mem=" parameter is of little use for this purpose.)
> 
> Signed-off-by: AKASHI Takahiro <takahiro.akashi@linaro.org>
> Reviewed-by: Will Deacon <will.deacon@arm.com>
> Cc: linux-mm@kvack.org
> Cc: Andrew Morton <akpm@linux-foundation.org>
> ---
>  include/linux/memblock.h |  1 +
>  mm/memblock.c            | 44 +++++++++++++++++++++++++++++---------------
>  2 files changed, 30 insertions(+), 15 deletions(-)

Are you OK with this patch to go in via the arm64 tree (together with
the other patches in this series)?

Thanks.

-- 
Catalin

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2016-11-24 10:26 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  9:55 [PATCH v28 0/9] arm64: add kdump support AKASHI Takahiro
2016-11-24  9:55 ` AKASHI Takahiro
2016-11-24  9:57 ` [PATCH v28 1/9] memblock: add memblock_cap_memory_range() AKASHI Takahiro
2016-11-24  9:57   ` AKASHI Takahiro
2016-11-24  9:57   ` AKASHI Takahiro
2016-11-24 10:26   ` Catalin Marinas [this message]
2016-11-24 10:26     ` Catalin Marinas
2016-11-24 10:26     ` Catalin Marinas
2016-11-24  9:58 ` [PATCH v28 2/9] arm64: limit memory regions based on DT property, usable-memory-range AKASHI Takahiro
2016-11-24  9:58   ` AKASHI Takahiro
2016-11-24  9:58 ` [PATCH v28 3/9] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-11-24  9:58   ` AKASHI Takahiro
2016-11-24  9:58 ` [PATCH v28 4/9] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-11-24  9:58   ` AKASHI Takahiro
2016-11-28 15:04   ` Catalin Marinas
2016-11-28 15:04     ` Catalin Marinas
2016-11-29  5:47     ` AKASHI Takahiro
2016-11-29  5:47       ` AKASHI Takahiro
2016-11-24  9:58 ` [PATCH v28 5/9] arm64: kdump: add VMCOREINFO's for user-space tools AKASHI Takahiro
2016-11-24  9:58   ` AKASHI Takahiro
2016-11-24  9:58 ` [PATCH v28 6/9] arm64: kdump: provide /proc/vmcore file AKASHI Takahiro
2016-11-24  9:58   ` AKASHI Takahiro
2016-11-24  9:58 ` [PATCH v28 7/9] arm64: kdump: enable kdump in defconfig AKASHI Takahiro
2016-11-24  9:58   ` AKASHI Takahiro
2016-11-24  9:58 ` [PATCH v28 8/9] Documentation: kdump: describe arm64 port AKASHI Takahiro
2016-11-24  9:58   ` AKASHI Takahiro
2016-11-24  9:59 ` [PATCH v28 9/9] Documentation: dt: chosen properties for arm64 kdump AKASHI Takahiro
2016-11-24  9:59   ` AKASHI Takahiro
2016-11-24  9:59   ` AKASHI Takahiro
2016-11-24 17:14   ` Catalin Marinas
2016-11-24 17:14     ` Catalin Marinas
2016-11-24 17:14     ` Catalin Marinas
2016-11-30 20:44     ` Rob Herring
2016-11-30 20:44       ` Rob Herring
2016-11-30 20:44       ` Rob Herring
2016-11-25 16:20 ` [PATCH v28 0/9] arm64: add kdump support Catalin Marinas
2016-11-25 16:20   ` Catalin Marinas
2016-11-29 11:05   ` Will Deacon
2016-11-29 11:05     ` Will Deacon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161124102619.GC78338@MBP.local \
    --to=catalin.marinas@arm.com \
    --cc=akpm@linux-foundation.org \
    --cc=bauerman@linux.vnet.ibm.com \
    --cc=dyoung@redhat.com \
    --cc=geoff@infradead.org \
    --cc=james.morse@arm.com \
    --cc=kexec@lists.infradead.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=mark.rutland@arm.com \
    --cc=takahiro.akashi@linaro.org \
    --cc=will.deacon@arm.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.