[off-list] a path toward killing thread_info

From	Andy Lutomirski <luto@amacapital.net>
Newsgroups	linux.kernel
Subject	[off-list] a path toward killing thread_info
Date	2016-06-18 00:50 +0200
Message-ID	<rLaKm-47q-5@gated-at.bofh.it> (permalink)
Organization	linux.* mail to news gateway

Show all headers | View raw

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

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

Thread

[off-list] a path toward killing thread_info Andy Lutomirski <luto@amacapital.net> - 2016-06-18 00:50 +0200
  Re: [off-list] a path toward killing thread_info Al Viro <viro@ZenIV.linux.org.uk> - 2016-06-18 01:10 +0200
    Re: [off-list] a path toward killing thread_info "H. Peter Anvin" <hpa@zytor.com> - 2016-06-18 01:20 +0200
      Re: [off-list] a path toward killing thread_info Benjamin Herrenschmidt <benh@kernel.crashing.org> - 2016-06-18 01:30 +0200
        Re: [off-list] a path toward killing thread_info "H. Peter Anvin" <hpa@zytor.com> - 2016-06-18 02:10 +0200
    Re: [off-list] a path toward killing thread_info Andy Lutomirski <luto@amacapital.net> - 2016-06-18 01:30 +0200

csiph-web