From: Rob Gardner <rob.gardner@xxxxxxxxxx> Date: Thu, 24 Dec 2015 10:39:05 -0700 > Sorry I should have noted this in the log message, but we > intentionally did not use get_fs() and set_fs() there because they are > not safe to use in a "nested" interrupt context. n.b. get_fs() is not > guaranteed to report a value consistent with %asi while we're > executing the perf interrupt handler, because it may have interrupted > kernel code where %asi is inconsistent with the thread_info current_ds > value. This is common, e.g. right in NGmemcpy. Is that a real problem? The return from trap will restore the %asi register properly from the %tstate register. -- To unsubscribe from this list: send the line "unsubscribe sparclinux" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
