From: Avi Kivity <avi@qumranet.com>
To: kvm@vger.kernel.org
Subject: Re: [GIT PULL] KVM fixes for 2.6.26-rc7
Date: Mon, 30 Jun 2008 17:35:02 +0300 [thread overview]
Message-ID: <4868EF16.7000902@qumranet.com> (raw)
In-Reply-To: <20080630142150.GE8698@ralph.linux2go.dk>
Soren Hansen wrote:
> On Mon, Jun 30, 2008 at 04:39:23PM +0300, Avi Kivity wrote:
>
>>>> Yeah. To be on the safe side you can have KVM_CHECK_EXTENSION
>>>> return false for KVM_CAP_CLOCKSOURCE.
>>>>
>>> Oh! That's even better. Would that be sufficient? I mean, do all
>>> guest versions check this before trying to use the paravirt clock?
>>>
>> You need to disable the host side (KVM_CAP_CLOCKSOURCE) and the guest
>> side (CONFIG_KVM_GUEST).
>>
>
> Well, we don't have KVM_GUEST in the Ubuntu 8.04 kernels anyway (them
> being 2.6.24 based and all), so returning false for KVM_CAP_CLOCKSOURCE
> should be sufficient, I presume?
>
>
Yes.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-06-30 14:35 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
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 [this message]
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=4868EF16.7000902@qumranet.com \
--to=avi@qumranet.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.