From: "Michael S. Tsirkin" <mst@redhat.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: Virtualization List <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 0/3] virtio: balloon: cleanups and a fix
Date: Thu, 26 Apr 2012 23:07:47 +0300 [thread overview]
Message-ID: <20120426200746.GA29932@redhat.com> (raw)
In-Reply-To: <cover.1335467427.git.amit.shah@redhat.com>
On Fri, Apr 27, 2012 at 12:45:54AM +0530, Amit Shah wrote:
> Hello,
>
> The main fix is to update the host with the current balloon value on
> module removal after deflating the balloon. Without the fix, the host
> has the wrong idea of the ballooned memory in the guest. This is
> patch 2.
>
> Patches 1 and 3 are cleanups with no effective code change.
better to just do fixes for 3.4. can you reorder pls?
> Please apply,
>
> Amit Shah (3):
> virtio: balloon: drop restore_common()
> virtio: balloon: let host know of updated balloon size before module
> removal
> virtio: balloon: separate out common code between remove and freeze
> functions
>
> drivers/virtio/virtio_balloon.c | 34 ++++++++++++++--------------------
> 1 files changed, 14 insertions(+), 20 deletions(-)
>
> --
> 1.7.7.6
next prev parent reply other threads:[~2012-04-26 20:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 19:15 [PATCH 0/3] virtio: balloon: cleanups and a fix Amit Shah
2012-04-26 19:15 ` [PATCH 1/3] virtio: balloon: drop restore_common() Amit Shah
2012-04-26 19:15 ` [PATCH 2/3] virtio: balloon: let host know of updated balloon size before module removal Amit Shah
2012-04-26 20:50 ` Michael S. Tsirkin
2012-04-26 19:15 ` [PATCH 3/3] virtio: balloon: separate out common code between remove and freeze functions Amit Shah
2012-04-26 20:07 ` Michael S. Tsirkin [this message]
2012-04-26 20:15 ` [PATCH 0/3] virtio: balloon: cleanups and a fix Amit Shah
2012-05-07 3:53 ` Rusty Russell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120426200746.GA29932@redhat.com \
--to=mst@redhat.com \
--cc=amit.shah@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).