[GIT PULL] x86: paravirt_ops updates

[Jeremy Fitzhardinge]

Hi Ingo,

This series has a some changes to x86 paravirt_ops:

x86/paravirt: split paravirt definitions into paravirt_types.h

  Move all the type-like definitions into asm/paravirt_types.h

x86: split out core __math_state_restore

  Split out the core of math_state_restore() into __math_state_restore(),
  which just does what's needed for a context switch (ie, assumes
  TS is already clear, and that the fpu context exists).

x86-32: make sure clts is batched during context switch
x86-64: move unlazy_fpu() into lazy cpu state part of context switch
x86-64: move clts into batch cpu state updates when preloading fpu

  Make sure the TS state updates during context switch are performed in
  the lazy CPU update region so that they can be batched when running
  paravirtualized.

The following changes since commit 9ce5424d75e56891905b77d1589924765e62059a:
  Ingo Molnar (1):
        Merge branch 'x86/urgent'

are available in the git repository at:

  git://git.kernel.org/pub/scm/linux/kernel/git/jeremy/xen.git x86/paravirt

Jeremy Fitzhardinge (5):
      x86/paravirt: split paravirt definitions into paravirt_types.h
      x86: split out core __math_state_restore
      x86-32: make sure clts is batched during context switch
      x86-64: move unlazy_fpu() into lazy cpu state part of context switch
      x86-64: move clts into batch cpu state updates when preloading fpu

 arch/x86/include/asm/i387.h           |    1 +
 arch/x86/include/asm/paravirt.h       |  711 +--------------------------------
 arch/x86/include/asm/paravirt_types.h |  720 +++++++++++++++++++++++++++++++++
 arch/x86/kernel/process_32.c          |   27 +-
 arch/x86/kernel/process_64.c          |   34 +-
 arch/x86/kernel/traps.c               |   33 +-
 6 files changed, 783 insertions(+), 743 deletions(-)
 create mode 100644 arch/x86/include/asm/paravirt_types.h

Thanks,
	J
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/