Messages in this thread | | | Date | Thu, 29 Mar 2012 13:11:25 -0700 | Subject | Re: [PATCH] percpu: use KERN_CONT in pcpu_dump_alloc_info() | From | Tejun Heo <> |
| |
Hello,
On Thu, Mar 29, 2012 at 1:06 PM, Joe Perches <joe@perches.com> wrote: > It'd be just for avoidance of any other possible > interleaving from other threads. > > It's an __init function so that's not too likely, > but if it every happens...
Ah, okay. Forgot about that. Yeah, the kernel is single threaded at that point, so it shouldn't matter. The code is rather complex so something simpler would be nice, I agree.
Another thing is that we seem to have structured logging coming our way and maybe userspace can deal with racing continuing printks? Not sure how different streams could be distinguished tho. Maybe the printing task can be used to group them? Kay, is this something structured logging would solve?
Thanks.
-- tejun
| |