[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1459876874-882-1-git-send-email-vkuznets@redhat.com>
Date: Tue, 5 Apr 2016 19:21:12 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: devel@...uxdriverproject.org
Cc: linux-kernel@...r.kernel.org,
"K. Y. Srinivasan" <kys@...rosoft.com>,
Haiyang Zhang <haiyangz@...rosoft.com>,
Alex Ng <alexng@...rosoft.com>, Cathy Avery <cavery@...hat.com>
Subject: [PATCH 0/2] Drivers: hv: balloon: two memory hotplug fixes
Hi,
I found an issue (crash) while testing memory hotplug on WS2016TP4 host.
It should be easily reproducible with the following test sequence
(4.6-rc2):
1) Start a VM with 4 vCPUs in 4 NUMA nodes, 4096Mb of RAM.
2) Enable memory auto onlining with
'echo online > /sys/devices/system/memory/auto_online_blocks'
3) Wait till hv_balloon driver finishes negotiation.
4) Increase memory to 8192Mb.
5) Increase memory to 10000Mb.
The first patch in the series fixes the issue. While writing it I stumbled
upon an unrelated issue which I fix with PATCH 2.
Please review.
Vitaly Kuznetsov (2):
Drivers: hv: balloon: don't crash when memory is added in non-sorted
order
Drivers: hv: balloon: reset host_specified_ha_region
drivers/hv/hv_balloon.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
--
2.5.5
Powered by blists - more mailing lists