RE: [PATCH 3/3] Drivers: hv: hv_balloon: Don't post pressure status from interrupt context

From: KY Srinivasan
Date: Mon Dec 08 2014 - 01:09:21 EST

> -----Original Message-----
> From: Sitsofe Wheeler [mailto:sitsofe@xxxxxxxxx]
> Sent: Sunday, December 7, 2014 12:05 AM
> To: KY Srinivasan
> Cc: gregkh@xxxxxxxxxxxxxxxxxxx; linux-kernel@xxxxxxxxxxxxxxx;
> devel@xxxxxxxxxxxxxxxxxxxxxx; olaf@xxxxxxxxx; apw@xxxxxxxxxxxxx;
> jasowang@xxxxxxxxxx
> Subject: Re: [PATCH 3/3] Drivers: hv: hv_balloon: Don't post pressure status
> from interrupt context
> On Tue, Dec 02, 2014 at 02:29:15PM -0800, K. Y. Srinivasan wrote:
> > We currently release memory (balloon down) in the interrupt context
> > and we also post memory status while releasing memory. Rather than
> > posting the status in the interrupt context, wakeup the status posting
> thread to post the status.
> > This will address the inconsistent lock state that Sitsofe Wheeler
> > <sitsofe@xxxxxxxxx>
> > reported:
> Sorry I didn't follow up on this. Things looked better after the patch but I was
> seeing a strange issue where the memory was being reduced to some
> minimum and the balloon would never shrink so the available memory was
> seemingly locked from then on. I ran out of time to investigate this later
> behaviour and didn't have the time to check if it had always been the case
> but I think I see other patches saying you nailed it and other issues. Do you
> have a published git tree with all these pieces in or have they already been
> mainlined?

Greg has not committed these patches yet. One of the patches changes the balloon floor.
This means that the guest will not be ballooned down below the floor. Is this what you are
seeing? In our testing we did not see anything unusual other than the floor being elevated
(as per the design).

K. Y
> --
> Sitsofe |
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at