public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Denis V. Lunev" <den@openvz.org>
Cc: virtualization@lists.linux-foundation.org,
	linux-kernel@vger.kernel.org,
	Konstantin Neumoin <kneumoin@virtuozzo.com>
Subject: Re: [PATCH 1/1] update balloon size in balloon "probe"
Date: Fri, 23 Sep 2016 21:58:37 +0300	[thread overview]
Message-ID: <20160923215334-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1474638477-8658-1-git-send-email-den@openvz.org>

On Fri, Sep 23, 2016 at 04:47:57PM +0300, Denis V. Lunev wrote:
> From: Konstantin Neumoin <kneumoin@virtuozzo.com>
> 
> Patch
>     Commit 3d2a3774c1b046f548ebea0391a602fd5685a307
>     Author: Michael S. Tsirkin <mst@redhat.com>
>     Date:   Tue Mar 10 11:55:08 2015 +1030
>     virtio-balloon: do not call blocking ops when !TASK_RUNNING
> has added a regression. Original code with wait_event_interruptible
> checked the condition before start waiting and started balloon operations
> if necessary.

I don't get it, sorry.

+               add_wait_queue(&vb->config_change, &wait);
+               for (;;) {
+                       if ((diff = towards_target(vb)) != 0 ||
+                           vb->need_stats_update ||
+                           kthread_should_stop() ||
+                           freezing(current))
+                               break;
+                       wait_woken(&wait, TASK_INTERRUPTIBLE, MAX_SCHEDULE_TIMEOUT);
+               }
+               remove_wait_queue(&vb->config_change, &wait);

Seems to check the condition before waiting.

The issue is more likely with this patch:

	commit fad7b7b27b6a168ca8ebc84482043886f837b89d
	Author: Petr Mladek <pmladek@suse.com>
	Date:   Mon Jan 25 17:38:05 2016 +0100

	    virtio_balloon: Use a workqueue instead of "vballoon" kthread
    


> Right now balloon is not inflated if ballon target is set before the
> driver is loaded.
> 
> Signed-off-by: Konstantin Neumoin <kneumoin@virtuozzo.com>
> Signed-off-by: Denis V. Lunev <den@openvz.org>
> CC: "Michael S. Tsirkin" <mst@redhat.com>
> ---
>  drivers/virtio/virtio_balloon.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
> index 4e7003d..0a6c10f 100644
> --- a/drivers/virtio/virtio_balloon.c
> +++ b/drivers/virtio/virtio_balloon.c
> @@ -577,6 +577,10 @@ static int virtballoon_probe(struct virtio_device *vdev)
>  
>  	virtio_device_ready(vdev);
>  
> +	if (towards_target(vb))
> +		virtballoon_changed(vdev);
> +	update_balloon_size(vb);
> +
>  	return 0;
>  
>  out_del_vqs:


I know we have same thing on restore, but it seems bogus
there as well:
        if (towards_target(vb))
                virtballoon_changed(vdev);
        update_balloon_size(vb);

makes no sense because virtballoon_changed merely queues
the work.


> -- 
> 2.7.4

  reply	other threads:[~2016-09-23 18:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 13:47 [PATCH 1/1] update balloon size in balloon "probe" Denis V. Lunev
2016-09-23 18:58 ` Michael S. Tsirkin [this message]
2016-09-26  7:16   ` Konstantin Neumoin
2016-09-28 14:03     ` Konstantin Neumoin

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=20160923215334-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=den@openvz.org \
    --cc=kneumoin@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --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