The patch titled
Vmi: initialize fs for smp
has been added to the -mm tree. Its filename is
paravirt-vmi-backend-for-paravirt-ops-initialize-fs-for-smp.patch
See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find
out what to do about this
------------------------------------------------------
Subject: Vmi: initialize fs for smp
From: Zachary Amsden <zach@xxxxxxxxxx>
Now that Jeremy's change to move the kernel PDA to %fs has arrived,
convert the AP processor setup for SMP to use FS instead of GS.
Signed-off-by: Zachary Amsden <zach@xxxxxxxxxx>
Cc: Andi Kleen <ak@xxxxxxx>
Cc: Jeremy Fitzhardinge <jeremy@xxxxxxxxxxxxx>
Cc: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
Cc: Chris Wright <chrisw@xxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxx>
---
arch/i386/kernel/vmi.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -puN arch/i386/kernel/vmi.c~paravirt-vmi-backend-for-paravirt-ops-initialize-fs-for-smp arch/i386/kernel/vmi.c
--- a/arch/i386/kernel/vmi.c~paravirt-vmi-backend-for-paravirt-ops-initialize-fs-for-smp
+++ a/arch/i386/kernel/vmi.c
@@ -518,8 +518,8 @@ vmi_startup_ipi_hook(int phys_apicid, un
ap.ds = __USER_DS;
ap.es = __USER_DS;
- ap.fs = 0;
- ap.gs = __KERNEL_PDA;
+ ap.fs = __KERNEL_PDA;
+ ap.gs = 0;
ap.eflags = 0;
_
Patches currently in -mm which might be from zach@xxxxxxxxxx are
convert-i386-pda-code-to-use-%fs.patch
paravirt-page-allocation-hooks-for-vmi-backend.patch
paravirt-paravirt-cpu-hypercall-batching-mode.patch
paravirt-iopl-handling-for-paravirt-guests.patch
paravirt-smp-boot-hook-for-paravirt.patch
paravirt-vmi-backend-for-paravirt-ops.patch
paravirt-vmi-backend-for-paravirt-ops-compile-fix.patch
paravirt-vmi-backend-for-paravirt-ops-initialize-fs-for-smp.patch
paravirt-vmi-timer-patches.patch
vmi-native-fix.patch
vmi-versus-hrtimers.patch
i386-apic-clean-up-the-apic-code.patch
i386-apic-rework-and-fix-local-apic-calibration.patch
dynticks-i386-prepare-nmi-watchdog.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
