Re: Sysenter crash with Nested Task Bit set

From: Ingo Molnar
Date: Mon Sep 18 2006 - 11:15:35 EST



* Linus Torvalds <torvalds@xxxxxxxx> wrote:

> And sysenter really is very special because of the weak trap
> semantics. Damn. We could either fix it in the sysenter code-path, or
> in the task-switch one, and both of them are timing-critical, but task
> switching perhaps just a tad less so.

agreed. Context-switching is 10 times less frequent on most workloads
than syscalls, so if it takes 10 cycles in the context-switch path to
eliminate a 1 cycle overhead in the syscall-entry path then we are still
break-even on average. In this case the overhead is similar i think, so
the switch_to() fix is preferable.

Ingo
-
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/