From: Anshuman Khandual <anshuman.khandual@arm.com> To: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org Cc: akpm@linux-foundation.org, catalin.marinas@arm.com, will@kernel.com, mark.rutland@arm.com, Anshuman Khandual <anshuman.khandual@arm.com>, Michal Hocko <mhocko@suse.com>, Dan Williams <dan.j.williams@intel.com>, David Hildenbrand <david@redhat.com>, Yu Zhao <yuzhao@google.com>, Hsin-Yi Wang <hsinyi@chromium.org>, Thomas Gleixner <tglx@linutronix.de>, Steve Capper <steve.capper@arm.com>, linux-kernel@vger.kernel.org Subject: [PATCH 0/2] arm64/hotplug: Process MEM_OFFLINE and MEM_CANCEL_OFFLINE events Date: Wed, 15 Apr 2020 12:09:42 +0530 [thread overview] Message-ID: <1586932784-16315-1-git-send-email-anshuman.khandual@arm.com> (raw) This series improves arm64 memory event notifier (hot remove) robustness by enabling it to detect potential problems (if any) in the future. But first it enumerates memory isolation failure reasons that can be sent across a notifier. This series does not go beyond arm64 to explore if these failure reason codes could be used in other existing registered memory notifiers. Please do let me know if there is any other potential use cases, will be happy to incorporate next time around. Also should we add similar failure reasons for online_pages() as well ? This series has been tested on arm64, boot tested on x86 and build tested on multiple other platforms. This series applies on v5.7-rc1. Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Michal Hocko <mhocko@suse.com> Cc: Dan Williams <dan.j.williams@intel.com> Cc: David Hildenbrand <david@redhat.com> Cc: Yu Zhao <yuzhao@google.com> Cc: Hsin-Yi Wang <hsinyi@chromium.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will@kernel.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Steve Capper <steve.capper@arm.com> Cc: linux-arm-kernel@lists.infradead.org Cc: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org Anshuman Khandual (2): mm/hotplug: Enumerate memory range offlining failure reasons arm64/hotplug: Process MEM_OFFLINE and MEM_CANCEL_OFFLINE arch/arm64/mm/mmu.c | 52 ++++++++++++++++++++++++++++++++++++++---- drivers/base/memory.c | 9 ++++++++ include/linux/memory.h | 27 ++++++++++++++++++++++ mm/memory_hotplug.c | 24 ++++++++++++------- 4 files changed, 99 insertions(+), 13 deletions(-) -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com> To: linux-mm@kvack.org, linux-arm-kernel@lists.infradead.org Cc: mark.rutland@arm.com, Michal Hocko <mhocko@suse.com>, will@kernel.com, Anshuman Khandual <anshuman.khandual@arm.com>, catalin.marinas@arm.com, David Hildenbrand <david@redhat.com>, Steve Capper <steve.capper@arm.com>, linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>, Hsin-Yi Wang <hsinyi@chromium.org>, akpm@linux-foundation.org, Dan Williams <dan.j.williams@intel.com>, Yu Zhao <yuzhao@google.com> Subject: [PATCH 0/2] arm64/hotplug: Process MEM_OFFLINE and MEM_CANCEL_OFFLINE events Date: Wed, 15 Apr 2020 12:09:42 +0530 [thread overview] Message-ID: <1586932784-16315-1-git-send-email-anshuman.khandual@arm.com> (raw) This series improves arm64 memory event notifier (hot remove) robustness by enabling it to detect potential problems (if any) in the future. But first it enumerates memory isolation failure reasons that can be sent across a notifier. This series does not go beyond arm64 to explore if these failure reason codes could be used in other existing registered memory notifiers. Please do let me know if there is any other potential use cases, will be happy to incorporate next time around. Also should we add similar failure reasons for online_pages() as well ? This series has been tested on arm64, boot tested on x86 and build tested on multiple other platforms. This series applies on v5.7-rc1. Cc: Andrew Morton <akpm@linux-foundation.org> Cc: Michal Hocko <mhocko@suse.com> Cc: Dan Williams <dan.j.williams@intel.com> Cc: David Hildenbrand <david@redhat.com> Cc: Yu Zhao <yuzhao@google.com> Cc: Hsin-Yi Wang <hsinyi@chromium.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will@kernel.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Steve Capper <steve.capper@arm.com> Cc: linux-arm-kernel@lists.infradead.org Cc: linux-mm@kvack.org Cc: linux-kernel@vger.kernel.org Anshuman Khandual (2): mm/hotplug: Enumerate memory range offlining failure reasons arm64/hotplug: Process MEM_OFFLINE and MEM_CANCEL_OFFLINE arch/arm64/mm/mmu.c | 52 ++++++++++++++++++++++++++++++++++++++---- drivers/base/memory.c | 9 ++++++++ include/linux/memory.h | 27 ++++++++++++++++++++++ mm/memory_hotplug.c | 24 ++++++++++++------- 4 files changed, 99 insertions(+), 13 deletions(-) -- 2.20.1 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2020-04-15 6:40 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-04-15 6:39 Anshuman Khandual [this message] 2020-04-15 6:39 ` [PATCH 0/2] arm64/hotplug: Process MEM_OFFLINE and MEM_CANCEL_OFFLINE events Anshuman Khandual 2020-04-15 6:39 ` [PATCH 1/2] mm/hotplug: Enumerate memory range offlining failure reasons Anshuman Khandual 2020-04-15 6:39 ` Anshuman Khandual 2020-04-15 6:39 ` [PATCH 2/2] arm64/hotplug: Process MEM_OFFLINE and MEM_CANCEL_OFFLINE Anshuman Khandual 2020-04-15 6:39 ` Anshuman Khandual 2020-04-15 7:35 ` [PATCH 0/2] arm64/hotplug: Process MEM_OFFLINE and MEM_CANCEL_OFFLINE events David Hildenbrand 2020-04-15 7:35 ` David Hildenbrand 2020-04-15 10:16 ` Michal Hocko 2020-04-15 10:16 ` Michal Hocko
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=1586932784-16315-1-git-send-email-anshuman.khandual@arm.com \ --to=anshuman.khandual@arm.com \ --cc=akpm@linux-foundation.org \ --cc=catalin.marinas@arm.com \ --cc=dan.j.williams@intel.com \ --cc=david@redhat.com \ --cc=hsinyi@chromium.org \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mark.rutland@arm.com \ --cc=mhocko@suse.com \ --cc=steve.capper@arm.com \ --cc=tglx@linutronix.de \ --cc=will@kernel.com \ --cc=yuzhao@google.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: linkBe 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.