Re: [PATCH 1/8] jump_label: no need to acquire the jump_label_mutex in jump_lable_init()

From
Kevin Hao <hidden>
Date
2015-08-21 03:18:10
Also in
lkml
Reply to
Peter Zijlstra, 2015-08-20
On Thu, Aug 20, 2015 at 08:29:03PM +0200, Peter Zijlstra wrote:
On Thu, Aug 20, 2015 at 08:14:29PM +0800, Kevin Hao wrote:
quoted
The jump_label_init() run in a very early stage, even before the
sched_init(). So there is no chance for concurrent access of the
jump label table.
It also doesn't hurt to have it. Its better to be consistent and
conservative with locking unless there is a pressing need.
Yes, it has no real hurt. IMHO it may cause confusion that the function
jump_label_init() may run in two different thread context simultaneously. 
Anyway if you guys don't think so, I can drop this patch.

Thanks,
Kevin

Attachments

Thread (17 messages) 17 messages, 3 authors, last reply 2015-08-21
Keyboard shortcuts
hback out one level
jnext message in thread / next series-diff position
kprevious message in thread / previous series-diff position
ldrill in
Escclose help / fold thread tree
?toggle this help