Messages in this thread | | | From | Andy Lutomirski <> | Date | Fri, 17 Jun 2016 15:41:49 -0700 | Subject | [off-list] a path toward killing thread_info |
| |
https://git.kernel.org/cgit/linux/kernel/git/luto/linux.git/commit/?h=x86/vmap_stack&id=50d6cef284e80678c2065813b54bf525d1202d0f
It's fairly straightforward, it's arguably a cleanup, and, with it applied, there are very few references to 'thread_info' left in the core kernel at all.
PeterZ, I'm thinking of adding task_ti_flags_ptr to directly find the ti flags word given a task_struct * so the scheduler can use it. Does that seem reasonable to you?
Ingo, lockdep tracks mutex owners by thread_info *. Is there any good reason for this? Can I just use task_struct *? If we do that, I think thread_info will be *gone* from the core.
--Andy
-- Andy Lutomirski AMA Capital Management, LLC
| |