qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Peter Lieven <pl@dlh.net>
To: Avi Kivity <avi@redhat.com>
Cc: qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [Qemu-devel] Re: disable clocksource=kvm-clock
Date: Wed, 02 Jun 2010 11:58:20 +0200	[thread overview]
Message-ID: <4C062B3C.2060407@dlh.net> (raw)
In-Reply-To: <4C0512AA.6060906@redhat.com>

Avi Kivity wrote:
> On 06/01/2010 04:57 PM, Peter Lieven wrote:
>> Avi Kivity wrote:
>>> On 06/01/2010 04:12 PM, Peter Lieven wrote:
>>>> hi,
>>>>
>>>> is it possible to avoid detection of clocksource=kvm_clock in a 
>>>> linux guest by
>>>> patching the qemu-kvm binary?
>>>> i would like to be able to avoid a guest detecting kvm-clock until 
>>>> bug #584516
>>>> is fixed without modifying all guest systems and reverting that later.
>>>>
>>>
>>> Newer qemu-kvm's will have this feature (using -cpu ...,-kvmclock).
>>>
>> with latest git, i can supply this switch, but
>>
>> cat /sys/devices/system/clocksource/clocksource0/current_clocksource
>>
>> still shows kvm_clock in an opensuse 11.2 64-bit or an ubuntu 10.04 
>> 64-bit guest.
>
> Try again with tomorrow's git, I sent out a patchset earlier today 
> that fixes this.
>
i don't see it in the git, do you mean:
[PATCH 0/5] Use more cpuid bits from upstream

thanks,
peter

      parent reply	other threads:[~2010-06-02  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-01 13:12 [Qemu-devel] disable clocksource=kvm-clock Peter Lieven
2010-06-01 13:17 ` [Qemu-devel] " Avi Kivity
2010-06-01 13:57   ` Peter Lieven
2010-06-01 14:01     ` Avi Kivity
2010-06-01 14:06       ` Peter Lieven
2010-06-01 14:10         ` Avi Kivity
2010-06-01 14:17           ` Peter Lieven
2010-06-02  9:58       ` Peter Lieven [this message]

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=4C062B3C.2060407@dlh.net \
    --to=pl@dlh.net \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).