From: Avi Kivity <avi@redhat.com>
To: Mark McLoughlin <markmc@redhat.com>
Cc: kvm@vger.kernel.org
Subject: Re: [PATCH] kvm: qemu: framebuffer: build fix for target-arm
Date: Tue, 28 Apr 2009 12:34:09 +0300 [thread overview]
Message-ID: <49F6CD91.9010602@redhat.com> (raw)
In-Reply-To: <1240842918-24649-1-git-send-email-markmc@redhat.com>
Mark McLoughlin wrote:
> Include qemu-kvm.h for non-KVM_UPSTREAM building and surround the
> kvm code with USE_KVM guards.
>
> Fixes target-arm:
>
> qemu/hw/framebuffer.c: In function 'framebuffer_update_display':
> qemu/hw/framebuffer.c:53: warning: implicit declaration of function 'kvm_enabled'
> qemu/hw/framebuffer.c:54: warning: implicit declaration of function 'kvm_physical_sync_dirty_bitmap'
>
> diff --git a/hw/framebuffer.c b/hw/framebuffer.c
> index 1086ba9..e2d7604 100644
> --- a/hw/framebuffer.c
> +++ b/hw/framebuffer.c
> @@ -18,6 +18,7 @@
> #include "console.h"
> #include "framebuffer.h"
> #include "kvm.h"
> +#include "qemu-kvm.h"
>
Maybe we should have kvm.h include qemu-kvm.h, to avoid more divergence
(even if it is trivial).
>
> /* Render an image from a shared memory framebuffer. */
>
> @@ -50,9 +51,11 @@ void framebuffer_update_display(
> *first_row = -1;
> src_len = src_width * rows;
>
> +#ifdef USE_KVM
> if (kvm_enabled()) {
> kvm_physical_sync_dirty_bitmap(base, src_len);
> }
> +#endif
Similarly, provide null definitions for kvm_enabled() and
kvm_physical_blah() to avoid the ifdefs.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
prev parent reply other threads:[~2009-04-28 9:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-27 14:35 [PATCH] kvm: qemu: framebuffer: build fix for target-arm Mark McLoughlin
2009-04-28 9:34 ` Avi Kivity [this message]
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=49F6CD91.9010602@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=markmc@redhat.com \
/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