RE: [PATCH 0/2] Drivers: hv: balloon: two memory hotplug fixes

...@microsoft.com>; Cathy > Avery <cav...@redhat.com>; de...@linuxdriverproject.org > Subject: Re: [PATCH 0/2] Drivers: hv: balloon: two memory hotplug fixes > > Vitaly Kuznetsov <vkuzn...@redhat.com> writes: > > > Hi, > > > > I found an issu

RE: [PATCH 0/2] Drivers: hv: balloon: two memory hotplug fixes

> -Original Message- > From: Vitaly Kuznetsov [mailto:vkuzn...@redhat.com] > Sent: Monday, April 18, 2016 5:59 AM > To: KY Srinivasan > Cc: linux-kernel@vger.kernel.org; Haiyang Zhang > ; Alex Ng (LIS) ; Cathy > Avery ; de...@linuxdriverproject.org > Subject: Re:

Re: [PATCH 0/2] Drivers: hv: balloon: two memory hotplug fixes

Vitaly Kuznetsov 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

Re: [PATCH 0/2] Drivers: hv: balloon: two memory hotplug fixes

Vitaly Kuznetsov 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 >

[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 >

[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 >

[PATCH 0/2] Drivers: hv: balloon: Online memory segments "in context"

The current code depends on user level code to bring online memory segments that have been hot added. Change this code to online memory in the same context that is hot adding the memory. This patch set implements the necessary infrastructure for making it possible to online memory segments from

[PATCH 0/2] Drivers: hv: balloon: Online memory segments in context

The current code depends on user level code to bring online memory segments that have been hot added. Change this code to online memory in the same context that is hot adding the memory. This patch set implements the necessary infrastructure for making it possible to online memory segments from

[PATCH 0/2] Drivers: hv: balloon: Fix some issues in the balloon driver

This patch set adresses a couple of issues discovered in the balloon driver: 1. Prevent stale pressure report being posted. 2. If memory is not brought online within the allowed time, do not roll back hot add state if hot add succeeded. K. Y. Srinivasan (2): Drivers: hv: balloon: Fix a bug

[PATCH 0/2] Drivers: hv: balloon: Fix some issues in the balloon driver

This patch set adresses a couple of issues discovered in the balloon driver: 1. Prevent stale pressure report being posted. 2. If memory is not brought online within the allowed time, do not roll back hot add state if hot add succeeded. K. Y. Srinivasan (2): Drivers: hv: balloon: Fix a bug

[PATCH 0/2] Drivers: hv: balloon

Support 2M page allocations when memory is ballooned out of the guest. Hyper-V Dynamic Memory protocol is optimized around the ability to move memory in 2M chunks. K. Y. Srinivasan (2): mm: Export split_page() Drivers: hv: balloon: Support 2M page allocations for ballooning

[PATCH 0/2] Drivers: hv: balloon

Support 2M page allocations when memory is ballooned out of the guest. Hyper-V Dynamic Memory protocol is optimized around the ability to move memory in 2M chunks. K. Y. Srinivasan (2): mm: Export split_page() Drivers: hv: balloon: Support 2M page allocations for ballooning

[PATCH 0/2] Drivers: hv: balloon

Make furher adjustments to memory pressure reporting and computation. In the current code, we begin to report pressure soon after the balloon driver loads and typically report a very low pressure until the system is fully operational. To avoid having the host take memory balancing decisions on

[PATCH 0/2] Drivers: hv: balloon

Make furher adjustments to memory pressure reporting and computation. In the current code, we begin to report pressure soon after the balloon driver loads and typically report a very low pressure until the system is fully operational. To avoid having the host take memory balancing decisions on