Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1447051

Re: Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8?

Show all headers | View raw

* Andy Lutomirski <luto@kernel.org> wrote:

> Cons: It's a bit odd to merge code that can't be enabled as-is.  OTOH
> x86 could plausibly enable it for 4.8 if Ingo is okay with applying
> "x86/dumpstack: Pin the target stack in save_stack_trace_tsk()" and
> "x86: Move thread_info into task_struct" during the merge window after
> the -mm patchbomb lands.

There's quite a few risky stuff piled up already so I'd prefer if we delayed these 
core bits and the enablement to v4.9.

We can carry these core bits in -tip as well, can create a tip:sched/thread_info 
tree for it and such. I'd prefer that because this way we have natural proximity 
between patch application, testing and eventual fixes.

Then we can expose -next to all these changes as a single, bisectable group of 
commits and, should anything overly catastrophic happen, remove it and regroup our 
forces.

This would really be the best approach I think, since I'd like to default-enable 
all this on x86 from the very beginning.

Thanks,

	Ingo

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

Thread

Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8? Andy Lutomirski <luto@kernel.org> - 2016-07-19 01:50 +0200
  Re: Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8? Christian Borntraeger <borntraeger@de.ibm.com> - 2016-07-19 10:30 +0200
    Re: Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8? Heiko Carstens <heiko.carstens@de.ibm.com> - 2016-07-25 16:30 +0200
  Re: Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8? Mark Rutland <mark.rutland@arm.com> - 2016-07-19 13:30 +0200
  Re: Is THREAD_INFO_IN_TASK appropriate for -mm for 4.8? Ingo Molnar <mingo@kernel.org> - 2016-07-20 09:50 +0200

csiph-web