From: Avi Kivity <avi@qumranet.com>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: kvm-devel@lists.sourceforge.net,
kvm-ppc-devel@lists.sourceforge.net,
Jerone Young <jyoung5@us.ibm.com>
Subject: Re: [PATCH] Move kvm_get_pit to libkvm.c common code
Date: Sun, 23 Mar 2008 10:44:08 +0200 [thread overview]
Message-ID: <47E61858.3000008@qumranet.com> (raw)
In-Reply-To: <1206131180.3136.46.camel@basalt>
Hollis Blanchard wrote:
>
> Don't compile kvm_*_pit() on architectures whose currently supported
> platforms do not contain a PIT.
>
> Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
>
> diff --git a/libkvm/libkvm.h b/libkvm/libkvm.h
> --- a/libkvm/libkvm.h
> +++ b/libkvm/libkvm.h
> @@ -539,6 +539,7 @@ int kvm_pit_in_kernel(kvm_context_t kvm)
>
> #ifdef KVM_CAP_PIT
>
> +#if defined(__i386__) || defined(__x86_64__) || defined(__ia64__)
> /*!
> * \brief Get in kernel PIT of the virtual domain
> *
> @@ -562,6 +563,8 @@ int kvm_set_pit(kvm_context_t kvm, struc
>
> #endif
>
> +#endif
> +
> #ifdef KVM_CAP_VAPIC
ia64 doesn't have an in-kernel pit? (yet?)
--
error compiling committee.c: too many arguments to function
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2008-03-23 8:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 20:17 [PATCH] Move kvm_get_pit to libkvm.c common code Jerone Young
2008-03-12 6:36 ` Yang, Sheng
2008-03-16 11:35 ` Avi Kivity
2008-03-21 20:26 ` Hollis Blanchard
2008-03-23 8:44 ` Avi Kivity [this message]
2008-03-24 1:51 ` [kvm-ppc-devel] [PATCH] Move kvm_get_pit tolibkvm.c " Zhang, Xiantao
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=47E61858.3000008@qumranet.com \
--to=avi@qumranet.com \
--cc=hollisb@us.ibm.com \
--cc=jyoung5@us.ibm.com \
--cc=kvm-devel@lists.sourceforge.net \
--cc=kvm-ppc-devel@lists.sourceforge.net \
/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