Hi Will, On 04/10/2013 07:41 AM, Will Deacon wrote: > On Tue, Apr 09, 2013 at 01:33:34PM +0100, Christopher Covington wrote: >> For accurate accounting pass contextidr_thread_switch the prev >> task pointer, since cpu_switch_to has at that point changed the >> the stack pointer. >> >> Signed-off-by: Christopher Covington <c...@codeaurora.org> > > Thanks Christopher -- I assume that using prev did resolve your issues?
Yes indeed. We're now able to see in simulation that if a userspace process uses 100% CPU, its thread ID, rather than what was usually some random kthread, gets written out most of the time. I donno if that meets your criteria for a "real" use case, but I hope it's at least sufficient testing of the code for now. Thanks, Christopher -- Employee of Qualcomm Innovation Center, Inc. Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by the Linux Foundation. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
