1. 15 10月, 2008 1 次提交
  2. 25 8月, 2008 1 次提交
    • E
      KVM: Use .fixup instead of .text.fixup on __kvm_handle_fault_on_reboot · 18b13e54
      Eduardo Habkost 提交于
      vmlinux.lds expects the fixup code to be on a section named .fixup. The
      .text.fixup section is not mentioned on vmlinux.lds, and is included on
      the resulting vmlinux (just after .text) only because of ld heuristics on
      placing orphan sections.
      
      However, placing .text.fixup outside .text breaks the definition of
      _etext, making it exclude the .text.fixup contents. That makes .text.fixup
      be ignored by the kernel initialization code that needs to know about
      section locations, such as the code setting page protection bits.
      Signed-off-by: NEduardo Habkost <ehabkost@redhat.com>
      Signed-off-by: NAvi Kivity <avi@qumranet.com>
      18b13e54
  3. 29 7月, 2008 1 次提交
  4. 27 7月, 2008 1 次提交
  5. 23 7月, 2008 2 次提交
  6. 21 7月, 2008 1 次提交
    • I
      KVM: fix exception entry / build bug, on 64-bit · 33a37eb4
      Ingo Molnar 提交于
      -tip testing found this build bug:
      
       arch/x86/kvm/built-in.o:(.text.fixup+0x1): relocation truncated to fit: R_X86_64_32 against `.text'
       arch/x86/kvm/built-in.o:(.text.fixup+0xb): relocation truncated to fit: R_X86_64_32 against `.text'
       arch/x86/kvm/built-in.o:(.text.fixup+0x15): relocation truncated to fit: R_X86_64_32 against `.text'
       arch/x86/kvm/built-in.o:(.text.fixup+0x1f): relocation truncated to fit: R_X86_64_32 against `.text'
       arch/x86/kvm/built-in.o:(.text.fixup+0x29): relocation truncated to fit: R_X86_64_32 against `.text'
      
      Introduced by commit 4ecac3fd. The problem is that 'push' will default
      to 32-bit, which is not wide enough as a fixup address. (and which would
      crash on any real fixup event even if it was wide enough)
      
      Introduce KVM_EX_PUSH to get the proper address push width on 64-bit too.
      Signed-off-by: NIngo Molnar <mingo@elte.hu>
      33a37eb4
  7. 20 7月, 2008 10 次提交
  8. 25 6月, 2008 1 次提交
  9. 04 5月, 2008 5 次提交
  10. 27 4月, 2008 17 次提交