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

2016-04-18 Thread KY Srinivasan


> -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: [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
> >'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 1Mb.
> >
> > 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?

No I have them. I will be sending these soon.

K. Y
> 
> >
> > 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


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

2016-04-18 Thread Vitaly Kuznetsov
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 
>'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 1Mb.
>
> 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


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

2016-04-05 Thread Vitaly Kuznetsov
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 1Mb.

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



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

2013-07-24 Thread K. Y. Srinivasan
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 within a driver.

K. Y. Srinivasan (2):
  Drivers: base: memory: Export functionality for "in kernel" onlining
of memory
  Drivers: hv: balloon: Online the hot-added memory "in context"

 drivers/base/memory.c   |   35 +++
 drivers/hv/hv_balloon.c |   20 +++-
 include/linux/memory.h  |5 +
 3 files changed, 43 insertions(+), 17 deletions(-)

-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


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

2013-07-12 Thread K. Y. Srinivasan
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 in the hot-add code
  Drivers: hv: balloon: Do not post pressure status if interrupted

 drivers/hv/hv_balloon.c |   18 ++
 1 files changed, 10 insertions(+), 8 deletions(-)

-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[PATCH 0/2] Drivers: hv: balloon

2013-03-16 Thread K. Y. Srinivasan
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

 drivers/hv/hv_balloon.c |   18 --
 mm/page_alloc.c |1 +
 2 files changed, 17 insertions(+), 2 deletions(-)

-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/


[PATCH 0/2] Drivers: hv: balloon

2013-02-08 Thread K. Y. Srinivasan
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
data that does not fully reflect the memory pressure, delay reporting the
pressure. Additionally, implement a floor for ballooning based on the amount
of memory being managed.

K. Y. Srinivasan (2):
  Drivers: hv: balloon: Add a parameter to delay pressure reporting
  Drivers: hv: balloon: Prevent the host from ballooning the guest too
low

 drivers/hv/hv_balloon.c |   48 --
 1 files changed, 45 insertions(+), 3 deletions(-)

-- 
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/