Re: [PATCH 0/3] THREAD_INFO_IN_TASK_STRUCT vs generic preemption code

2016-10-13 Thread Andy Lutomirski
On Thu, Oct 13, 2016 at 4:57 AM, Heiko Carstens wrote: > Commit c65eacbe290b ("sched/core: Allow putting thread_info into > task_struct") made struct thread_info a generic struct with only a > single flags member if THREAD_INFO_IN_TASK_STRUCT is selected. > > This

Re: [PATCH 0/3] THREAD_INFO_IN_TASK_STRUCT vs generic preemption code

2016-10-13 Thread Andy Lutomirski
On Thu, Oct 13, 2016 at 4:57 AM, Heiko Carstens wrote: > Commit c65eacbe290b ("sched/core: Allow putting thread_info into > task_struct") made struct thread_info a generic struct with only a > single flags member if THREAD_INFO_IN_TASK_STRUCT is selected. > > This change however seems to be quite

[PATCH 0/3] THREAD_INFO_IN_TASK_STRUCT vs generic preemption code

2016-10-13 Thread Heiko Carstens
Commit c65eacbe290b ("sched/core: Allow putting thread_info into task_struct") made struct thread_info a generic struct with only a single flags member if THREAD_INFO_IN_TASK_STRUCT is selected. This change however seems to be quite x86 centric, since at least the generic preemption code

[PATCH 0/3] THREAD_INFO_IN_TASK_STRUCT vs generic preemption code

2016-10-13 Thread Heiko Carstens
Commit c65eacbe290b ("sched/core: Allow putting thread_info into task_struct") made struct thread_info a generic struct with only a single flags member if THREAD_INFO_IN_TASK_STRUCT is selected. This change however seems to be quite x86 centric, since at least the generic preemption code