From: Rusty Russell <rusty@rustcorp.com.au>
To: Amit Shah <amit.shah@redhat.com>, "Michael S. Tsirkin" <mst@redhat.com>
Cc: Virtualization List <virtualization@lists.linux-foundation.org>
Subject: Re: [PATCH 0/3] virtio: balloon: cleanups and a fix
Date: Mon, 07 May 2012 13:23:21 +0930 [thread overview]
Message-ID: <87fwbcfxzi.fsf@rustcorp.com.au> (raw)
In-Reply-To: <20120426201554.GA5804@amit.redhat.com>
On Fri, 27 Apr 2012 01:45:54 +0530, Amit Shah <amit.shah@redhat.com> wrote:
> On (Thu) 26 Apr 2012 [23:07:47], Michael S. Tsirkin wrote:
> > 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?
>
> Well if you just pick patch 2, it'll work fine. There's no context
> change there.
1 and 3 applied.
Thanks!
Rusty.
prev parent reply other threads:[~2012-05-07 3:53 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 ` [PATCH 0/3] virtio: balloon: cleanups and a fix Michael S. Tsirkin
2012-04-26 20:15 ` Amit Shah
2012-05-07 3:53 ` Rusty Russell [this message]
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=87fwbcfxzi.fsf@rustcorp.com.au \
--to=rusty@rustcorp.com.au \
--cc=amit.shah@redhat.com \
--cc=mst@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).