From: Laurent Vivier <Laurent.Vivier@bull.net>
To: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] libkvm: export init for coalesced MMIO support
Date: Wed, 18 Jun 2008 09:39:46 +0200 [thread overview]
Message-ID: <1213774786.3854.3.camel@frecb07144> (raw)
In-Reply-To: <20080618052216.GB1486@tapir>
Le mercredi 18 juin 2008 à 00:22 -0500, Carlo Marcelo Arenas Belon a
écrit :
> complement 2680f3df932a3119880a692609943587ecc8f409 to export the
> definition for kvm_init_coalesced_mmio as it is used by the per
> arch libkvm as shown by the following warning :
>
> libkvm-x86.c: In function 'kvm_arch_create':
> libkvm-x86.c:182: warning: implicit declaration of function 'kvm_init_coalesced_mmio'
>
> Signed-off-by: Carlo Marcelo Arenas Belon <carenas@sajinet.com.pe>
Looks good for me.
Laurent
> ---
> libkvm/libkvm.h | 9 +++++++++
> 1 files changed, 9 insertions(+), 0 deletions(-)
>
> diff --git a/libkvm/libkvm.h b/libkvm/libkvm.h
> index a33e9db..4fd8587 100644
> --- a/libkvm/libkvm.h
> +++ b/libkvm/libkvm.h
> @@ -576,6 +576,15 @@ int kvm_set_lapic(kvm_context_t kvm, int vcpu, struct kvm_lapic_state *s);
> */
> int kvm_pit_in_kernel(kvm_context_t kvm);
>
> +/*!
> + * \brief Initialize coalesced MMIO
> + *
> + * Check for coalesced MMIO capability and store in context
> + *
> + * \param kvm Pointer to the current kvm_context
> + */
> +int kvm_init_coalesced_mmio(kvm_context_t kvm);
> +
> #ifdef KVM_CAP_PIT
>
> #if defined(__i386__) || defined(__x86_64__)
--
------------- Laurent.Vivier@bull.net ---------------
"The best way to predict the future is to invent it."
- Alan Kay
next prev parent reply other threads:[~2008-06-18 7:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-18 5:22 [PATCH] libkvm: export init for coalesced MMIO support Carlo Marcelo Arenas Belon
2008-06-18 7:39 ` Laurent Vivier [this message]
2008-06-18 14:27 ` Avi Kivity
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=1213774786.3854.3.camel@frecb07144 \
--to=laurent.vivier@bull.net \
--cc=carenas@sajinet.com.pe \
--cc=kvm@vger.kernel.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.