Glauber Costa wrote:
There's no need to polute the already poluted CPUState
with "ready_for_interrupt_injection". We can compute it
in the few times we use it, and be fine.
#define CPUState CPUIA64State
diff --git a/qemu/target-ia64/op_helper.c b/qemu/target-ia64/op_helper.c
index 4969ef7..f582023 100644
--- a/qemu/target-ia64/op_helper.c
+++ b/qemu/target-ia64/op_helper.c
@@ -36,7 +36,6 @@ CPUState *cpu_ia64_init(char *cpu_model){
cpu_reset(env);
if (kvm_enabled()) {
kvm_qemu_init_env(env);
- env->ready_for_interrupt_injection = 1;
kvm_init_new_ap(env->cpu_index, env);
}
return env;
This bit means that this patch is not an identity transformation.
Anthony/Xiantao, can you confirm that this patch is safe for ia64?
--
Do not meddle in the internals of kernels, for they are subtle and quick to
panic.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
