linux-stable.git/arch/powerpc/kernel/kvm.c, branch linux-3.4.y

KVM: PPC: Avoid patching paravirt template code

2012-03-05T12:52:34+00:00

Currently we patch the whole code include paravirt template code.
This isn't safe for scratch area and has impact to performance.

Signed-off-by: Liu Yu 
Signed-off-by: Alexander Graf 
Signed-off-by: Avi Kivity

KVM: PPC: Paravirtualize SPRG4-7, ESR, PIR, MASn

2012-03-05T12:52:26+00:00

This allows additional registers to be accessed by the guest
in PR-mode KVM without trapping.

SPRG4-7 are readable from userspace.  On booke, KVM will sync
these registers when it enters the guest, so that accesses from
guest userspace will work.  The guest kernel, OTOH, must consistently
use either the real registers or the shared area between exits.  This
also applies to the already-paravirted SPRG3.

On non-booke, it's not clear to what extent SPRG4-7 are supported
(they're not architected for book3s, but exist on at least some classic
chips).  They are copied in the get/set regs ioctls, but I do not see any
non-booke emulation.  I also do not see any syncing with real registers
(in PR-mode) including the user-readable SPRG3.  This patch should not
make that situation any worse.

Signed-off-by: Scott Wood 
Signed-off-by: Alexander Graf 
Signed-off-by: Avi Kivity

KVM: PPC: booke: Paravirtualize wrtee

2012-03-05T12:52:26+00:00

Also fix wrteei 1 paravirt to check for a pending interrupt.

Signed-off-by: Scott Wood 
Signed-off-by: Alexander Graf 
Signed-off-by: Avi Kivity

powerpc: Copy down exception vectors after feature fixups

2011-11-16T03:47:54+00:00

kdump fails because we try to execute an HV only instruction. Feature
fixups are being applied after we copy the exception vectors down to 0
so they miss out on any updates.

We have always had this issue but it only became critical in v3.0
when we added CFAR support (breaks POWER5) and v3.1 when we added
POWERNV (breaks everyone).

Signed-off-by: Anton Blanchard 
Cc:  [v3.0+]
Signed-off-by: Benjamin Herrenschmidt

powerpc: add export.h to files making use of EXPORT_SYMBOL

2011-10-31T23:30:37+00:00

With module.h being implicitly everywhere via device.h, the absence
of explicitly including something for EXPORT_SYMBOL went unnoticed.
Since we are heading to fix things up and clean module.h from the
device.h file, we need to explicitly include these files now.

Signed-off-by: Paul Gortmaker

PPC: KVM: Book E doesn't have __end_interrupts.

2010-11-05T16:42:27+00:00

Fix an unresolved symbol with CONFIG_KVM_GUEST plus CONFIG_RELOCATABLE on
Book E.

Signed-off-by: Scott Wood 
Signed-off-by: Alexander Graf

KVM: PPC: Enable napping only for Book3s_64

2010-10-24T08:52:19+00:00

Before I incorrectly enabled napping also for BookE, which would result in
needless dcache flushes. Since we only need to force enable napping on
Book3s_64 because it doesn't go into MSR_POW otherwise, we can just #ifdef
that code to this particular platform.

Reported-by: Scott Wood 
Signed-off-by: Alexander Graf

KVM: PPC: Force enable nap on KVM

2010-10-24T08:52:15+00:00

There are some heuristics in the PPC power management code that try to find
out if the particular hardware we're running on supports proper power management
or just hangs the machine when going into nap mode.

Since we know that KVM is safe with nap, let's force enable it in the PV code
once we're certain that we are on a KVM VM.

Signed-off-by: Alexander Graf

KVM: PPC: Make PV mtmsrd L=1 work with r30 and r31

2010-10-24T08:52:14+00:00

We had an arbitrary limitation in mtmsrd L=1 that kept us from using r30 and
r31 as input registers. Let's get rid of that and get more potential speedups!

Signed-off-by: Alexander Graf

KVM: PPC: Make PV mtmsr work with r30 and r31

2010-10-24T08:52:13+00:00

So far we've been restricting ourselves to r0-r29 as registers an mtmsr
instruction could use. This was bad, as there are some code paths in
Linux actually using r30.

So let's instead handle all registers gracefully and get rid of that
stupid limitation

Signed-off-by: Alexander Graf