itimer_delete() uses spin_lock_irqsave() to obtain a `flags' variable
which can then be passed to unlock_timer(). It uses already spin_lock
locking for the structure instead of lock_timer() because it has a timer
which can not be removed by others at this point. The cleanup is always
performed with
Small cleanup / optimisation / clarification in itimer_delete() which I
noticed while doing other things…
Sebastian
-off-by: Kees Cook
Signed-off-by: Shuah Khan
Signed-off-by: Sasha Levin
---
tools/testing/selftests/timers/adjtick.c| 1 +
tools/testing/selftests/timers/leapcrash.c | 1 +
tools/testing/selftests/timers/mqueue-lat.c | 1 +
tools/testing/selftests/timers/nanosleep.c | 1
On 18/06/2019 21:18, Anna Schumaker wrote:
>
> On Tue, 2019-06-18 at 10:35 +0100, Jon Hunter wrote:
>> Trond, Anna,
>>
>> On 12/06/2019 15:23, Jon Hunter wrote:
>>> On 05/06/2019 23:01, Trond Myklebust wrote:
>>>
>>> ...
>>>
I'd be OK with just reverting this patch if it is causing a
p
This series adds missing generic 3-cells PWM to STM32 timers dt-bindings,
PWM driver, and the relevant dtsi files for STM32F4, STM32F7 and STM32MP1.
Fabrice Gasnier (5):
dt-bindings: pwm-stm32: add #pwm-cells
pwm: stm32: use 3 cells ->of_xlate()
ARM: dts: stm32: add pwm cells to stm32mp1
On Tue, 2019-06-18 at 10:35 +0100, Jon Hunter wrote:
> Trond, Anna,
>
> On 12/06/2019 15:23, Jon Hunter wrote:
> > On 05/06/2019 23:01, Trond Myklebust wrote:
> >
> > ...
> >
> > > I'd be OK with just reverting this patch if it is causing a
> > > performance
> > > issue.
> > >
> > > Anna?
> >
yd
Signed-off-by: Miroslav Lichvar
---
tools/testing/selftests/timers/freq-step.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/tools/testing/selftests/timers/freq-step.c
b/tools/testing/selftests/timers/freq-step.c
index 8cd10662ffba..4b76450d78d1 100644
--- a/too
Trond, Anna,
On 12/06/2019 15:23, Jon Hunter wrote:
>
> On 05/06/2019 23:01, Trond Myklebust wrote:
>
> ...
>
>> I'd be OK with just reverting this patch if it is causing a performance
>> issue.
>>
>> Anna?
>
> Any update on this?
I have not seen any update on this. Do you plan to revert this
fied from a remote CPU, then the only way
> > > right now is to dequeue and requeue it with add_timer_on().
> >
> > Indeed. If add_timer_on() should always be used when with pinned
> > timers, IMHO it would be good to comment probably above TIMER_PINNED
> > about t
-off-by: Kees Cook
Signed-off-by: Shuah Khan
Signed-off-by: Sasha Levin
---
tools/testing/selftests/timers/adjtick.c| 1 +
tools/testing/selftests/timers/leapcrash.c | 1 +
tools/testing/selftests/timers/mqueue-lat.c | 1 +
tools/testing/selftests/timers/nanosleep.c | 1
-off-by: Kees Cook
Signed-off-by: Shuah Khan
Signed-off-by: Sasha Levin
---
tools/testing/selftests/timers/adjtick.c| 1 +
tools/testing/selftests/timers/leapcrash.c | 1 +
tools/testing/selftests/timers/mqueue-lat.c | 1 +
tools/testing/selftests/timers/nanosleep.c | 1
-off-by: Kees Cook
Signed-off-by: Shuah Khan
Signed-off-by: Sasha Levin
---
tools/testing/selftests/timers/adjtick.c| 1 +
tools/testing/selftests/timers/leapcrash.c | 1 +
tools/testing/selftests/timers/mqueue-lat.c | 1 +
tools/testing/selftests/timers/nanosleep.c | 1
x27;t push cfs_bandwith slack timers forward
When a cfs_rq sleeps and returns its quota, we delay for 5ms before
waking any throttled cfs_rqs to coalesce with other cfs_rqs going to
sleep, as this has to be done outside of the rq lock we hold.
The current code waits for 5ms without any sleeps, inste
>
> Indeed. If add_timer_on() should always be used when with pinned
> timers, IMHO it would be good to comment probably above TIMER_PINNED
> about the fact so people will never misuse the interfaces (it seems to
> be mis-used somehow but I cannot be 100% sure, please see below
ase, unsigned
> > tflags)
> > !(tflags & TIMER_PINNED))
> > return get_timer_cpu_base(tflags, get_nohz_timer_target());
> > #endif
> > - return get_timer_this_cpu_base(tflags);
> > + return base;
> > }
>
> Timers a
me/timer.c
> +++ b/kernel/time/timer.c
> @@ -868,7 +868,7 @@ get_target_base(struct timer_base *base, unsigned tflags)
> !(tflags & TIMER_PINNED))
> return get_timer_cpu_base(tflags, get_nohz_timer_target());
> #endif
> - return get_timer_this_cpu_base
On Mon, Jun 03, 2019 at 09:29:44PM +0800, Peter Xu wrote:
> get_target_base() in the timer code is not using the "base" parameter
> at all. My gut feeling is that instead of removing that extra
> parameter, what we really want to do is "return the old base if it
> does not suite for a new one".
P
On 6/14/19 2:42 PM, Thomas Gleixner wrote:
> On Wed, 12 Jun 2019, Dmitry Safonov wrote:
>
>> Subject: posix-timers/timens: Take into account clock offsets
>
> Please avoid that '/timens' appendix. It's not really a new subsystem or
> subfunction of posix
On Wed, 12 Jun 2019, Dmitry Safonov wrote:
> Subject: posix-timers/timens: Take into account clock offsets
Please avoid that '/timens' appendix. It's not really a new subsystem or
subfunction of posix-timers.
posix-timers: Add time namespace support to common_timer_set()
&g
From: Andrei Vagin
Wire timer_settime() syscall into time namespace virtualization.
Signed-off-by: Andrei Vagin
Co-developed-by: Dmitry Safonov
Signed-off-by: Dmitry Safonov
---
kernel/time/posix-timers.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/kernel/time/posix-timers.c b/kern
On 05/06/2019 23:01, Trond Myklebust wrote:
...
> I'd be OK with just reverting this patch if it is causing a performance
> issue.
>
> Anna?
Any update on this?
Thanks
Jon
--
nvpublic
Peter Zijlstra writes:
> On Thu, Jun 06, 2019 at 10:21:01AM -0700, bseg...@google.com wrote:
>> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
>> index efa686eeff26..60219acda94b 100644
>> --- a/kernel/sched/sched.h
>> +++ b/kernel/sched/sched.h
>> @@ -356,6 +356,7 @@ struct cfs_bandwid
On Tue, Jun 11, 2019 at 04:24:43PM +0200 Peter Zijlstra wrote:
> On Tue, Jun 11, 2019 at 10:12:19AM -0400, Phil Auld wrote:
>
> > That looks reasonable to me.
> >
> > Out of curiosity, why not bool? Is sizeof bool architecture dependent?
>
> Yeah, sizeof(_Bool) is unspecified and depends on ABI
On Tue, Jun 11, 2019 at 10:12:19AM -0400, Phil Auld wrote:
> That looks reasonable to me.
>
> Out of curiosity, why not bool? Is sizeof bool architecture dependent?
Yeah, sizeof(_Bool) is unspecified and depends on ABI. It is mostly 1,
but there are known cases where it is 4.
On Tue, Jun 11, 2019 at 03:53:25PM +0200 Peter Zijlstra wrote:
> On Thu, Jun 06, 2019 at 10:21:01AM -0700, bseg...@google.com wrote:
> > diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> > index efa686eeff26..60219acda94b 100644
> > --- a/kernel/sched/sched.h
> > +++ b/kernel/sched/sched.h
On Thu, Jun 06, 2019 at 10:21:01AM -0700, bseg...@google.com wrote:
> diff --git a/kernel/sched/sched.h b/kernel/sched/sched.h
> index efa686eeff26..60219acda94b 100644
> --- a/kernel/sched/sched.h
> +++ b/kernel/sched/sched.h
> @@ -356,6 +356,7 @@ struct cfs_bandwidth {
> u64
On Tue, Jun 11, 2019 at 09:04:17AM -0400, Phil Auld wrote:
> On Thu, Jun 06, 2019 at 10:21:01AM -0700 bseg...@google.com wrote:
> > When a cfs_rq sleeps and returns its quota, we delay for 5ms before
> > waking any throttled cfs_rqs to coalesce with other cfs_rqs going to
> > sleep, as this has to
On Thu, Jun 06, 2019 at 10:21:01AM -0700 bseg...@google.com wrote:
> When a cfs_rq sleeps and returns its quota, we delay for 5ms before
> waking any throttled cfs_rqs to coalesce with other cfs_rqs going to
> sleep, as this has to be done outside of the rq lock we hold.
>
> The current code waits
ruct timer_list *timer)
{
- if (!is_timers_nohz_active())
- return;
-
- /*
-* TODO: This wants some optimizing similar to the code below, but we
-* will do that when we switch from push to pull for deferrable timers.
-*/
- if (timer->
f it's not a housekeeping cpu (because
get_nohz_timer_target() will always try to provision timers onto the
housekeeping ones), or did I misunderstand your comment?
#if defined(CONFIG_SMP) && defined(CONFIG_NO_HZ_COMMON)
if (static_branch_likely(&timers_migration_enabled) &
When a cfs_rq sleeps and returns its quota, we delay for 5ms before
waking any throttled cfs_rqs to coalesce with other cfs_rqs going to
sleep, as this has to be done outside of the rq lock we hold.
The current code waits for 5ms without any sleeps, instead of waiting
for 5ms from the first sleep,
On Mon, Jun 03, 2019 at 09:29:44PM +0800, Peter Xu wrote:
> get_target_base() in the timer code is not using the "base" parameter
> at all. My gut feeling is that instead of removing that extra
> parameter, what we really want to do is "return the old base if it
> does not suite for a new one".
H
On Tue, Jun 04, 2019 at 02:29:31PM +0800, Peter Xu wrote:
> On Mon, Apr 15, 2019 at 05:12:15PM -0300, Marcelo Tosatti wrote:
> > Check base->pending_map locklessly and skip raising timer softirq
> > if empty.
> >
> > What allows the lockless (and potentially racy against mod_timer)
> > check is
On 2019/6/6 AM 4:06, bseg...@google.com wrote:
> When a cfs_rq sleeps and returns its quota, we delay for 5ms before
> waking any throttled cfs_rqs to coalesce with other cfs_rqs going to
> sleep, as this has has to be done outside of the rq lock we hold.
two "has".
>
> The current code waits fo
("SUNRPC: Declare RPC
> timers as TIMER_DEFERRABLE") and reverting this on top of v5.2-rc3
> does
> appear to resolve the problem.
>
> The cause of the suspend failure appears to be a long delay observed
> sometimes when resuming from suspend, and this is causing our test t
Hi Trond,
I have been noticing intermittent failures with a system suspend test on
some of our machines that have a NFS mounted root file-system. Bisecting
this issue points to your commit 431235818bc3 ("SUNRPC: Declare RPC
timers as TIMER_DEFERRABLE") and reverting this on top of v5.
can enjoy.
Signed-off-by: Kees Cook
Signed-off-by: Shuah Khan
Signed-off-by: Sasha Levin
---
tools/testing/selftests/timers/adjtick.c| 1 +
tools/testing/selftests/timers/leapcrash.c | 1 +
tools/testing/selftests/timers/mqueue-lat.c | 1 +
tools/testing/selftests/timers
can enjoy.
Signed-off-by: Kees Cook
Signed-off-by: Shuah Khan
Signed-off-by: Sasha Levin
---
tools/testing/selftests/timers/adjtick.c| 1 +
tools/testing/selftests/timers/leapcrash.c | 1 +
tools/testing/selftests/timers/mqueue-lat.c | 1 +
tools/testing/selftests/timers
On Mon, Apr 15, 2019 at 05:12:15PM -0300, Marcelo Tosatti wrote:
> Check base->pending_map locklessly and skip raising timer softirq
> if empty.
>
> What allows the lockless (and potentially racy against mod_timer)
> check is that mod_timer will raise another timer softirq after
> modifying base
On Mon, Jun 03, 2019 at 09:29:44PM +0800, Peter Xu wrote:
> get_target_base() in the timer code is not using the "base" parameter
> at all. My gut feeling is that instead of removing that extra
> parameter, what we really want to do is "return the old base if it
> does not suite for a new one".
I
Assign TMR1-4 per-CPU core on 32bit Tegra's in a way it is done for
Tegra210. In a result each core can handle its own timer events, less
code is unique to ARM64 and Tegra's clock events driver now has higher
rating on all Tegra's, replacing the ARM's TWD timer which isn't very
accurate due to the
get_target_base() in the timer code is not using the "base" parameter
at all. My gut feeling is that instead of removing that extra
parameter, what we really want to do is "return the old base if it
does not suite for a new one".
CC: Thomas Gleixner
CC: John Stultz
CC: Stephen Boyd
CC: Luiz Ca
t; +
> > > +#ifdef CONFIG_PREEMPT_RT_FULL
> > > +/* On RT, irq work runs from softirq */
> > > + if (irq_work_needs_cpu())
> > > + goto raise;
> >
> > So with this patch and the change you made in the patch before, timers on
> > RT are expired only w
Hi Anna-Maria,
On Wed, May 29, 2019 at 04:53:05PM +0200, Anna-Maria Gleixner wrote:
> On Mon, 15 Apr 2019, Marcelo Tosatti wrote:
>
> [...]
>
> > The patch "timers: do not raise softirq unconditionally" from Thomas
> > attempts to address that by checki
15 14:22:56.755047354
> > -0300
> > @@ -1776,6 +1776,24 @@
> > if (time_before(jiffies, base->clk))
> > return;
> > }
> > +
> > +#ifdef CONFIG_PREEMPT_RT_FULL
> > +/* On RT, irq work runs from softirq */
> >
ase->clk))
> return;
> }
> +
> +#ifdef CONFIG_PREEMPT_RT_FULL
> +/* On RT, irq work runs from softirq */
> + if (irq_work_needs_cpu())
> + goto raise;
So with this patch and the change you made in the patch before, timers on
RT are expire
On Mon, 15 Apr 2019, Marcelo Tosatti wrote:
[...]
> The patch "timers: do not raise softirq unconditionally" from Thomas
> attempts to address that by checking, in the sched tick, whether its
> necessary to raise the timer softirq. Unfortunately, it attempts to grab
>
Assign TMR1-4 per-CPU core on 32bit Tegra's in a way it is done for
Tegra210. In a result each core can handle its own timer events, less
code is unique to ARM64 and Tegra's clock events driver now has higher
rating on all Tegra's, replacing the ARM's TWD timer which isn't very
accurate due to the
When running under a pipe, some timer tests would not report output in
real-time because stdout flushes were missing after printf()s that lacked
a newline. This adds them to restore real-time status output that humans
can enjoy.
Signed-off-by: Kees Cook
---
tools/testing/selftests/timers
The pull request you sent on Mon, 6 May 2019 12:52:12 +0200:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git x86-timers-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/db10ad041b318a07985363e243742a07f4b0f44b
Thank you!
--
Deet-doot-dot, I a
Linus,
Please pull the latest x86-timers-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-timers-for-linus
# HEAD: 81423c37415fe45057d64196ae0ce8e17a9c7148 x86/timer: Don't inline
__const_udelay()
Two changes: an LTO improvement, plus th
Assign TMR1-4 per-CPU core on 32bit Tegra's in a way it is done for
Tegra210. In a result each core can handle its own timer events, less
code is unique to ARM64 and Tegra's clock events driver now has higher
rating on all Tegra's, replacing the ARM's TWD timer which isn't very
accurate due to the
From: luca abeni
commit 1b02cd6a2d7f3e2a6a5262887d2cb2912083e42f upstream.
syzbot reported the following warning:
[ ] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255
task_non_contending+0xae0/0x1950
line 255 of deadline.c is:
WARN_ON(hrtimer_active(&dl_se->inactive_timer
From: luca abeni
commit 1b02cd6a2d7f3e2a6a5262887d2cb2912083e42f upstream.
syzbot reported the following warning:
[ ] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255
task_non_contending+0xae0/0x1950
line 255 of deadline.c is:
WARN_ON(hrtimer_active(&dl_se->inactive_timer
From: luca abeni
commit 1b02cd6a2d7f3e2a6a5262887d2cb2912083e42f upstream.
syzbot reported the following warning:
[ ] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255
task_non_contending+0xae0/0x1950
line 255 of deadline.c is:
WARN_ON(hrtimer_active(&dl_se->inactive_timer
On Thu, 25 Apr 2019, Dmitry Safonov wrote:
> From: Andrei Vagin
>
> Wire timer_settime() syscall into time namespace virtualization.
>
> Signed-off-by: Andrei Vagin
> Signed-off-by: Dmitry Safonov
> ---
> kernel/time/alarmtimer.c | 3 +++
> kernel/time/posix-timers.c | 2 ++
> 2 files chan
From: Andrei Vagin
Wire timer_settime() syscall into time namespace virtualization.
Signed-off-by: Andrei Vagin
Signed-off-by: Dmitry Safonov
---
kernel/time/alarmtimer.c | 3 +++
kernel/time/posix-timers.c | 2 ++
2 files changed, 5 insertions(+)
diff --git a/kernel/time/alarmtimer.c b/ke
Assign TMR1-4 per-CPU core on 32bit Tegra's in a way it is done for
Tegra210. In a result each core can handle its own timer events, less
code is unique to ARM64 and Tegra's clock events driver now has higher
rating on all Tegra's, replacing the ARM's TWD timer which isn't very
accurate due to the
From: Chang-An Chen
commit 3f2552f7e9c5abef2775c53f7af66532f8bf65bc upstream.
tick_freeze() introduced by suspend-to-idle in commit 124cf9117c5f ("PM /
sleep: Make it possible to quiesce timers during suspend-to-idle") uses
timekeeping_suspend() instead of syscore_suspend() during
From: Chang-An Chen
commit 3f2552f7e9c5abef2775c53f7af66532f8bf65bc upstream.
tick_freeze() introduced by suspend-to-idle in commit 124cf9117c5f ("PM /
sleep: Make it possible to quiesce timers during suspend-to-idle") uses
timekeeping_suspend() instead of syscore_suspend() during
Commit-ID: 81423c37415fe45057d64196ae0ce8e17a9c7148
Gitweb: https://git.kernel.org/tip/81423c37415fe45057d64196ae0ce8e17a9c7148
Author: Andi Kleen
AuthorDate: Fri, 29 Mar 2019 17:47:38 -0700
Committer: Thomas Gleixner
CommitDate: Fri, 19 Apr 2019 17:49:47 +0200
x86/timer: Don't inline
Commit-ID: 3f2552f7e9c5abef2775c53f7af66532f8bf65bc
Gitweb: https://git.kernel.org/tip/3f2552f7e9c5abef2775c53f7af66532f8bf65bc
Author: Chang-An Chen
AuthorDate: Fri, 29 Mar 2019 10:59:09 +0800
Committer: Thomas Gleixner
CommitDate: Thu, 18 Apr 2019 14:34:53 +0200
timers/sched_clock
handle active 0-lag timers
syzbot reported the following warning:
[ ] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255
task_non_contending+0xae0/0x1950
line 255 of deadline.c is:
WARN_ON(hrtimer_active(&dl_se->inactive_timer));
in task_non_contending().
Unfortunat
Condense the pending bitmap information in a bool.
Improves cyclictest results by 4us.
Signed-off-by: Marcelo Tosatti
---
kernel/time/timer.c |9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
Index: linux-rt-devel/kernel/time/timer.c
===
For isolated CPUs, we'd like to skip awakening ktimersoftd
(the switch to and then back from ktimersoftd takes 10us in
virtualized environments, in addition to other OS overhead,
which exceeds telco requirements for packet forwarding for
5G) from the sched tick.
The patch "timers: do
Check base->pending_map locklessly and skip raising timer softirq
if empty.
What allows the lockless (and potentially racy against mod_timer)
check is that mod_timer will raise another timer softirq after
modifying base->pending_map.
Signed-off-by: Marcelo Tosatti
---
kernel/time/timer.c |
On Thu, Mar 21, 2019 at 01:09:17PM +0100, Anna-Maria Gleixner wrote:
> Hi,
>
> the patch series was developed during investigating timer problems and
> timer improvements. It contains a struct documentation fix in tick-sched
> and a fixes as well as an improvement for timer tracing.
>
> Thanks,
>
Andreas Koensgen
Signed-off-by: David S. Miller
[bwh: Backported to 3.16: Move initialisation of resync_t.data and
resync_t.function to sixpack_open(), as done by upstream commit
8e763de0b91d "net/hamradio/6pack: Convert timers to use timer_setup()".]
Signed-off-by: Ben Hutchings
---
Hi,
On 25/03/19 14:15, luca abeni wrote:
> syzbot reported the following warning:
> [ 948.126369] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255
> task_non_contending+0xae0/0x1950
> [ 948.130198] Kernel panic - not syncing: panic_on_warn set ...
> [ 948.130198]
> [ 948.134221] CPU:
syzbot reported the following warning:
[ 948.126369] WARNING: CPU: 4 PID: 17089 at kernel/sched/deadline.c:255
task_non_contending+0xae0/0x1950
[ 948.130198] Kernel panic - not syncing: panic_on_warn set ...
[ 948.130198]
[ 948.134221] CPU: 4 PID: 17089 Comm: syz-executor.1 Not tainted 4.19.27
The pull request you sent on Sun, 24 Mar 2019 14:12:21 -:
> git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> timers-urgent-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a75eda7bce5e8ffdebe6ddfe513b31e5ec3527d2
Thank you!
--
Deet-do
Linus,
please pull the latest timers-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
timers-urgent-for-linus
A set of small fixes plus the removal of stale board support code:
- Remove the board support code from the clpx711x clocksource
Commit-ID: 0f0b7e1cc7abf8e1a8b301f2868379d611d05ae2
Gitweb: https://git.kernel.org/tip/0f0b7e1cc7abf8e1a8b301f2868379d611d05ae2
Author: Juri Lelli
AuthorDate: Thu, 7 Mar 2019 13:09:13 +0100
Committer: Thomas Gleixner
CommitDate: Fri, 22 Mar 2019 14:14:58 +0100
x86/tsc: Add option to di
Hi,
the patch series was developed during investigating timer problems and
timer improvements. It contains a struct documentation fix in tick-sched
and a fixes as well as an improvement for timer tracing.
Thanks,
Anna-Maria
Anna-Maria Gleixner (4):
tick-sched: Update tick_sched struc
gt;
> tools/testing/selftests/timers/skew_consistency.c | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/tools/testing/selftests/timers/skew_consistency.c
> b/tools/testing/selftests/timers/skew_consistency.c
> index 022b711..8066be9 100644
> --- a/tools/testing/selfte
-O2 -pipe -g -feliminate-unused-debug-types -O3 -Wl,-no-as-needed -Wall
-DKTEST -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lrt -lpthread
posix_timers.c
-o
/build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers
/tmp
-O2 -pipe -g -feliminate-unused-debug-types -O3 -Wl,-no-as-needed -Wall
-DKTEST -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lrt -lpthread
posix_timers.c
-o
/build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers
/tmp
-O2 -pipe -g -feliminate-unused-debug-types -O3 -Wl,-no-as-needed -Wall
-DKTEST -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lrt -lpthread
posix_timers.c
-o
/build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers
/tmp
On 2019/3/6 18:38, Arnd Bergmann wrote:
> On Wed, Mar 6, 2019 at 9:41 AM Xiongfeng Wang
> wrote:
>>
>>
>> diff --git a/kernel/time/posix-timers.c b/kernel/time/posix-timers.c
>> index 0e84bb7..4b57566 100644
>> --- a/kernel/time/posix-timers.c
>> +++ b/kernel/time/posix-timers.c
>> @@ -856,6 +
From: Sabyasachi Gupta
Remove duplicate header which is included twice.
Signed-off-by: Sabyasachi Gupta
Signed-off-by: Souptick Joarder
---
v2: Corrected format.
tools/testing/selftests/timers/skew_consistency.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests
On Wed, Mar 6, 2019 at 9:41 AM Xiongfeng Wang wrote:
>
>
> diff --git a/kernel/time/posix-timers.c b/kernel/time/posix-timers.c
> index 0e84bb7..4b57566 100644
> --- a/kernel/time/posix-timers.c
> +++ b/kernel/time/posix-timers.c
> @@ -856,6 +856,10 @@ static int do_timer_settime(timer_t timer_id,
When I ran Syzkaller testsuite, I got the following call trace.
UBSAN: Undefined behaviour in ./include/linux/time64.h:120:27
signed integer overflow:
8243129037239968815 * 10 cannot be represented in type 'lon
Remove duplicate header which is included twice.
Signed-off-by: Sabyasachi Gupta
Signed-off-by: Souptick Joarder
---
tools/testing/selftests/timers/skew_consistency.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/tools/testing/selftests/timers/skew_consistency.c
b/tools/testing/selftests
On Thu, Feb 28, 2019 at 11:35 AM Thomas Gleixner wrote:
> On Thu, 28 Feb 2019, Arnd Bergmann wrote:
> > On Thu, Feb 28, 2019 at 5:25 AM Deepa Dinamani
> > wrote:
> > >
> > > On Tue, Feb 26, 2019 at 11:52 PM Xiongfeng Wang
> > > wrote:
> > I think returning EINVAL here is better than silently tr
On Thu, 28 Feb 2019, Arnd Bergmann wrote:
> On Thu, Feb 28, 2019 at 5:25 AM Deepa Dinamani wrote:
> >
> > On Tue, Feb 26, 2019 at 11:52 PM Xiongfeng Wang
> > wrote:
> > >
> > > +++ b/kernel/time/posix-timers.c
> > > @@ -853,8 +853,8 @@ static int do_timer_settime(timer_t timer_id, int
> > > flag
On Thu, Feb 28, 2019 at 5:25 AM Deepa Dinamani wrote:
>
> On Tue, Feb 26, 2019 at 11:52 PM Xiongfeng Wang
> wrote:
> >
> > +++ b/kernel/time/posix-timers.c
> > @@ -853,8 +853,8 @@ static int do_timer_settime(timer_t timer_id, int flags,
> > unsigned long flag;
> > int error = 0;
>
On Tue, Feb 26, 2019 at 11:52 PM Xiongfeng Wang
wrote:
>
> When I ran Syzkaller testsuite, I got the following call trace.
>
> UBSAN: Undefined behaviour in ./include/linux/time64.h:120:27
> signed integer overflow:
>
When I ran Syzkaller testsuite, I got the following call trace.
UBSAN: Undefined behaviour in ./include/linux/time64.h:120:27
signed integer overflow:
8243129037239968815 * 10 cannot be represented in type 'lon
On 2019/2/27 10:38, Deepa Dinamani wrote:
> On Tue, Feb 26, 2019 at 6:07 PM Xiongfeng Wang
> wrote:
>>
>> When I ran Syzkaller testsuite, I got the following call trace.
>>
>> UBSAN: Undefined behaviour in ./includ
On Tue, Feb 26, 2019 at 6:07 PM Xiongfeng Wang
wrote:
>
> When I ran Syzkaller testsuite, I got the following call trace.
>
> UBSAN: Undefined behaviour in ./include/linux/time64.h:120:27
> signed integer overflow:
>
When I ran Syzkaller testsuite, I got the following call trace.
UBSAN: Undefined behaviour in ./include/linux/time64.h:120:27
signed integer overflow:
8243129037239968815 * 10 cannot be represented in type 'lon
cmd timer or
qfull timer. For some corner cases the timers are always working only for
the ringbuffer's and full queue's newest cmd. That's to say the timer won't
be fired even if one cmd has been stuck for a very long time and the
deadline is reached.
This fix will keep the cm
cmd timer or
qfull timer. For some corner cases the timers are always working only for
the ringbuffer's and full queue's newest cmd. That's to say the timer won't
be fired even if one cmd has been stuck for a very long time and the
deadline is reached.
This fix will keep the cm
-DKTEST -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lrt -lpthread
posix_timers.c
-o
/build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers
/tmp/cc1FTZzT.o: In function `check_timer_create':
/usr/src/debug/kselftests/4.
-DKTEST -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lrt -lpthread
posix_timers.c
-o
/build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers
/tmp/cc1FTZzT.o: In function `check_timer_create':
/usr/src/debug/kselftests/4.
-DKTEST -Wl,-O1 -Wl,--hash-style=gnu -Wl,--as-needed -lrt -lpthread
posix_timers.c
-o
/build/tmp-rpb-glibc/work/hikey-linaro-linux/kselftests/4.12-r0/linux-4.12-rc7/tools/testing/selftests/timers/posix_timers
/tmp/cc1FTZzT.o: In function `check_timer_create':
/usr/src/debug/kselftests/4.
If the guest has offloaded the timer virq, handle the following
hypercalls for programming the timer:
VCPUOP_set_singleshot_timer
VCPUOP_stop_singleshot_timer
set_timer_op(timestamp_ns)
The event channel corresponding to the timer virq is then used to inject
events once timer deadline
From: Xiubo Li
[ Upstream commit a94a2572b97744d3a35a1996df0e5cf6b2461a4a ]
Currently there is one cmd timeout timer and one qfull timer for each udev,
and whenever any new command is coming in we will update the cmd timer or
qfull timer. For some corner cases the timers are always working only
From: Xiubo Li
[ Upstream commit a94a2572b97744d3a35a1996df0e5cf6b2461a4a ]
Currently there is one cmd timeout timer and one qfull timer for each udev,
and whenever any new command is coming in we will update the cmd timer or
qfull timer. For some corner cases the timers are always working only
On Thu, Feb 7, 2019 at 7:43 AM Eric W. Biederman wrote:
>
>
> Dmitry,
>
> Can you please verify the follow two patches. The first one is a
> simplification of the one you have already tested and makes the
> processes killable. The second patch improves our heuristic for
> detecting synchronous l
901 - 1000 of 3562 matches
Mail list logo
