On 01/10/2010 02:22 PM, Avi Kivity wrote:
On 01/10/2010 04:27 AM, Alexander Graf wrote:
When we get a program interrupt in guest kernel mode, we try to
emulate the
instruction.
If that doesn't fail, we report to the user and try again - at the
exact same
instruction pointer. So if the guest kernel really does trigger an
invalid
instruction, we loop forever.
So let's better go and forward program exceptions to the guest when
we don't
know the instruction we're supposed to emulate.
Applied both, and queued for .33. I was able to guess this from the
description, but please mention it explicitly in the future.
I get this building ppc32:
scripts/kconfig/conf -s arch/powerpc/Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
CALL scripts/checksyscalls.sh
<stdin>:1523:2: warning: #warning syscall recvmmsg not implemented
CC arch/powerpc/kvm/emulate.o
arch/powerpc/kvm/emulate.c: In function 'kvmppc_emulate_instruction':
arch/powerpc/kvm/emulate.c:467: error: too many arguments to function
'kvmppc_core_queue_program'
make[1]: *** [arch/powerpc/kvm/emulate.o] Error 1
--
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 majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
