public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: "Michael S. Tsirkin" <mst@redhat•com>,
	Rusty Russell <rusty@rustcorp•com.au>
Cc: linux-next@vger•kernel.org, linux-kernel@vger•kernel.org
Subject: linux-next: manual merge of the vhost tree with the virtio tree
Date: Fri, 6 Mar 2015 14:36:20 +1100	[thread overview]
Message-ID: <20150306143620.664bf043@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1666 bytes --]

Hi Michael,

Today's linux-next merge of the vhost tree got a conflict in
drivers/virtio/virtio_balloon.c between commit 7f8998200dcb
("virtio_balloon: annotate possible sleep waiting for event") from the
virtio tree and commit 2426d3b03d07 ("virtio-balloon: do not call
blocking ops when !TASK_RUNNING") from the vhost tree.

I fixed it up (I think - see below) and can carry the fix as necessary
(no action is required).

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au

diff --cc drivers/virtio/virtio_balloon.c
index 06001ca71ea3,5a6ad6dbdec4..000000000000
--- a/drivers/virtio/virtio_balloon.c
+++ b/drivers/virtio/virtio_balloon.c
@@@ -341,19 -343,17 +343,25 @@@ static int balloon(void *_vballoon
  
  		try_to_freeze();
  
 +		/*
 +		 * Reading the config on the ccw backend involves an
 +		 * allocation, so we may actually sleep and have an
 +		 * extra iteration.  It's extremely unlikely, and this
 +		 * isn't a fast path in any sense.
 +		 */
 +		sched_annotate_sleep();
 +
- 		wait_event_interruptible(vb->config_change,
- 					 (diff = towards_target(vb)) != 0
- 					 || vb->need_stats_update
- 					 || kthread_should_stop()
- 					 || freezing(current));
+ 		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);
+ 
  		if (vb->need_stats_update)
  			stats_handle_request(vb);
  		if (diff > 0)

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2015-03-06  3:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-06  3:36 Stephen Rothwell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-04-20  4:54 linux-next: manual merge of the vhost tree with the virtio tree Stephen Rothwell
2013-02-20  5:00 Stephen Rothwell

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=20150306143620.664bf043@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mst@redhat$(echo .)com \
    --cc=rusty@rustcorp$(echo .)com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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