Current cpu index is stored at either segment. If userspace sets that segment, kernel will not overwrite it on every reschedule. This is fine as long as user program does not use anything that relies on it :)
Current cpu index is stored at either segment. If userspace sets that segment, kernel will not overwrite it on every reschedule. This is fine as long as user program does not use anything that relies on it :)