On 02/07/2010 05:57 PM, Alexander Graf wrote:+
+ dprintk(KERN_INFO "FPU Emulator 0x%x ( 0x%llx, 0x%llx, 0x%llx )", inst,
+                inout[1], inout[2], inout[3]);
+
+    call_stack =&kvmppc_call_stack[(smp_processor_id() * 2)];
+    call_stack[0] = inst;
+    /* call_stack[1] is INS_BLR */
+


Would be easier on the cache to do this per-cpu?

It is per-cpu. Or do you mean to actually use the PER_CPU definition? Is that guaranteed to be executable?

I meant, per-cpu vmalloc area, but it should be enough to have a per-cpu cache line.

--
error compiling committee.c: too many arguments to function

--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to