public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Soren Hansen <soren@ubuntu.com>
To: Avi Kivity <avi@qumranet.com>
Cc: Anthony Liguori <anthony@codemonkey.ws>,
	Bernd Schubert <bernd-schubert@gmx.de>,
	Gerd Hoffmann <kraxel@redhat.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM fixes for 2.6.26-rc7
Date: Thu, 26 Jun 2008 15:43:57 +0200	[thread overview]
Message-ID: <20080626134357.GE21543@ralph.linux2go.dk> (raw)
In-Reply-To: <4863911F.5090807@qumranet.com>

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

On Thu, Jun 26, 2008 at 03:52:47PM +0300, Avi Kivity wrote:
>> The ubuntu kernel has a newer KVM module backported to it so it's
>> really 2.6.25-rcX.
> That's a big no-no.  We only guarantee binary compatibility for
> kernel.org releases.  kvm-blah releases may break compatibility
> temporarily as issues are worked out.

Well, anyhow, let's focus on getting this fixed, shall we?

The kernel modules shipped in 2.6.24 was causing all sorts of issues, so
in an effort to fix those, IIRC I grabbed what was in 2.6.25 at the time
and backported that, so if I were to get this issue fixed, it should be
sufficient to find anything that touches the kvm clock ABI between
2.6.25-rc<whatever I used> and 2.6.25 final. Does that sound about
right?

I'm a bit confused about this, though. I was under the impression that
for the KVM_CLOCK stuff to work, it'd would have to be in the host *and*
the guest kernel, but our kernels don't have KVM_CLOCK enabled at all?

Hmm... Looking at the code, it seems it does require host support, but
it's not #ifdef'ed, so that would explain my confusion..

-- 
Soren Hansen               | 
Virtualisation specialist  | Ubuntu Server Team
Canonical Ltd.             | http://www.ubuntu.com/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2008-06-26 13:43 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-24 21:05 [GIT PULL] KVM fixes for 2.6.26-rc7 Avi Kivity
2008-06-25  1:12 ` Linus Torvalds
2008-06-25  7:08   ` Avi Kivity
2008-06-25 16:13 ` Bernd Schubert
2008-06-25 17:19   ` Marcelo Tosatti
2008-06-25 18:54     ` Bernd Schubert
2008-06-25 19:17       ` Marcelo Tosatti
2008-06-25 19:26         ` Bernd Schubert
2008-06-25 19:33         ` Marcelo Tosatti
2008-06-25 19:44           ` Bernd Schubert
2008-06-26  6:20         ` Gerd Hoffmann
2008-06-26  8:45           ` Bernd Schubert
2008-06-26  9:07             ` Gerd Hoffmann
2008-06-26 12:48             ` Anthony Liguori
2008-06-26 12:52               ` Avi Kivity
2008-06-26 13:12                 ` Soren Hansen
2008-06-29 10:03                   ` Avi Kivity
2008-06-26 13:43                 ` Soren Hansen [this message]
2008-06-26 14:00                   ` Gerd Hoffmann
2008-06-26 14:25                     ` Soren Hansen
2008-06-29  8:59                   ` Avi Kivity
2008-06-30 13:21                     ` Soren Hansen
2008-06-30 13:39                       ` Avi Kivity
2008-06-30 14:21                         ` Soren Hansen
2008-06-30 14:35                           ` Avi Kivity
2008-06-27  5:18 ` Jeremy Fitzhardinge
2008-06-28  4:02   ` Avi Kivity

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=20080626134357.GE21543@ralph.linux2go.dk \
    --to=soren@ubuntu.com \
    --cc=anthony@codemonkey.ws \
    --cc=avi@qumranet.com \
    --cc=bernd-schubert@gmx.de \
    --cc=kraxel@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    /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