From: Anshuman Khandual <anshuman.khandual@arm.com> To: linux-arm-kernel@lists.infradead.org Cc: catalin.marinas@arm.com, will@kernel.org, Anshuman Khandual <anshuman.khandual@arm.com>, Will Deacon <will@kernel.com>, Mark Rutland <mark.rutland@arm.com>, Marc Zyngier <maz@kernel.org>, Steve Capper <steve.capper@arm.com>, Mark Brown <broonie@kernel.org>, linux-kernel@vger.kernel.org Subject: [PATCH V3 0/3] arm64/mm/hotplug: Improve memory offline event notifier Date: Mon, 21 Sep 2020 17:35:05 +0530 [thread overview] Message-ID: <1600689908-28213-1-git-send-email-anshuman.khandual@arm.com> (raw) This series brings three different changes to the only memory event notifier on arm64 platform. These changes improve it's robustness while also enhancing debug capabilities during potential memory offlining error conditions. This applies on 5.9-rc6 Changes in V3: - Split the single patch into three patch series per Catalin - Trigger changed from setup_arch() to early_initcall() per Catalin - Renamed back memory_hotremove_notifier() as prevent_bootmem_remove_init() - validate_bootmem_online() is now called from prevent_bootmem_remove_init() per Catalin - Skip registering the notifier if validate_bootmem_online() returns negative Changes in V2: (https://patchwork.kernel.org/patch/11732161/) - Dropped all generic changes wrt MEM_CANCEL_OFFLINE reasons enumeration - Dropped all related (processing MEM_CANCEL_OFFLINE reasons) changes on arm64 - Added validate_boot_mem_online_state() that gets called with early_initcall() - Added CONFIG_MEMORY_HOTREMOVE check before registering memory notifier - Moved notifier registration i.e memory_hotremove_notifier into setup_arch() Changes in V1: (https://patchwork.kernel.org/project/linux-mm/list/?series=271237) Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will@kernel.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Marc Zyngier <maz@kernel.org> Cc: Steve Capper <steve.capper@arm.com> Cc: Mark Brown <broonie@kernel.org> Cc: linux-arm-kernel@lists.infradead.org Cc: linux-kernel@vger.kernel.org Anshuman Khandual (3): arm64/mm/hotplug: Register boot memory hot remove notifier earlier arm64/mm/hotplug: Enable MEM_OFFLINE event handling arm64/mm/hotplug: Ensure early memory sections are all online arch/arm64/mm/mmu.c | 110 +++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 103 insertions(+), 7 deletions(-) -- 2.20.1
WARNING: multiple messages have this Message-ID (diff)
From: Anshuman Khandual <anshuman.khandual@arm.com> To: linux-arm-kernel@lists.infradead.org Cc: Mark Rutland <mark.rutland@arm.com>, Will Deacon <will@kernel.com>, Anshuman Khandual <anshuman.khandual@arm.com>, catalin.marinas@arm.com, Steve Capper <steve.capper@arm.com>, linux-kernel@vger.kernel.org, Mark Brown <broonie@kernel.org>, Marc Zyngier <maz@kernel.org>, will@kernel.org Subject: [PATCH V3 0/3] arm64/mm/hotplug: Improve memory offline event notifier Date: Mon, 21 Sep 2020 17:35:05 +0530 [thread overview] Message-ID: <1600689908-28213-1-git-send-email-anshuman.khandual@arm.com> (raw) This series brings three different changes to the only memory event notifier on arm64 platform. These changes improve it's robustness while also enhancing debug capabilities during potential memory offlining error conditions. This applies on 5.9-rc6 Changes in V3: - Split the single patch into three patch series per Catalin - Trigger changed from setup_arch() to early_initcall() per Catalin - Renamed back memory_hotremove_notifier() as prevent_bootmem_remove_init() - validate_bootmem_online() is now called from prevent_bootmem_remove_init() per Catalin - Skip registering the notifier if validate_bootmem_online() returns negative Changes in V2: (https://patchwork.kernel.org/patch/11732161/) - Dropped all generic changes wrt MEM_CANCEL_OFFLINE reasons enumeration - Dropped all related (processing MEM_CANCEL_OFFLINE reasons) changes on arm64 - Added validate_boot_mem_online_state() that gets called with early_initcall() - Added CONFIG_MEMORY_HOTREMOVE check before registering memory notifier - Moved notifier registration i.e memory_hotremove_notifier into setup_arch() Changes in V1: (https://patchwork.kernel.org/project/linux-mm/list/?series=271237) Cc: Catalin Marinas <catalin.marinas@arm.com> Cc: Will Deacon <will@kernel.com> Cc: Mark Rutland <mark.rutland@arm.com> Cc: Marc Zyngier <maz@kernel.org> Cc: Steve Capper <steve.capper@arm.com> Cc: Mark Brown <broonie@kernel.org> Cc: linux-arm-kernel@lists.infradead.org Cc: linux-kernel@vger.kernel.org Anshuman Khandual (3): arm64/mm/hotplug: Register boot memory hot remove notifier earlier arm64/mm/hotplug: Enable MEM_OFFLINE event handling arm64/mm/hotplug: Ensure early memory sections are all online arch/arm64/mm/mmu.c | 110 +++++++++++++++++++++++++++++++++++++++++--- 1 file changed, 103 insertions(+), 7 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-09-21 12:06 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-21 12:05 Anshuman Khandual [this message] 2020-09-21 12:05 ` [PATCH V3 0/3] arm64/mm/hotplug: Improve memory offline event notifier Anshuman Khandual 2020-09-21 12:05 ` [PATCH V3 1/3] arm64/mm/hotplug: Register boot memory hot remove notifier earlier Anshuman Khandual 2020-09-21 12:05 ` Anshuman Khandual 2020-09-23 6:04 ` Gavin Shan 2020-09-23 6:04 ` Gavin Shan 2020-09-24 3:23 ` Anshuman Khandual 2020-09-24 3:23 ` Anshuman Khandual 2020-09-21 12:05 ` [PATCH V3 2/3] arm64/mm/hotplug: Enable MEM_OFFLINE event handling Anshuman Khandual 2020-09-21 12:05 ` Anshuman Khandual 2020-09-23 4:44 ` Anshuman Khandual 2020-09-23 4:44 ` Anshuman Khandual 2020-09-23 6:31 ` Gavin Shan 2020-09-23 6:31 ` Gavin Shan 2020-09-24 3:51 ` Anshuman Khandual 2020-09-24 3:51 ` Anshuman Khandual 2020-09-21 12:05 ` [PATCH V3 3/3] arm64/mm/hotplug: Ensure early memory sections are all online Anshuman Khandual 2020-09-21 12:05 ` Anshuman Khandual
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=1600689908-28213-1-git-send-email-anshuman.khandual@arm.com \ --to=anshuman.khandual@arm.com \ --cc=broonie@kernel.org \ --cc=catalin.marinas@arm.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-kernel@vger.kernel.org \ --cc=mark.rutland@arm.com \ --cc=maz@kernel.org \ --cc=steve.capper@arm.com \ --cc=will@kernel.com \ --cc=will@kernel.org \ /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.