Skip to content

*** SUBJECT HERE ***

Jeremy Fitzhardinge lkml xen-devel 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest7 of 9 patches 8 repliesIn review

7 of 9 patches are in this archive. The cover letter announces 9.

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
3/9x86/paravirt: remove lazy mode in interruptsarch/x86/kernel/paravirt.c arch/x86/mm/fault.c arch/x86/mm/highmem_32.c +2 more+5 -222 replies
4/9x86/pvops: replace arch_enter_lazy_cpu_mode with arch_start_context_switcharch/x86/include/asm/paravirt.h arch/x86/kernel/paravirt.c arch/x86/kernel/process_32.c +5 more+20 -370 replies
5/9x86/paravirt: flush pending mmu updates on context switcharch/x86/include/asm/paravirt.h arch/x86/include/asm/thread_info.h arch/x86/kernel/kvm.c +6 more+42 -180 replies
6/9x86/paravirt: allow preemption with lazy mmu modearch/x86/kernel/paravirt.c arch/x86/xen/mmu.c+5 -100 replies
7/9mm: allow preemption in apply_to_pte_rangemm/memory.c+0 -20 replies
8/9x86/paravirt: use percpu_ rather than __get_cpu_vararch/x86/kernel/paravirt.c+5 -50 replies
9/9x86/paravirt: finish change from lazy cpu to context switch start/endarch/x86/include/asm/paravirt.h arch/x86/include/asm/pgtable.h arch/x86/kernel/paravirt.c +8 more+37 -360 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH 0/9] *** SUBJECT HERE ***

From: Jeremy Fitzhardinge <[email protected]>

Hi,

This series changes the paravirt-ops lazy update modes in the following ways:

1. Make paravirt_get_lazy_mode() always return PARAVIRT_LAZY_NONE in interrupt context. This has the effect of making all mmu and cpu state updates synchronous in interrupt routines, without the need to add explicit flushing.

2. De-generalize lazy cpu mode to a specific context-switch operation. Rather than dealing with fully general enter/leave lazy cpu update mode, make it specifically about start/end context switch, since that was the only use anyway. That means the implementations know that they're in the middle of a context switch.

3. On starting a context switch, if the task is in lazy mmu update mode, record that fact in thread_info->flags TIF_LAZY_MMU_UPDATE, and disable lazy updates (flushing anything pending). On ending a context switch, if the new task has TIF_LAZY_MMU_UPDATE set, then reenter lazy mmu update mode.

4. Remove all the preempt_disable/enable pairs and assertion that preemption must be disabled for lazy mmu updates.

This has the net effect of 1) making lazy mmu updates more robust, and
2) not requiring any changes to the current rules of how init_mm can be updated.

Thanks,
J

Jeremy Fitzhardinge (7):
x86/paravirt: remove lazy mode in interrupts
x86/pvops: replace arch_enter_lazy_cpu_mode with arch_start_context_switch x86/paravirt: flush pending mmu updates on context switch x86/paravirt: allow preemption with lazy mmu mode
mm: allow preemption in apply_to_pte_range
x86/paravirt: use percpu_ rather than __get_cpu_var x86/paravirt: finish change from lazy cpu to context switch start/end