From: Anshuman Khandual <anshuman.khandual@arm.com>
To: Robin Murphy <robin.murphy@arm.com>, linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org,
rafael@kernel.org, mhocko@kernel.org, akpm@linux-foundation.org,
osalvador@suse.de
Subject: Re: [PATCH v2] mm/memory-hotplug: Add sysfs hot-remove trigger
Date: Tue, 12 Feb 2019 08:50:52 +0530 [thread overview]
Message-ID: <4d92d783-736b-b94c-dbfd-1560c0936fb3@arm.com> (raw)
In-Reply-To: <49ef5e6c12f5ede189419d4dcced5dc04957c34d.1549906631.git.robin.murphy@arm.com>
On 02/11/2019 11:20 PM, 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.
>
> Since process dictates the new sysfs entry be documented, let's also
> document the existing probe entry to match - better 13-and-a-half years
> late than never, as they say...
>
> Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> ---
>
> v2: Use is_memblock_offlined() helper, write up documentation
>
> .../ABI/testing/sysfs-devices-memory | 25 +++++++++++
> drivers/base/memory.c | 42 ++++++++++++++++++-
> 2 files changed, 66 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/ABI/testing/sysfs-devices-memory b/Documentation/ABI/testing/sysfs-devices-memory
> index deef3b5723cf..02a4250964e0 100644
> --- a/Documentation/ABI/testing/sysfs-devices-memory
> +++ b/Documentation/ABI/testing/sysfs-devices-memory
> @@ -91,3 +91,28 @@ Description:
> memory section directory. For example, the following symbolic
> link is created for memory section 9 on node0.
> /sys/devices/system/node/node0/memory9 -> ../../memory/memory9
> +
> +What: /sys/devices/system/memory/probe
> +Date: October 2005
> +Contact: Linux Memory Management list <linux-mm@kvack.org>
> +Description:
> + The file /sys/devices/system/memory/probe is write-only, and
> + when written will simulate a physical hot-add of a memory
Small nit. It does not 'simulate' but really does add the memory block into
the memblock, buddy allocator and so on.
> + section at the given address. For example, assuming a section
> + of unused memory exists at physical address 0x80000000, it can
> + be introduced to the kernel with the following command:
> + # echo 0x80000000 > /sys/devices/system/memory/probe
> +Users: Memory hotplug testing and development
> +
> +What: /sys/devices/system/memory/memoryX/remove
> +Date: February 2019
> +Contact: Linux Memory Management list <linux-mm@kvack.org>
> +Description:
> + The file /sys/devices/system/memory/memoryX/remove is
> + write-only, and when written with a boolean 'true' value will
> + simulate a physical hot-remove of that memory section. For
Same here.
> + example, assuming a 1GB section size, the section added by the
> + above "probe" example could be removed again with the following
There is no need to mention specific memory block sizes like 1G in documentation
for this generic interface which would work for all possible sizes.
next prev parent reply other threads:[~2019-02-12 3:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-11 17:50 Robin Murphy
2019-02-12 3:20 ` Anshuman Khandual [this message]
2019-02-12 8:33 ` Michal Hocko
2019-02-12 14:54 ` Robin Murphy
2019-02-12 15:11 ` Michal Hocko
2019-02-25 21:14 ` David Hildenbrand
2019-02-26 15:12 ` Robin Murphy
2019-02-26 15:18 ` 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=4d92d783-736b-b94c-dbfd-1560c0936fb3@arm.com \
--to=anshuman.khandual@arm.com \
--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=osalvador@suse.de \
--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