[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87lh4b3wg5.fsf@vitty.brq.redhat.com>
Date: Mon, 18 Apr 2016 14:58:34 +0200
From: Vitaly Kuznetsov <vkuznets@...hat.com>
To: "K. Y. Srinivasan" <kys@...rosoft.com>
Cc: linux-kernel@...r.kernel.org,
Haiyang Zhang <haiyangz@...rosoft.com>,
Alex Ng <alexng@...rosoft.com>,
Cathy Avery <cavery@...hat.com>, devel@...uxdriverproject.org
Subject: Re: [PATCH 0/2] Drivers: hv: balloon: two memory hotplug fixes
Vitaly Kuznetsov <vkuznets@...hat.com> writes:
> 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.
K. Y.,
it seems these two patches were lost. Should I resend them?
>
> 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(-)
--
Vitaly
Powered by blists - more mailing lists