From: lantianyu1986@gmail.com
To: kys@microsoft.com, haiyangz@microsoft.com,
sthemmin@microsoft.com, sashal@kernel.org,
akpm@linux-foundation.org, dan.j.williams@intel.com,
jgg@ziepe.ca, dave.hansen@linux.intel.com,
richardw.yang@linux.intel.com, namit@vmware.com,
Tianyu.Lan@microsoft.com, david@redhat.com,
christophe.leroy@c-s.fr, michael.h.kelley@microsoft.com
Cc: linux-hyperv@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, vkuznets@redhat.com,
eric.devolder@oracle.com
Subject: [RFC PATCH V2 00/10] x86/Hyper-V: Add Dynamic memory hot-remove function
Date: Tue, 7 Jan 2020 21:09:40 +0800 [thread overview]
Message-ID: <20200107130950.2983-1-Tianyu.Lan@microsoft.com> (raw)
From: Tianyu Lan <Tianyu.Lan@microsoft.com>
Hyper-V provides dynamic memory hot add/remove function.
Memory hot-add has already enabled in Hyper-V balloon driver.
Now add memory hot-remove function.
This patchset is based on the David Hildenbrand's "virtio-mem:
paravirtualized memory" RFC V4 version and use new interface
offline_and_remove_memory().
https://lkml.org/lkml/2019/12/12/681
Change since V1:
- Split patch into small patch for review.
- Convert ha_lock from spin lock to mutex.
- Add a common work to handle all mem hot plug and
balloon msg
- Use offline_and_remove_memory() to offline and remove
memory.
Tianyu Lan (10):
mm/resource: Move child to new resource when release mem region.
mm: expose is_mem_section_removable() symbol
x86/Hyper-V/Balloon: Replace hot-add and balloon up works with a
common work
x86/Hyper-V/Balloon: Convert spin lock ha_lock to mutex
x86/Hyper-V/Balloon: Avoid releasing ha_lock when traverse
ha_region_list
x86/Hyper-V/Balloon: Enable mem hot-remove capability
x86/Hyper-V/Balloon: Handle mem hot-remove request
x86/Hyper-V/Balloon: Handle request with non-aligned page number
x86/Hyper-V/Balloon: Hot add mem in the gaps of hot add region
x86/Hyper-V: Workaround Hyper-V unballoon msg bug
drivers/hv/hv_balloon.c | 754 ++++++++++++++++++++++++++++++++++++++++--------
kernel/resource.c | 38 ++-
mm/memory_hotplug.c | 1 +
3 files changed, 673 insertions(+), 120 deletions(-)
--
2.14.5
next reply other threads:[~2020-01-07 13:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 13:09 lantianyu1986 [this message]
2020-01-07 13:09 ` [RFC PATCH V2 1/10] mm/resource: Move child to new resource when release mem region lantianyu1986
2020-01-20 18:34 ` Michael Kelley
2020-01-20 19:20 ` Michael Kelley
2020-01-07 13:09 ` [RFC PATCH V2 2/10] mm: expose is_mem_section_removable() symbol lantianyu1986
2020-01-07 13:36 ` Michal Hocko
2020-01-10 13:41 ` David Hildenbrand
2020-01-13 14:49 ` [EXTERNAL] " Tianyu Lan
2020-01-13 15:01 ` David Hildenbrand
2020-01-14 9:50 ` Michal Hocko
2020-01-17 16:35 ` Tianyu Lan
2020-01-20 14:14 ` Michal Hocko
2020-01-07 13:09 ` [RFC PATCH V2 3/10] x86/Hyper-V/Balloon: Replace hot-add and balloon up works with a common work lantianyu1986
2020-01-20 19:12 ` Michael Kelley
2020-01-07 13:09 ` [RFC PATCH V2 4/10] x86/Hyper-V/Balloon: Convert spin lock ha_lock to mutex lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 5/10] x86/Hyper-V/Balloon: Avoid releasing ha_lock when traverse ha_region_list lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 6/10] x86/Hyper-V/Balloon: Enable mem hot-remove capability lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 7/10] x86/Hyper-V/Balloon: Handle mem hot-remove request lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 8/10] x86/Hyper-V/Balloon: Handle request with non-aligned page number lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 9/10] x86/Hyper-V/Balloon: Hot add mem in the gaps of hot add region lantianyu1986
2020-01-07 13:09 ` [RFC PATCH V2 10/10] x86/Hyper-V: Workaround Hyper-V unballoon msg bug lantianyu1986
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=20200107130950.2983-1-Tianyu.Lan@microsoft.com \
--to=lantianyu1986@gmail.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=akpm@linux-foundation.org \
--cc=christophe.leroy@c-s.fr \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=david@redhat.com \
--cc=eric.devolder@oracle.com \
--cc=haiyangz@microsoft.com \
--cc=jgg@ziepe.ca \
--cc=kys@microsoft.com \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michael.h.kelley@microsoft.com \
--cc=namit@vmware.com \
--cc=richardw.yang@linux.intel.com \
--cc=sashal@kernel.org \
--cc=sthemmin@microsoft.com \
--cc=vkuznets@redhat.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;
as well as URLs for NNTP newsgroup(s).