All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, will.deacon@arm.com,
	catalin.marinas@arm.com
Cc: mark.rutland@arm.com, mhocko@suse.com, ira.weiny@intel.com,
	robin.murphy@arm.com, cai@lca.pw, logang@deltatee.com,
	james.morse@arm.com, cpandya@codeaurora.org,
	arunks@codeaurora.org, dan.j.williams@intel.com,
	mgorman@techsingularity.net, osalvador@suse.de
Subject: Re: [PATCH V2 0/2] arm64/mm: Enable memory hot remove
Date: Mon, 13 May 2019 10:22:11 +0200	[thread overview]
Message-ID: <bbfc6ede-01b2-2331-112e-fa28bc2591fb@redhat.com> (raw)
In-Reply-To: <1555221553-18845-1-git-send-email-anshuman.khandual@arm.com>

On 14.04.19 07:59, Anshuman Khandual wrote:
> This series enables memory hot remove on arm64 after fixing a memblock
> removal ordering problem in generic __remove_memory(). This is based
> on the following arm64 working tree.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> 
> Testing:
> 
> Tested hot remove on arm64 for all 4K, 16K, 64K page config options with
> all possible VA_BITS and PGTABLE_LEVELS combinations. Build tested on non
> arm64 platforms.
> 
> Changes in V2:
> 
> - Added all received review and ack tags
> - Split the series from ZONE_DEVICE enablement for better review
> 
> - Moved memblock re-order patch to the front as per Robin Murphy
> - Updated commit message on memblock re-order patch per Michal Hocko
> 
> - Dropped [pmd|pud]_large() definitions
> - Used existing [pmd|pud]_sect() instead of earlier [pmd|pud]_large()
> - Removed __meminit and __ref tags as per Oscar Salvador
> - Dropped unnecessary 'ret' init in arch_add_memory() per Robin Murphy
> - Skipped calling into pgtable_page_dtor() for linear mapping page table
>   pages and updated all relevant functions
> 
> Changes in V1: (https://lkml.org/lkml/2019/4/3/28)
> 
> Anshuman Khandual (2):
>   mm/hotplug: Reorder arch_remove_memory() call in __remove_memory()
>   arm64/mm: Enable memory hot remove
> 
>  arch/arm64/Kconfig               |   3 +
>  arch/arm64/include/asm/pgtable.h |   2 +
>  arch/arm64/mm/mmu.c              | 221 ++++++++++++++++++++++++++++++++++++++-
>  mm/memory_hotplug.c              |   3 +-
>  4 files changed, 225 insertions(+), 4 deletions(-)
> 

What's the progress of this series? I'll need arch_remove_memory() for
the series

[PATCH v2 0/8] mm/memory_hotplug: Factor out memory block device handling

-- 

Thanks,

David / dhildenb

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

WARNING: multiple messages have this Message-ID (diff)
From: David Hildenbrand <david@redhat.com>
To: Anshuman Khandual <anshuman.khandual@arm.com>,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org, linux-mm@kvack.org,
	akpm@linux-foundation.org, will.deacon@arm.com,
	catalin.marinas@arm.com
Cc: mhocko@suse.com, mgorman@techsingularity.net,
	james.morse@arm.com, mark.rutland@arm.com, robin.murphy@arm.com,
	cpandya@codeaurora.org, arunks@codeaurora.org,
	dan.j.williams@intel.com, osalvador@suse.de, cai@lca.pw,
	logang@deltatee.com, ira.weiny@intel.com
Subject: Re: [PATCH V2 0/2] arm64/mm: Enable memory hot remove
Date: Mon, 13 May 2019 10:22:11 +0200	[thread overview]
Message-ID: <bbfc6ede-01b2-2331-112e-fa28bc2591fb@redhat.com> (raw)
In-Reply-To: <1555221553-18845-1-git-send-email-anshuman.khandual@arm.com>

On 14.04.19 07:59, Anshuman Khandual wrote:
> This series enables memory hot remove on arm64 after fixing a memblock
> removal ordering problem in generic __remove_memory(). This is based
> on the following arm64 working tree.
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux.git for-next/core
> 
> Testing:
> 
> Tested hot remove on arm64 for all 4K, 16K, 64K page config options with
> all possible VA_BITS and PGTABLE_LEVELS combinations. Build tested on non
> arm64 platforms.
> 
> Changes in V2:
> 
> - Added all received review and ack tags
> - Split the series from ZONE_DEVICE enablement for better review
> 
> - Moved memblock re-order patch to the front as per Robin Murphy
> - Updated commit message on memblock re-order patch per Michal Hocko
> 
> - Dropped [pmd|pud]_large() definitions
> - Used existing [pmd|pud]_sect() instead of earlier [pmd|pud]_large()
> - Removed __meminit and __ref tags as per Oscar Salvador
> - Dropped unnecessary 'ret' init in arch_add_memory() per Robin Murphy
> - Skipped calling into pgtable_page_dtor() for linear mapping page table
>   pages and updated all relevant functions
> 
> Changes in V1: (https://lkml.org/lkml/2019/4/3/28)
> 
> Anshuman Khandual (2):
>   mm/hotplug: Reorder arch_remove_memory() call in __remove_memory()
>   arm64/mm: Enable memory hot remove
> 
>  arch/arm64/Kconfig               |   3 +
>  arch/arm64/include/asm/pgtable.h |   2 +
>  arch/arm64/mm/mmu.c              | 221 ++++++++++++++++++++++++++++++++++++++-
>  mm/memory_hotplug.c              |   3 +-
>  4 files changed, 225 insertions(+), 4 deletions(-)
> 

What's the progress of this series? I'll need arch_remove_memory() for
the series

[PATCH v2 0/8] mm/memory_hotplug: Factor out memory block device handling

-- 

Thanks,

David / dhildenb


  parent reply	other threads:[~2019-05-13  8:22 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-14  5:59 [PATCH V2 0/2] arm64/mm: Enable memory hot remove Anshuman Khandual
2019-04-14  5:59 ` Anshuman Khandual
2019-04-14  5:59 ` [PATCH V2 1/2] mm/hotplug: Reorder arch_remove_memory() call in __remove_memory() Anshuman Khandual
2019-04-14  5:59   ` Anshuman Khandual
2019-04-15 13:58   ` David Hildenbrand
2019-04-15 13:58     ` David Hildenbrand
2019-04-16 10:12     ` Anshuman Khandual
2019-04-16 10:12       ` Anshuman Khandual
2019-04-14  5:59 ` [PATCH V2 2/2] arm64/mm: Enable memory hot remove Anshuman Khandual
2019-04-14  5:59   ` Anshuman Khandual
2019-04-15 13:48   ` Mark Rutland
2019-04-15 13:48     ` Mark Rutland
2019-04-17  9:58     ` Anshuman Khandual
2019-04-17  9:58       ` Anshuman Khandual
2019-04-17 14:21       ` Mark Rutland
2019-04-17 14:21         ` Mark Rutland
2019-04-17 16:45         ` Anshuman Khandual
2019-04-17 16:45           ` Anshuman Khandual
2019-04-17 17:39           ` Mark Rutland
2019-04-17 17:39             ` Mark Rutland
2019-04-18  5:28             ` Anshuman Khandual
2019-04-18  5:28               ` Anshuman Khandual
2019-04-23  7:31               ` Anshuman Khandual
2019-04-23  7:31                 ` Anshuman Khandual
2019-04-23  7:37                 ` David Hildenbrand
2019-04-23  7:37                   ` David Hildenbrand
2019-04-23  7:45                   ` Anshuman Khandual
2019-04-23  7:45                     ` Anshuman Khandual
2019-04-23  7:51                     ` David Hildenbrand
2019-04-23  7:51                       ` David Hildenbrand
2019-04-23  8:37                       ` Anshuman Khandual
2019-04-23  8:37                         ` Anshuman Khandual
2019-04-23 16:05                 ` Mark Rutland
2019-04-23 16:05                   ` Mark Rutland
2019-04-24  5:59                   ` Anshuman Khandual
2019-04-24  5:59                     ` Anshuman Khandual
2019-04-24  8:19                     ` Mark Rutland
2019-04-24  8:19                       ` Mark Rutland
2019-04-15 13:55   ` David Hildenbrand
2019-04-15 13:55     ` David Hildenbrand
2019-04-16  9:52     ` Anshuman Khandual
2019-04-16  9:52       ` Anshuman Khandual
2019-05-13  8:22 ` David Hildenbrand [this message]
2019-05-13  8:22   ` [PATCH V2 0/2] " David Hildenbrand
2019-05-13  8:37   ` Anshuman Khandual
2019-05-13  8:37     ` Anshuman Khandual
2019-05-13 10:01     ` David Hildenbrand
2019-05-13 10:01       ` David Hildenbrand

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=bbfc6ede-01b2-2331-112e-fa28bc2591fb@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=arunks@codeaurora.org \
    --cc=cai@lca.pw \
    --cc=catalin.marinas@arm.com \
    --cc=cpandya@codeaurora.org \
    --cc=dan.j.williams@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=james.morse@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=logang@deltatee.com \
    --cc=mark.rutland@arm.com \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@suse.com \
    --cc=osalvador@suse.de \
    --cc=robin.murphy@arm.com \
    --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.