public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Avi Kivity <avi@qumranet•com>
Cc: linux-next@vger•kernel.org, Marcelo Tosatti <mtosatti@redhat•com>,
	Arjan van de Ven <arjan@linux•intel.com>
Subject: linux-next: manual merge of the kvm tree
Date: Sat, 13 Sep 2008 05:50:17 +1000	[thread overview]
Message-ID: <20080913055017.f54fbf66.sfr@canb.auug.org.au> (raw)

Hi Avi,

Today's linux-next merge of the kvm tree got a conflict in
arch/x86/kvm/i8254.c between commit
beb20d52d03a51218827fb4a36a4b583debb03f9 ("hrtimer: convert kvm to the
new hrtimer apis") from the timers tree and commit
3dceed526eaab43af90bcec3476c4f534f98dd41 ("KVM: PIT: fix injection logic
and count") from the kvm tree.

Just contextual. I fixed it up (see below) and can carry the fix.
-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

diff --cc arch/x86/kvm/i8254.c
index 1bf8f57,634132a..0000000
--- a/arch/x86/kvm/i8254.c
+++ b/arch/x86/kvm/i8254.c
@@@ -200,13 -200,14 +200,14 @@@ static int __pit_timer_fn(struct kvm_kp
  
  	if (!atomic_inc_and_test(&pt->pending))
  		set_bit(KVM_REQ_PENDING_TIMER, &vcpu0->requests);
- 	if (vcpu0 && waitqueue_active(&vcpu0->wq)) {
- 		vcpu0->arch.mp_state = KVM_MP_STATE_RUNNABLE;
+ 
+ 	if (vcpu0 && waitqueue_active(&vcpu0->wq))
  		wake_up_interruptible(&vcpu0->wq);
- 	}
  
 -	pt->timer.expires = ktime_add_ns(pt->timer.expires, pt->period);
 -	pt->scheduled = ktime_to_ns(pt->timer.expires);
 +	hrtimer_add_expires_ns(&pt->timer, pt->period);
 +	pt->scheduled = ktime_to_ns(hrtimer_get_expires(&pt->timer));
+ 	if (pt->period)
+ 		ps->channels[0].count_load_time = pt->timer.expires;
  
  	return (pt->period == 0 ? 0 : 1);
  }

             reply	other threads:[~2008-09-12 19:50 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-12 19:50 Stephen Rothwell [this message]
2008-09-12 19:53 ` linux-next: manual merge of the kvm tree Arjan van de Ven
2008-09-12 19:59 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2009-06-12  2:57 Stephen Rothwell
2009-06-12  7:19 ` Avi Kivity
2009-01-02  0:44 Stephen Rothwell
2008-12-29  5:11 Stephen Rothwell
2008-12-22  3:52 Stephen Rothwell
2008-12-22  5:13 ` Benjamin Herrenschmidt
2008-12-22 21:39   ` Hollis Blanchard
2008-12-22 21:41     ` Benjamin Herrenschmidt
2008-12-22 22:03       ` Hollis Blanchard
2008-12-22 22:11         ` Benjamin Herrenschmidt
2008-12-22 22:29         ` Paul Mackerras
2008-12-22 22:44           ` Hollis Blanchard
2008-12-23  0:07             ` Paul Mackerras
2008-12-23  1:02               ` Hollis Blanchard
2008-12-23  1:38                 ` Benjamin Herrenschmidt
2008-11-25  6:49 Stephen Rothwell
2008-10-29  2:58 Stephen Rothwell
2008-10-29  9:55 ` Avi Kivity
2008-10-29 10:35   ` Stephen Rothwell
2008-10-15  5:27 Stephen Rothwell
2008-09-17  5:50 Stephen Rothwell
2008-09-17  5:24 Stephen Rothwell
2008-09-15  0:14 Stephen Rothwell
2008-09-15  6:53 ` Ingo Molnar
2008-08-26  4:45 Stephen Rothwell
2008-08-26  7:39 ` Avi Kivity
2008-08-26  7:41   ` Stephen Rothwell
2008-08-15  4:46 Stephen Rothwell
2008-08-04  3:13 Stephen Rothwell
2008-07-22  3:43 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=20080913055017.f54fbf66.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=arjan@linux$(echo .)intel.com \
    --cc=avi@qumranet$(echo .)com \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mtosatti@redhat$(echo .)com \
    /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