similar to: [RFC, PATCH 20/24] i386 Vmi module fixups

Linker changes to add the VMI MACH_TEXT area into the kernel text section. This area layout is heavily influenced by magic to overlap exactly with the 32-byte VMI ROM entry points, allowing the kernel to copy the VMI ROM over the native section. As use of magic is on the decline, this approach is being phased out in favor of the more modern approach of the inline implementation. The translation

Linker changes to add the VMI MACH_TEXT area into the kernel text section. This area layout is heavily influenced by magic to overlap exactly with the 32-byte VMI ROM entry points, allowing the kernel to copy the VMI ROM over the native section. As use of magic is on the decline, this approach is being phased out in favor of the more modern approach of the inline implementation. The translation

Hi Peter, Removal of VMI(VMware's para-virtualization technique) is scheduled for 2.6.37, I was wondering what would be the right time frame for submitting a patch which does that. Does the x86-tip tree have any next branch where we can park this patch ? Below is the patch for your reference which just removes VMI specific bits, applies on top of x86-tip. There is also an opportunity to

Hi Peter, Removal of VMI(VMware's para-virtualization technique) is scheduled for 2.6.37, I was wondering what would be the right time frame for submitting a patch which does that. Does the x86-tip tree have any next branch where we can park this patch ? Below is the patch for your reference which just removes VMI specific bits, applies on top of x86-tip. There is also an opportunity to

So there is a logic error that would prevent us from ever using NOP = relocations, thus stopping any unnecessary callouts into a VMI ROM. It = doesn't affect us so much, but could conceivably affect open source = implementations of a VMI ROM in the future. It is not absolutely = critical, but it would be extremely nice to get it fixed in 2.6.21 so = there are no broken older kernels

So there is a logic error that would prevent us from ever using NOP = relocations, thus stopping any unnecessary callouts into a VMI ROM. It = doesn't affect us so much, but could conceivably affect open source = implementations of a VMI ROM in the future. It is not absolutely = critical, but it would be extremely nice to get it fixed in 2.6.21 so = there are no broken older kernels

Add a /proc node for the VMI sub-arch, which gives information on the VMI ROM detected using /proc/vmi/info and a list of kernel annotations in /proc/vmi/annotations. The timing information is VMware specific, and should probably be put into a separate /proc node (and a separate patch for our internal use). Signed-off-by: Zachary Amsden <zach@vmware.com> Index:

Add a /proc node for the VMI sub-arch, which gives information on the VMI ROM detected using /proc/vmi/info and a list of kernel annotations in /proc/vmi/annotations. The timing information is VMware specific, and should probably be put into a separate /proc node (and a separate patch for our internal use). Signed-off-by: Zachary Amsden <zach@vmware.com> Index:

In paravirt builds with VMI compiled in, vmi_bringup is called unconditionally, not via a paravirt-ops table (as no other hypervisor uses the APIC startup technique). Make the calls to setup VMI state conditional on the presence of the VMI ROM. Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 1915e2685a3c arch/i386/kernel/vmi.c --- a/arch/i386/kernel/vmi.c Thu Jan 04 15:56:40 2007

In paravirt builds with VMI compiled in, vmi_bringup is called unconditionally, not via a paravirt-ops table (as no other hypervisor uses the APIC startup technique). Make the calls to setup VMI state conditional on the presence of the VMI ROM. Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 1915e2685a3c arch/i386/kernel/vmi.c --- a/arch/i386/kernel/vmi.c Thu Jan 04 15:56:40 2007

Move APIC read / write accessors to sub-arch layer. Note that we don't bother to implement apic_write_atomic any different, as it is only present to work around old processor erratums (Pentium Processor Spec update 11AP), and VMI kernels do not offer support for this class of processor. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Daniel Arai <arai@vmware.com>

Move APIC read / write accessors to sub-arch layer. Note that we don't bother to implement apic_write_atomic any different, as it is only present to work around old processor erratums (Pentium Processor Spec update 11AP), and VMI kernels do not offer support for this class of processor. Signed-off-by: Zachary Amsden <zach@vmware.com> Signed-off-by: Daniel Arai <arai@vmware.com>

Use para_fill instead of directly setting the APIC ops to the result of the vmi_get_function call - this allows one to implement a VMI ROM without implementing APIC functions, just using the native APIC functions. While doing this, I realized that there is a lot more cleanup that should have been done. Basically, we should never assume that the ROM implements a specific set of functions, and

Use para_fill instead of directly setting the APIC ops to the result of the vmi_get_function call - this allows one to implement a VMI ROM without implementing APIC functions, just using the native APIC functions. While doing this, I realized that there is a lot more cleanup that should have been done. Basically, we should never assume that the ROM implements a specific set of functions, and

Implement vmi_kmap_atomic_pte in terms of the backend set_linear_mapping operation. The conversion is rather straighforward; call kmap_atomic and then inform the hypervisor of the page mapping. The _flush_tlb damage is due to macros being pulled in from highmem.h. Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 2207a31829e7 arch/i386/kernel/vmi.c --- a/arch/i386/kernel/vmi.c Mon

Implement vmi_kmap_atomic_pte in terms of the backend set_linear_mapping operation. The conversion is rather straighforward; call kmap_atomic and then inform the hypervisor of the page mapping. The _flush_tlb damage is due to macros being pulled in from highmem.h. Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 2207a31829e7 arch/i386/kernel/vmi.c --- a/arch/i386/kernel/vmi.c Mon

Hi, We ran a few experiments to compare performance of VMware's paravirtualization technique (VMI) and hardware MMU technologies (HWMMU) on VMware's hypervisor. To give some background, VMI is VMware's paravirtualization specification which tries to optimize CPU and MMU operations of the guest operating system. For more information take a look at this

Hi, We ran a few experiments to compare performance of VMware's paravirtualization technique (VMI) and hardware MMU technologies (HWMMU) on VMware's hypervisor. To give some background, VMI is VMware's paravirtualization specification which tries to optimize CPU and MMU operations of the guest operating system. For more information take a look at this

Now that the VDSO can be relocated, we can support it in VMI configurations. Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 158d9ffb46fe arch/i386/Kconfig --- a/arch/i386/Kconfig Thu Mar 29 04:17:05 2007 -0700 +++ b/arch/i386/Kconfig Thu Mar 29 04:18:05 2007 -0700 @@ -220,7 +220,7 @@ config PARAVIRT config VMI bool "VMI Paravirt-ops support" - depends on PARAVIRT

The variable no_timer_check does not exist in UP builds; don't try to set it in the vmi init code. Signed-off-by: Zachary Amsden <zach@vmware.com> diff -r 21d7686ee318 arch/i386/kernel/vmi.c --- a/arch/i386/kernel/vmi.c Thu Jan 04 15:23:30 2007 -0800 +++ b/arch/i386/kernel/vmi.c Thu Jan 04 15:55:39 2007 -0800 @@ -913,7 +913,9 @@ void __init vmi_init(void) local_irq_save(flags);