public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: ehrhardt@linux.vnet.ibm.com
To: kvm-ppc@vger.kernel.org, kvm@vger.kernel.org, avi@qumranet.com
Cc: hollisb@us.ibm.com, ehrhardt@linux.vnet.ibm.com
Subject: [PATCH] kvmppc: comply with requirement for kvm_arch_try_push_nmi
Date: Fri, 17 Oct 2008 10:46:50 +0200	[thread overview]
Message-ID: <1224233210-27223-1-git-send-email-ehrhardt@linux.vnet.ibm.com> (raw)

From: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>

Since a recent patch all architetcures need a kvm_arch_try_push_nmi function.
Powerpc has no direct nmi equivalent, so this patch fixes only build for
powerpc by adding an empty stub.
If powerpc later wants to support the nmi monitor command somehow the function
can still be extended.

Signed-off-by: Christian Ehrhardt <ehrhardt@linux.vnet.ibm.com>
---

[diffstat]
 qemu-kvm-powerpc.c |    8 ++++++++
 1 file changed, 8 insertions(+)

[diff]
diff --git a/qemu/qemu-kvm-powerpc.c b/qemu/qemu-kvm-powerpc.c
--- a/qemu/qemu-kvm-powerpc.c
+++ b/qemu/qemu-kvm-powerpc.c
@@ -190,6 +190,14 @@
     return 0;
 }
 
+int kvm_arch_try_push_nmi(void *opaque)
+{
+	/* no nmi irq, so discard that call for now and return success.
+	 * This might later get mapped to something on powerpc too if we want
+	 *  to support the nmi monitor command somwhow */
+	return 0;
+}
+
 void kvm_arch_update_regs_for_sipi(CPUState *env)
 {
     printf("%s: no kvm-powerpc multi processor support yet!\n", __func__);

             reply	other threads:[~2008-10-17  8:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-17  8:46 ehrhardt [this message]
2008-10-17 14:47 ` [PATCH] kvmppc: comply with requirement for kvm_arch_try_push_nmi Hollis Blanchard
2008-10-19 10:09 ` 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=1224233210-27223-1-git-send-email-ehrhardt@linux.vnet.ibm.com \
    --to=ehrhardt@linux.vnet.ibm.com \
    --cc=avi@qumranet.com \
    --cc=hollisb@us.ibm.com \
    --cc=kvm-ppc@vger.kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox