From mboxrd@z Thu Jan  1 00:00:00 1970
From: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [patch 2/4] KVM: x86: add KVM_HC_CLOCK_OFFSET hypercall
Date: Wed, 25 Jan 2017 14:15:40 +0100
Message-ID: <ba417690-bee4-7495-e4f1-121624521462@redhat.com>
References: <20170124170938.909652059@redhat.com>
 <20170124171020.377051231@redhat.com>
 <1c6182a5-9894-74c5-23bd-872d7e9e20b5@redhat.com>
 <20170125125505.GC10780@amt.cnet>
 <aaead840-52c9-5b7f-1466-8a6c53f66f7d@redhat.com>
 <20170125130627.GB13444@amt.cnet>
Mime-Version: 1.0
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
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>
To: Marcelo Tosatti <mtosatti@redhat.com>
Return-path: <linux-kernel-owner@vger.kernel.org>
In-Reply-To: <20170125130627.GB13444@amt.cnet>
Sender: linux-kernel-owner@vger.kernel.org
List-Id: kvm.vger.kernel.org



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