Re: [patch V2 28/38] posix-cpu-timers: Restructure expiry array

2019-08-26 Thread Thomas Gleixner
On Mon, 26 Aug 2019, Frederic Weisbecker wrote: > On Wed, Aug 21, 2019 at 09:09:15PM +0200, Thomas Gleixner wrote: > > @@ -884,7 +888,7 @@ static void check_process_timers(struct > > struct list_head *firing) > > { > > struct signal_struct *const sig = tsk->signal;

Re: [patch V2 28/38] posix-cpu-timers: Restructure expiry array

2019-08-26 Thread Frederic Weisbecker
On Wed, Aug 21, 2019 at 09:09:15PM +0200, Thomas Gleixner wrote: > @@ -884,7 +888,7 @@ static void check_process_timers(struct >struct list_head *firing) > { > struct signal_struct *const sig = tsk->signal; > - struct list_head *timers = sig->posix_cputime

Re: [patch V2 28/38] posix-cpu-timers: Restructure expiry array

2019-08-26 Thread Thomas Gleixner
On Mon, 26 Aug 2019, Frederic Weisbecker wrote: > On Wed, Aug 21, 2019 at 09:09:15PM +0200, Thomas Gleixner wrote: > > /** > > - * task_cputimers_expired - Compare two task_cputime entities. > > + * task_cputimers_expired - Check whether posix CPU timers are expired > > * > > * @samples:

Re: [patch V2 28/38] posix-cpu-timers: Restructure expiry array

2019-08-26 Thread Frederic Weisbecker
On Wed, Aug 21, 2019 at 09:09:15PM +0200, Thomas Gleixner wrote: > /** > - * task_cputimers_expired - Compare two task_cputime entities. > + * task_cputimers_expired - Check whether posix CPU timers are expired > * > * @samples: Array of current samples for the CPUCLOCK clocks > - * @expiries:

[patch V2 28/38] posix-cpu-timers: Restructure expiry array

2019-08-21 Thread Thomas Gleixner
Now that the abused struct task_cputime is gone, it's more natural to bundle the expiry cache and the list head of each clock into a struct and have an array of those structs. Follow the hrtimer naming convention of 'bases' and rename the expiry cache to 'nextevt' and adapt all usage sites. Gener