diff options
Diffstat (limited to 'arch/i386/xen/enlighten.c')
-rw-r--r-- | arch/i386/xen/enlighten.c | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/arch/i386/xen/enlighten.c b/arch/i386/xen/enlighten.c index 031dc1dcf819..42756771b8eb 100644 --- a/arch/i386/xen/enlighten.c +++ b/arch/i386/xen/enlighten.c | |||
@@ -291,6 +291,18 @@ static void xen_load_tls(struct thread_struct *t, unsigned int cpu) | |||
291 | load_TLS_descriptor(t, cpu, 2); | 291 | load_TLS_descriptor(t, cpu, 2); |
292 | 292 | ||
293 | xen_mc_issue(PARAVIRT_LAZY_CPU); | 293 | xen_mc_issue(PARAVIRT_LAZY_CPU); |
294 | |||
295 | /* | ||
296 | * XXX sleazy hack: If we're being called in a lazy-cpu zone, | ||
297 | * it means we're in a context switch, and %gs has just been | ||
298 | * saved. This means we can zero it out to prevent faults on | ||
299 | * exit from the hypervisor if the next process has no %gs. | ||
300 | * Either way, it has been saved, and the new value will get | ||
301 | * loaded properly. This will go away as soon as Xen has been | ||
302 | * modified to not save/restore %gs for normal hypercalls. | ||
303 | */ | ||
304 | if (xen_get_lazy_mode() == PARAVIRT_LAZY_CPU) | ||
305 | loadsegment(gs, 0); | ||
294 | } | 306 | } |
295 | 307 | ||
296 | static void xen_write_ldt_entry(struct desc_struct *dt, int entrynum, | 308 | static void xen_write_ldt_entry(struct desc_struct *dt, int entrynum, |