From: Alexander Graf <agraf@suse.de>
To: qemu-devel@nongnu.org
Cc: hollisb@us.ibm.com
Subject: [Qemu-devel] [PATCH 5/7] Use correct input constant
Date: Fri, 17 Jul 2009 13:51:46 +0200 [thread overview]
Message-ID: <1247831508-19023-6-git-send-email-agraf@suse.de> (raw)
In-Reply-To: <1247831508-19023-5-git-send-email-agraf@suse.de>
440 and desktop codes use different input constants for interrupt indication.
Let's use the respective ones for KVM.
Signed-off-by: Alexander Graf <agraf@suse.de>
---
target-ppc/kvm.c | 10 +++++++++-
1 files changed, 9 insertions(+), 1 deletions(-)
diff --git a/target-ppc/kvm.c b/target-ppc/kvm.c
index 04bb305..b53d6e9 100644
--- a/target-ppc/kvm.c
+++ b/target-ppc/kvm.c
@@ -124,6 +124,14 @@ int kvm_arch_get_registers(CPUState *env)
return 0;
}
+#if defined(TARGET_PPCEMB)
+#define PPC_INPUT_INT PPC40x_INPUT_INT
+#elif defined(TARGET_PPC64)
+#define PPC_INPUT_INT PPC970_INPUT_INT
+#else
+#define PPC_INPUT_INT PPC6xx_INPUT_INT
+#endif
+
int kvm_arch_pre_run(CPUState *env, struct kvm_run *run)
{
int r;
@@ -133,7 +141,7 @@ int kvm_arch_pre_run(CPUState *env, struct kvm_run *run)
* interrupt, reset, etc) in PPC-specific env->irq_input_state. */
if (run->ready_for_interrupt_injection &&
(env->interrupt_request & CPU_INTERRUPT_HARD) &&
- (env->irq_input_state & (1<<PPC40x_INPUT_INT)))
+ (env->irq_input_state & (1<<PPC_INPUT_INT)))
{
/* For now KVM disregards the 'irq' argument. However, in the
* future KVM could cache it in-kernel to avoid a heavyweight exit
--
1.6.0.2
next prev parent reply other threads:[~2009-07-17 11:52 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 11:51 [Qemu-devel] [PATCH 0/4] Add preliminary KVM support for non-embedded PPC v3 Alexander Graf
2009-07-17 11:51 ` [Qemu-devel] [PATCH 1/7] Enable PPC KVM for non-embedded Alexander Graf
2009-07-17 11:51 ` [Qemu-devel] [PATCH 2/7] Set PVR in sregs Alexander Graf
2009-07-17 11:51 ` [Qemu-devel] [PATCH 3/7] Add mp_state to PPC CPU struct Alexander Graf
2009-07-17 11:51 ` [Qemu-devel] [PATCH 4/7] Fix warning in kvm-all.c Alexander Graf
2009-07-17 11:51 ` Alexander Graf [this message]
2009-07-17 11:51 ` [Qemu-devel] [PATCH 6/7] Set slots more carefully Alexander Graf
2009-07-17 11:51 ` [Qemu-devel] [PATCH 7/7] Fake dirty loggin when it's not there Alexander Graf
2009-07-17 12:10 ` Stefano Stabellini
2009-07-17 12:14 ` Alexander Graf
2009-07-17 12:18 ` Alexander Graf
2009-07-17 12:25 ` Stefano Stabellini
2009-07-17 12:27 ` Alexander Graf
2009-07-17 13:18 ` Stefano Stabellini
2009-07-17 13:23 ` Alexander Graf
2009-07-17 14:37 ` [Qemu-devel] " Jan Kiszka
2009-07-17 15:00 ` Alexander Graf
2009-07-17 15:47 ` Jan Kiszka
2009-07-17 13:48 ` [Qemu-devel] Re: [PATCH 6/7] Set slots more carefully Jan Kiszka
2009-07-17 13:53 ` Alexander Graf
2009-07-17 14:18 ` Jan Kiszka
2009-07-17 14:23 ` Alexander Graf
2009-07-17 14:30 ` Jan Kiszka
2009-07-21 22:55 ` [Qemu-devel] " Anthony Liguori
2009-07-22 15:34 ` [Qemu-devel] [PATCH 3/7] Add mp_state to PPC CPU struct Anthony Liguori
2009-07-22 15:59 ` Hollis Blanchard
2009-07-22 16:22 ` Anthony Liguori
2009-07-22 16:26 ` Hollis Blanchard
2009-07-22 16:51 ` [Qemu-devel] " Jan Kiszka
2009-07-22 18:11 ` Anthony Liguori
2009-07-22 19:11 ` Jan Kiszka
2009-07-21 22:36 ` [Qemu-devel] Re: [PATCH 0/4] Add preliminary KVM support for non-embedded PPC v3 Hollis Blanchard
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=1247831508-19023-6-git-send-email-agraf@suse.de \
--to=agraf@suse.de \
--cc=hollisb@us.ibm.com \
--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).