[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180212092405.GB25314@hirez.programming.kicks-ass.net>
Date: Mon, 12 Feb 2018 10:24:05 +0100
From: Peter Zijlstra <peterz@...radead.org>
To: Waiman Long <longman@...hat.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Tejun Heo <tj@...nel.org>, Ingo Molnar <mingo@...nel.org>,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] kthread: Export kthread_data()
On Fri, Feb 09, 2018 at 09:52:21AM -0500, Waiman Long wrote:
> When multiple kernel threads are created to cooperatively work on
> a common task, we may need a convenient way to access data that are
> specific to each kthread.
>
> The kthread_data() function fits this need. However, it was not
> visible to kthreads started in a kernel module. To solve this problem,
> the kthread_data() function is now exported allowing kthreads from
> kernel modules to use it.
No. Without an in-tree user, no export.
Powered by blists - more mailing lists