From: Gerd Hoffmann <kraxel@redhat.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: kvm-devel@lists.sourceforge.net, virtualization@lists.osdl.org
Subject: Re: [PATCH 1/4] Add helper functions for paravirtual clocksources.
Date: Thu, 22 May 2008 11:32:36 +0200 [thread overview]
Message-ID: <48353DB4.1020303@redhat.com> (raw)
In-Reply-To: <4834A630.7060208@goop.org>
Jeremy Fitzhardinge wrote:
>> +static unsigned pvclock_get_time_values(struct pvclock_shadow_time *dst,
>> + struct kvm_vcpu_time_info *src)
>>
>
> I think the kvm_* types should be renamed. xen_* would make some sense
> since the ABI originated with Xen, but something generic would be OK
> too. The important thing to get across is that the structure defines a
> guest<->host ABI which happens to be shared by Xen and KVM, and it isn't
> an in-kernel API like the rest of paravirt_ops.
Fine with me, but see below.
> And having defined a common structure, we may as well use it in the
> hypervisor-specific code/headers so there's no strange casting going on.
Hmm, what is the state of include/xen/interface/? It is a straight copy
of the xen public header files, right? Is it really ok to modify them?
We have to do that to make the cast actually go away ...
>> +/*
>> + * This is our read_clock function. The host puts an tsc timestamp
>> each time
>> + * it updates a new time. Without the tsc adjustment, we can have a
>> situation
>> + * in which a vcpu starts to run earlier (smaller system_time), but
>> probes
>> + * time later (compared to another vcpu), leading to backwards time
>> + */
>>
>
> This comment is confusing. Are you explaining why the tsc is read
> within the loop? I think it can be clarified.
This was just copyed over from somewhere else (kvmclock I think).
>> +++ b/include/asm-x86/pvclock.h
>> @@ -0,0 +1,6 @@
>> +#include <linux/clocksource.h>
>> +#include <asm/kvm_para.h>
>> +cycle_t pvclock_clocksource_read(struct kvm_vcpu_time_info *src);
>> +void pvclock_read_wallclock(struct kvm_wall_clock *wall,
>> + struct kvm_vcpu_time_info *vcpu,
>> + struct timespec *ts);
>>
>
> No #ifdef guards?
Oh yes, I should better add some ...
thanks,
Gerd
--
http://kraxel.fedorapeople.org/xenner/
next prev parent reply other threads:[~2008-05-22 9:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-16 8:01 [PATCH 0/4] paravirt clock source patches, #3 Gerd Hoffmann
2008-05-16 8:01 ` [PATCH 1/4] Add helper functions for paravirtual clocksources Gerd Hoffmann
2008-05-21 22:46 ` Jeremy Fitzhardinge
2008-05-22 9:32 ` Gerd Hoffmann [this message]
2008-05-22 9:55 ` Jeremy Fitzhardinge
2008-05-27 13:19 ` Gerd Hoffmann
2008-05-27 13:23 ` Jeremy Fitzhardinge
2008-05-27 13:52 ` Gerd Hoffmann
2008-05-16 8:01 ` [PATCH 2/4] Make xen use the generic paravirt clocksource code Gerd Hoffmann
2008-05-16 8:01 ` [PATCH 3/4] kvm/host: fix paravirt clocksource to be compatible with xen Gerd Hoffmann
2008-05-16 8:01 ` [PATCH 4/4] kvm/guest: fix paravirt clocksource to be compartible " Gerd Hoffmann
2008-05-21 15:22 ` [kvm-devel] [PATCH 0/4] paravirt clock source patches, #3 Avi Kivity
-- strict thread matches above, loose matches on Subject: below --
2008-05-08 11:48 [PATCH 0/4] paravirt clock series Gerd Hoffmann
2008-05-08 11:48 ` [PATCH 1/4] Add helper functions for paravirtual clocksources Gerd Hoffmann
2008-04-24 8:37 [PATCH 0/4] paravirt clock patches Gerd Hoffmann
2008-04-24 8:37 ` [PATCH 1/4] Add helper functions for paravirtual clocksources Gerd Hoffmann
2008-04-24 13:11 ` Glauber Costa
2008-04-28 8:54 ` Gerd Hoffmann
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=48353DB4.1020303@redhat.com \
--to=kraxel@redhat.com \
--cc=jeremy@goop.org \
--cc=kvm-devel@lists.sourceforge.net \
--cc=virtualization@lists.osdl.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.