From: Glauber Costa <glommer@redhat.com>
To: kvm@vger.kernel.org
Cc: qemu-devel@nongnu.org, hollisb@us.ibm.com, avi@redhat.com
Subject: [Qemu-devel] [PATCH] use KVM_UPSTREAM for ppc.
Date: Fri, 13 Feb 2009 13:07:26 -0500 [thread overview]
Message-ID: <1234548446-30006-1-git-send-email-glommer@redhat.com> (raw)
ppc should compile with upstream qemu code, so, put these
defines in ppc specific code that references kvm functions.
We don put them in config.h in this case, since there are
files (like vl.c) that includes both kvm.h and qemu-kvm.h,
and would break compilation.
Signed-off-by: Glauber Costa <glommer@redhat.com>
---
qemu/hw/ppc440.c | 1 +
qemu/hw/ppc440_bamboo.c | 1 +
qemu/target-ppc/helper.c | 1 +
3 files changed, 3 insertions(+), 0 deletions(-)
diff --git a/qemu/hw/ppc440.c b/qemu/hw/ppc440.c
index 00d82e4..164c326 100644
--- a/qemu/hw/ppc440.c
+++ b/qemu/hw/ppc440.c
@@ -18,6 +18,7 @@
#include "ppc440.h"
#include "ppc405.h"
#include "sysemu.h"
+#define KVM_UPSTREAM
#include "kvm.h"
#define PPC440EP_PCI_CONFIG 0xeec00000
diff --git a/qemu/hw/ppc440_bamboo.c b/qemu/hw/ppc440_bamboo.c
index fbd447c..60ddaf4 100644
--- a/qemu/hw/ppc440_bamboo.c
+++ b/qemu/hw/ppc440_bamboo.c
@@ -21,6 +21,7 @@
#include "boards.h"
#include "sysemu.h"
#include "ppc440.h"
+#define KVM_UPSTREAM
#include "kvm.h"
#include "kvm_ppc.h"
#include "device_tree.h"
diff --git a/qemu/target-ppc/helper.c b/qemu/target-ppc/helper.c
index fc62a63..d49acaf 100644
--- a/qemu/target-ppc/helper.c
+++ b/qemu/target-ppc/helper.c
@@ -29,6 +29,7 @@
#include "exec-all.h"
#include "helper_regs.h"
#include "qemu-common.h"
+#define KVM_UPSTREAM
#include "kvm.h"
//#define DEBUG_MMU
--
1.5.6.5
next reply other threads:[~2009-02-13 18:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-13 18:07 Glauber Costa [this message]
2009-02-13 19:13 ` [Qemu-devel] Re: [PATCH] use KVM_UPSTREAM for ppc Hollis Blanchard
2009-02-13 19:20 ` Glauber Costa
2009-02-16 23:57 ` Dustin Kirkland
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=1234548446-30006-1-git-send-email-glommer@redhat.com \
--to=glommer@redhat.com \
--cc=avi@redhat.com \
--cc=hollisb@us.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=qemu-devel@nongnu.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).