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:19:33 +0200 [thread overview]
Message-ID: <483C0A65.2090208@redhat.com> (raw)
In-Reply-To: <48353DB4.1020303@redhat.com>
Gerd Hoffmann wrote:
>> 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 ...
ping ...
cheers,
Gerd
--
http://kraxel.fedorapeople.org/xenner/
next prev parent reply other threads:[~2008-05-27 13:19 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 [this message]
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
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=483C0A65.2090208@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).