From: mawupeng <mawupeng1@huawei.com>
To: <gregkh@linuxfoundation.org>
Cc: <mawupeng1@huawei.com>, <akpm@linux-foundation.org>,
<david@redhat.com>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
<richard.weiyang@linux.alibaba.com>, <mst@redhat.com>,
<jasowang@redhat.com>, <pankaj.gupta.linux@gmail.com>,
<mhocko@kernel.org>, <osalvador@suse.de>
Subject: Re: [PATCH stable 5.10 1/1] mm/memory_hotplug: extend offline_and_remove_memory() to handle more than one memory block
Date: Wed, 14 Jun 2023 14:45:58 +0800 [thread overview]
Message-ID: <cd9688dc-a716-3031-489e-a867df0d1ea2@huawei.com> (raw)
In-Reply-To: <2023061440-showing-happiest-937e@gregkh>
On 2023/6/14 14:35, Greg KH wrote:
> On Wed, Jun 14, 2023 at 02:19:00PM +0800, Wupeng Ma wrote:
>> From: David Hildenbrand <david@redhat.com>
>>
>> virtio-mem soon wants to use offline_and_remove_memory() memory that
>> exceeds a single Linux memory block (memory_block_size_bytes()). Let's
>> remove that restriction.
>>
>> Let's remember the old state and try to restore that if anything goes
>> wrong. While re-onlining can, in general, fail, it's highly unlikely to
>> happen (usually only when a notifier fails to allocate memory, and these
>> are rather rare).
>>
>> This will be used by virtio-mem to offline+remove memory ranges that are
>> bigger than a single memory block - for example, with a device block
>> size of 1 GiB (e.g., gigantic pages in the hypervisor) and a Linux memory
>> block size of 128MB.
>>
>> While we could compress the state into 2 bit, using 8 bit is much
>> easier.
>>
>> This handling is similar, but different to acpi_scan_try_to_offline():
>>
>> a) We don't try to offline twice. I am not sure if this CONFIG_MEMCG
>> optimization is still relevant - it should only apply to ZONE_NORMAL
>> (where we have no guarantees). If relevant, we can always add it.
>>
>> b) acpi_scan_try_to_offline() simply onlines all memory in case
>> something goes wrong. It doesn't restore previous online type. Let's do
>> that, so we won't overwrite what e.g., user space configured.
>>
>> Reviewed-by: Wei Yang <richard.weiyang@linux.alibaba.com>
>> Cc: "Michael S. Tsirkin" <mst@redhat.com>
>> Cc: Jason Wang <jasowang@redhat.com>
>> Cc: Pankaj Gupta <pankaj.gupta.linux@gmail.com>
>> Cc: Michal Hocko <mhocko@kernel.org>
>> Cc: Oscar Salvador <osalvador@suse.de>
>> Cc: Wei Yang <richard.weiyang@linux.alibaba.com>
>> Cc: Andrew Morton <akpm@linux-foundation.org>
>> Signed-off-by: David Hildenbrand <david@redhat.com>
>> Link: https://lore.kernel.org/r/20201112133815.13332-28-david@redhat.com
>> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
>> Acked-by: Andrew Morton <akpm@linux-foundation.org>
>> ---
>> mm/memory_hotplug.c | 105 +++++++++++++++++++++++++++++++++++++-------
>> 1 file changed, 89 insertions(+), 16 deletions(-)
>
> As you forwarded this patch on, you too need to sign-off on it.
Thanks for reminding me.
Signed-off-by: Ma Wupeng <mawupeng1@huawei.com>
>
> Also, what is the git id of the commit in Linus's tree?
Sorry, here is the commit in Linus's tree.
commit 8dc4bb58a146655eb057247d7c9d19e73928715b upstream.
>
> thanks,
>
> greg k-h
next prev parent reply other threads:[~2023-06-14 6:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-14 6:18 [PATCH stable 5.10 0/1] Fix memleak during hotremove memory Wupeng Ma
2023-06-14 6:19 ` [PATCH stable 5.10 1/1] mm/memory_hotplug: extend offline_and_remove_memory() to handle more than one memory block Wupeng Ma
2023-06-14 6:35 ` Greg KH
2023-06-14 6:45 ` mawupeng [this message]
2023-06-19 6:20 ` Greg KH
2023-06-19 6:54 ` mawupeng
2023-06-19 6:51 ` [PATCH stable 5.10] " Wupeng Ma
2023-06-19 7:16 ` Greg KH
2023-06-19 7:22 ` mawupeng
2023-06-19 7:41 ` David Hildenbrand
2023-06-19 7:53 ` mawupeng
2023-06-19 8:04 ` Greg KH
2023-06-19 7:48 ` Greg KH
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=cd9688dc-a716-3031-489e-a867df0d1ea2@huawei.com \
--to=mawupeng1@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=osalvador@suse.de \
--cc=pankaj.gupta.linux@gmail.com \
--cc=richard.weiyang@linux.alibaba.com \
--cc=stable@vger.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: 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