linux-toradex.git/arch/x86/kernel/kvm.c, branch v3.2.18

KVM guest: KVM Steal time registration

2011-07-24T08:49:36+00:00

This patch implements the kvm bits of the steal time infrastructure.
The most important part of it, is the steal time clock. It is an
continuous clock that shows the accumulated amount of steal time
since vcpu creation. It is supposed to survive cpu offlining/onlining.

[marcelo: fix build with CONFIG_KVM_GUEST=n]

Signed-off-by: Glauber Costa 
Acked-by: Rik van Riel 
Tested-by: Eric B Munson 
CC: Jeremy Fitzhardinge 
CC: Peter Zijlstra 
CC: Avi Kivity 
CC: Anthony Liguori 
Signed-off-by: Avi Kivity 
Signed-off-by: Marcelo Tosatti

KVM guest: Fix section mismatch derived from kvm_guest_cpu_online()

2011-03-17T16:08:25+00:00

WARNING: arch/x86/built-in.o(.text+0x1bb74): Section mismatch in reference from the function kvm_guest_cpu_online() to the function .cpuinit.text:kvm_guest_cpu_init()
The function kvm_guest_cpu_online() references
the function __cpuinit kvm_guest_cpu_init().
This is often because kvm_guest_cpu_online lacks a __cpuinit
annotation or the annotation of kvm_guest_cpu_init is wrong.

This patch fixes the warning.

Tested with linux-next (next-20101231)

Signed-off-by: Sedat Dilek 
Acked-by: Rik van Riel 
Signed-off-by: Marcelo Tosatti

KVM guest: Fix kvm clock initialization when it's configured out

2011-01-12T09:30:56+00:00

Signed-off-by: Avi Kivity

KVM: Let host know whether the guest can handle async PF in non-userspace context.

2011-01-12T09:23:21+00:00

If guest can detect that it runs in non-preemptable context it can
handle async PFs at any time, so let host know that it can send async
PF even if guest cpu is not in userspace.

Acked-by: Rik van Riel 
Signed-off-by: Gleb Natapov 
Signed-off-by: Marcelo Tosatti

KVM paravirt: Handle async PF in non preemptable context

2011-01-12T09:23:19+00:00

If async page fault is received by idle task or when preemp_count is
not zero guest cannot reschedule, so do sti; hlt and wait for page to be
ready. vcpu can still process interrupts while it waits for the page to
be ready.

Acked-by: Rik van Riel 
Signed-off-by: Gleb Natapov 
Signed-off-by: Marcelo Tosatti

KVM: Handle async PF in a guest.

2011-01-12T09:23:16+00:00

When async PF capability is detected hook up special page fault handler
that will handle async page fault events and bypass other page faults to
regular page fault handler. Also add async PF handling to nested SVM
emulation. Async PF always generates exit to L1 where vcpu thread will
be scheduled out until page is available.

Acked-by: Rik van Riel 
Signed-off-by: Gleb Natapov 
Signed-off-by: Marcelo Tosatti

KVM paravirt: Add async PF initialization to PV guest.

2011-01-12T09:23:14+00:00

Enable async PF in a guest if async PF capability is discovered.

Acked-by: Rik van Riel 
Signed-off-by: Gleb Natapov 
Signed-off-by: Marcelo Tosatti

KVM paravirt: Move kvm_smp_prepare_boot_cpu() from kvmclock.c to kvm.c.

2011-01-12T09:23:10+00:00

Async PF also needs to hook into smp_prepare_boot_cpu so move the hook
into generic code.

Acked-by: Rik van Riel 
Signed-off-by: Gleb Natapov 
Signed-off-by: Marcelo Tosatti

KVM guest: do not batch pte updates from interrupt context

2009-09-10T15:10:50+00:00

Commit b8bcfe997e4 made paravirt pte updates synchronous in interrupt
context.

Unfortunately the KVM pv mmu code caches the lazy/nonlazy mode
internally, so a pte update from interrupt context during a lazy mmu
operation can be batched while it should be performed synchronously.

https://bugzilla.redhat.com/show_bug.cgi?id=518022

Drop the internal mode variable and use paravirt_get_lazy_mode(), which
returns the correct state.

Cc: stable@kernel.org
Signed-off-by: Marcelo Tosatti 
Signed-off-by: Avi Kivity

x86, kvm: Fix section mismatches in kvm.c

2009-07-03T12:34:22+00:00

The function paravirt_ops_setup() has been refering the
variable no_timer_check, which is a __initdata. Thus generates
the following warning. paravirt_ops_setup() function is called
from kvm_guest_init() which is a __init function. So to fix
this we mark paravirt_ops_setup as __init.

The sections-check output that warned us about this was:

   LD      arch/x86/built-in.o
  WARNING: arch/x86/built-in.o(.text+0x166ce): Section mismatch in
  reference from the function paravirt_ops_setup() to the variable
  .init.data:no_timer_check
  The function paravirt_ops_setup() references
  the variable __initdata no_timer_check.
  This is often because paravirt_ops_setup lacks a __initdata
  annotation or the annotation of no_timer_check is wrong.

Signed-off-by: Rakib Mullick 
Acked-by: Avi Kivity 
Cc: Andrew Morton 
LKML-Reference: 
Signed-off-by: Ingo Molnar