From: Oscar Salvador <osalvador@suse.de>
To: Robin Murphy <robin.murphy@arm.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
gregkh@linuxfoundation.org, rafael@kernel.org, mhocko@kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH] mm/memory-hotplug: Add sysfs hot-remove trigger
Date: Thu, 7 Feb 2019 14:36:24 +0100 [thread overview]
Message-ID: <20190207133620.a4vg2xqphsloke6i@d104.suse.de> (raw)
In-Reply-To: <29ed519902512319bcc62e071d52b712fa97e306.1549469965.git.robin.murphy@arm.com>
On Wed, Feb 06, 2019 at 05:03:53PM +0000, Robin Murphy wrote:
> ARCH_MEMORY_PROBE is a useful thing for testing and debugging hotplug,
> but being able to exercise the (arguably trickier) hot-remove path would
> be even more useful. Extend the feature to allow removal of offline
> sections to be triggered manually to aid development.
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>
> This is inspired by a previous proposal[1], but in coming up with a
> more robust interface I ended up rewriting the whole thing from
> scratch. The lack of documentation is semi-deliberate, since I don't
> like the idea of anyone actually relying on this interface as ABI, but
> as a handy tool it felt useful enough to be worth sharing :)
Hi Robin,
I think this might come in handy, especially when trying to test hot-remove
on arch's that do not have any means to hot-remove memory, or even on virtual
platforms that do not have yet support for hot-remove depending on the platform,
like qemu/arm64.
I could have used this while testing hot-remove on other archs for [1]
>
> Robin.
>
> [1] https://lore.kernel.org/lkml/22d34fe30df0fbacbfceeb47e20cb1184af73585.1511433386.git.ar@linux.vnet.ibm.com/
>
> + if (mem->state != MEM_OFFLINE)
> + return -EBUSY;
We do have the helper "is_memblock_offlined()", although it is only used in one place now.
So, I would rather use it here as well.
> +
> + ret = lock_device_hotplug_sysfs();
> + if (ret)
> + return ret;
> +
> + if (device_remove_file_self(dev, attr)) {
> + __remove_memory(pfn_to_nid(start_pfn), PFN_PHYS(start_pfn),
> + MIN_MEMORY_BLOCK_SIZE * sections_per_block);
Sorry, I am not into sysfs inners, but I thought that:
device_del::device_remove_attrs::device_remove_groups::sysfs_remove_groups
would be enough to remove the dev attributes.
I guess in this case that is not enough, could you explain why?
[1] https://patchwork.kernel.org/patch/10775339/
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2019-02-07 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-06 17:03 Robin Murphy
2019-02-06 18:45 ` Greg KH
2019-02-06 20:07 ` Robin Murphy
2019-02-07 13:36 ` Oscar Salvador [this message]
2019-02-07 15:32 ` Robin Murphy
2019-02-08 3:03 ` 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=20190207133620.a4vg2xqphsloke6i@d104.suse.de \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox