KVM: PPC: Separate loadstore emulation from priv emulation

Browse source

Today the instruction emulator can get called via 2 separate code paths. It
can either be called by MMIO emulation detection code or by privileged
instruction traps.

This is bad, as both code paths prepare the environment differently. For MMIO
emulation we already know the virtual address we faulted on, so instructions
there don't have to actually fetch that information.

Split out the two separate use cases into separate files.

Signed-off-by: Alexander Graf <agraf@suse.de>

...

This commit is contained in:

Alexander Graf 2014-06-18 14:53:49 +02:00

parent c12fb43c2f

commit d69614a295

5 changed files with 278 additions and 193 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1

arch/powerpc/include/asm/kvm_ppc.h

View file

4

arch/powerpc/kvm/Makefile

View file

192

arch/powerpc/kvm/emulate.c

View file

272

arch/powerpc/kvm/emulate_loadstore.c

View file

2

arch/powerpc/kvm/powerpc.c

View file