Messages in this thread | | | Date | Fri, 24 Jan 2014 14:34:41 -0500 | Subject | Re: [PATCH V2 4/6] ARM: Make PID_IN_CONTEXTIDR incompatible with PID_NS | From | Adrien Vergé <> |
| |
2014/1/24 Will Deacon <will.deacon@arm.com>: > I think I'd rather have the global ID than disable a potentially useful > feature, especially since this is likely to be consumed by external trace > tools as opposed to user-space tasks.
I understand.
2014/1/24 Christopher Covington <cov@codeaurora.org>: > Would it be reasonable to make what's > written to the CONTEXTIDR run-time configurable? If so, what would be the best > interface for configuring it?
This is an interesting option.
An other option would be to keep the global PID in the Context ID register, and rely on kernel support to translate virtual PID to global PID when needed. Then, it would be possible to select a task to trace via its PID, by asking the kernel to write its global ID to the Context ID comparator.
| |