public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Vogt <vogt@itwm.fraunhofer.de>
To: kvm@vger.kernel.org
Subject: Re: [ANNOUNCE] kvm-79 release
Date: Wed, 12 Nov 2008 15:53:35 +0100	[thread overview]
Message-ID: <491AEDEF.4010105@itwm.fraunhofer.de> (raw)


Hello,


[...]
>Notes:
>If you use the modules bundled with kvm-79, you can use any version
>of Linux from 2.6.16 upwards.

Nope.
I tested kvm-79 on a SLES 10 with 2.6.16,
in the hope that my previously reported bug:

"hrtimer_start: Unknown symbol in module"

was fixed. (It wasnt)

Now I have this "one-liner patch(tm)" here which works for me:


diff -u external-module-compat-comm.h.org external-module-compat-comm.h
--- external-module-compat-comm.h.org   2008-11-12 15:51:55.000000000 +0100
+++ external-module-compat-comm.h       2008-11-12 15:52:05.000000000 +0100
@@ -601,7 +601,7 @@

 static inline void hrtimer_start_expires(struct hrtimer *timer, int mode)
 {
-       hrtimer_start(timer, timer->expires, mode);
+       hrtimer_start_p(timer, timer->expires, mode);
 }



Is this a correct fix?

- I could boot suse 11.1 beta4 with it(which didnt work with kvm-77)

Im really not sure if this works corretly and I dont want have broken
modules in my kernel :(

Is hrtimer_start_p already initialized when  hrtimer_start_expires is
called? (help)

regards,

Martin






             reply	other threads:[~2008-11-12 14:53 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-12 14:53 Martin Vogt [this message]
2008-11-12 14:55 ` [ANNOUNCE] kvm-79 release Avi Kivity
     [not found]   ` <491AF497.7020700@itwm.fraunhofer.de>
2008-11-12 15:27     ` Avi Kivity
  -- strict thread matches above, loose matches on Subject: below --
2008-11-12 12:41 Avi Kivity
2008-11-14 13:44 ` Farkas Levente
2008-11-14 18:46   ` Jan Kiszka
2008-11-14 22:15     ` Charles Duffy

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=491AEDEF.4010105@itwm.fraunhofer.de \
    --to=vogt@itwm.fraunhofer.de \
    --cc=kvm@vger.kernel.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