virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
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: Tue, 27 May 2008 15:52:40 +0200	[thread overview]
Message-ID: <483C1228.4010004@redhat.com> (raw)
In-Reply-To: <483C0B4E.9050909@goop.org>

Jeremy Fitzhardinge wrote:
> Hm?  I sent a reply, didn't I?  Attached again.

Hmm, seems to have gotten lost somewhere, I can't remember having seen
that one.  Lossy email sucks :-(

>> 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?
>>   
> 
> Yeah, sure.  They were copied once, but they can now drift without 
> consequence.  Xen defines an ABI, so it doesn't matter how the source 
> spells the names of the structures.

Ok, so I'll go just doing that ;)

>>> 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).
>>   
> 
> OK, but it still needs to be clarified.

Yep, will do.

> Also, the patches themselves need some changelogs.  Even though they're 
> mostly just code motion, it would be good if the changelog for the 
> common pvclock code had a description of the basics of operation.
> 
> Also, one implicit part of the ABI which should be explicitly documented 
> is that the interface expects that the host updates the per-vcpu time 
> structures on the same physical CPU that the guest runs, and that's why 
> we can avoid explicit cross-cpu ordering barriers.

pvclock.h is probably a good place for the structs and the comments ...

cheers,
  Gerd

-- 
http://kraxel.fedorapeople.org/xenner/

  reply	other threads:[~2008-05-27 13:52 UTC|newest]

Thread overview: 13+ 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
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 [this message]
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

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=483C1228.4010004@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 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).