All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Amit Shah <amit.shah@redhat.com>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
	Anthony Liguori <aliguori@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org,
	virtualization@lists.linux-foundation.org
Subject: Re: [RFC][PATCH] virtio balloon: kill tell-host-first logic
Date: Tue, 12 Apr 2011 09:22:32 -0700	[thread overview]
Message-ID: <1302625352.8321.2126.camel@nimitz> (raw)
In-Reply-To: <20110412054330.GH26678@amit-x200.redhat.com>

On Tue, 2011-04-12 at 11:13 +0530, Amit Shah wrote:
> Sure, the only contention was on the commit message, where you stated
> modern qemus set this... qemu doesn't, and it should.  Care to do a
> patch for that? 

If Rusty hasn't pushed the commit out anywhere, we can still amend the
commit.  Otherwise, we're in a _bit_ of a pickle since you can't patch
git logs. :)

Whatever is easiest for Rusty works for me.  

How about this for a replacement log?

--

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
feature, 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; we're under no obligation to do _anything_.
That's the state of affairs in current qemu:

	#define VIRTIO_BALLOON_F_MUST_TELL_HOST 0

This patch makes the "tell host first" logic the only case.  This
should make everybody happy, and reduce the amount of untested or
untestable code in the kernel.

This _also_ means that we don't have to preserve a pfn list
after the pages are freed, which should let us get rid of some
temporary storage (vb->pfns) eventually.

Signed-off-by: Dave Hansen <dave@linux.vnet.ibm.com>

-- Dave


  reply	other threads:[~2011-04-12 16:22 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 22:11   ` Dave Hansen
2011-04-12  5:43     ` Amit Shah
2011-04-12  5:43     ` Amit Shah
2011-04-12 16:22       ` Dave Hansen [this message]
2011-04-12 16:43         ` Amit Shah
2011-04-14 20:28           ` Dave Hansen
2011-04-15 10:39             ` Amit Shah
2011-04-15 10:39             ` Amit Shah
2011-04-14 20:28           ` Dave Hansen
2011-04-12 16:43         ` 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-14 20:30           ` Dave Hansen
2011-04-19  1:25             ` Rusty Russell
2011-04-19  1:25               ` Rusty Russell
2011-04-12 16:22       ` Dave Hansen
2011-04-11 22:11   ` Dave Hansen
2011-04-11 11:01 ` Michael S. Tsirkin
  -- 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=1302625352.8321.2126.camel@nimitz \
    --to=dave@linux.vnet.ibm.com \
    --cc=aliguori@linux.vnet.ibm.com \
    --cc=amit.shah@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.