From: Paolo Bonzini <pbonzini@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Radim Krcmar <rkrcmar@redhat.com>,
Richard Cochran <richardcochran@gmail.com>,
Miroslav Lichvar <mlichvar@redhat.com>
Subject: Re: [patch 2/4] KVM: x86: add KVM_HC_CLOCK_OFFSET hypercall
Date: Wed, 25 Jan 2017 14:15:40 +0100 [thread overview]
Message-ID: <ba417690-bee4-7495-e4f1-121624521462@redhat.com> (raw)
In-Reply-To: <20170125130627.GB13444@amt.cnet>
On 25/01/2017 14:06, Marcelo Tosatti wrote:
>>> Well you don't know: we could implement it in case of HPET clocksource
>>> hosts.
>> But then the guest wouldn't have a TSC value to use, would it?
>>
>> Also, how would it use more padding?
> I don't know, maybe pass the TSC and host HPET read in the structure?
> (after exposing the HPET to the guest).
>
> Or maybe you want to sync CLOCK_MONOTONIC and that requires other data.
>
> Not sure.
>
> Just some space if new features are necessary.
Fair enough.
Paolo
next prev parent reply other threads:[~2017-01-25 13:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-24 17:09 [patch 0/4] KVM virtual PTP driver (v5) Marcelo Tosatti
2017-01-24 17:09 ` [patch 1/4] KVM: x86: provide realtime host clock via vsyscall notifiers Marcelo Tosatti
2017-01-25 12:30 ` Paolo Bonzini
2017-01-24 17:09 ` [patch 2/4] KVM: x86: add KVM_HC_CLOCK_OFFSET hypercall Marcelo Tosatti
2017-01-25 12:30 ` Paolo Bonzini
2017-01-25 12:55 ` Marcelo Tosatti
2017-01-25 12:59 ` Paolo Bonzini
2017-01-25 13:06 ` Marcelo Tosatti
2017-01-25 13:15 ` Paolo Bonzini [this message]
2017-01-24 17:09 ` [patch 3/4] kvmclock: export kvmclock clocksource pointer Marcelo Tosatti
2017-01-24 17:09 ` [patch 4/4] PTP: add kvm PTP driver Marcelo Tosatti
2017-01-24 18:11 ` Richard Cochran
2017-01-25 12:56 ` Paolo Bonzini
2017-01-25 13:03 ` Marcelo Tosatti
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=ba417690-bee4-7495-e4f1-121624521462@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mlichvar@redhat.com \
--cc=mtosatti@redhat.com \
--cc=richardcochran@gmail.com \
--cc=rkrcmar@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 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.