From: Dave Hansen <dave@linux.vnet.ibm.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Rusty Russell <rusty@rustcorp.com.au>,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org,
Anthony Liguori <aliguori@linux.vnet.ibm.com>
Subject: Re: [RFC][PATCH] virtio balloon: kill tell-host-first logic
Date: Mon, 11 Apr 2011 15:11:11 -0700 [thread overview]
Message-ID: <1302559871.7286.16749.camel@nimitz> (raw)
In-Reply-To: <20110411110131.GA23123@redhat.com>
On Mon, 2011-04-11 at 14:01 +0300, Michael S. Tsirkin wrote:
> On Thu, Apr 07, 2011 at 10:43:25AM -0700, Dave Hansen wrote:
> > The virtio balloon driver has a VIRTIO_BALLOON_F_MUST_TELL_HOST
> > feature bit. Whenever the bit is set, we must always tell the
> > host before we free pages back to the allocator. Without this
> > we might free a page (and have another user touch it) while the
> > hypervisor is unprepared for it.
> >
> > But, if the bit is _not_ set, we are under no obligation to
> > reverse the order. Furthermore, all modern qemus set this bit.
>
> Which qemus do this, specifically? Amit Shah just pointed out to me
> that upstream qemu.git and qemu-kvm.git don't seem to do this.
I had a conversation with Anthony about it, and I think I managed to
confuse myself somewhere. Just to be clear, all that I see in the
qemu-kvm git tree right now (df85c051d780bca0ee2462cfeb8ef6d9552a19b0)
is this:
hw/virtio-balloon.h:#define VIRTIO_BALLOON_F_MUST_TELL_HOST 0 /* Tell before reclaiming pages */
> Which qemu did you test this with?
Probably a week or two old qemu-kvm.
My changelog could probably use some work, but the patch still stands.
The only requirement we have is that when
VIRTIO_BALLOON_F_MUST_TELL_HOST is set we *MUST* tell the host, first.
But, when it's not set, we can do whatever we want.
So, we might as well always have the ...F_MUST_TELL_HOST behavior all
the time.
-- Dave
next prev parent reply other threads:[~2011-04-11 22:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-07 17:43 [RFC][PATCH] virtio balloon: kill tell-host-first logic Dave Hansen
2011-04-09 22:48 ` Rusty Russell
2011-04-09 22:48 ` Rusty Russell
2011-04-11 11:01 ` Michael S. Tsirkin
2011-04-11 11:01 ` Michael S. Tsirkin
2011-04-11 22:11 ` Dave Hansen [this message]
2011-04-12 5:43 ` Amit Shah
2011-04-12 16:22 ` Dave Hansen
2011-04-12 16:22 ` Dave Hansen
2011-04-12 16:43 ` Amit Shah
2011-04-12 16:43 ` Amit Shah
2011-04-14 20:28 ` Dave Hansen
2011-04-14 20:28 ` Dave Hansen
2011-04-15 10:39 ` Amit Shah
2011-04-15 10:39 ` Amit Shah
2011-04-14 11:37 ` Rusty Russell
2011-04-14 11:37 ` Rusty Russell
2011-04-14 20:30 ` Dave Hansen
2011-04-19 1:25 ` Rusty Russell
2011-04-19 1:25 ` Rusty Russell
2011-04-14 20:30 ` Dave Hansen
2011-04-12 5:43 ` Amit Shah
2011-04-11 22:11 ` Dave Hansen
-- strict thread matches above, loose matches on Subject: below --
2011-04-07 17:43 Dave Hansen
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=1302559871.7286.16749.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=rusty@rustcorp.com.au \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.