From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Sasha Levin <sasha.levin@oracle.com>,
linux-kernel@vger.kernel.org, pjt@google.com, tglx@linutronix.de,
klamm@yandex-team.ru, bsegall@google.com, hpa@zytor.com
Subject: Re: [tip:timers/core] hrtimer: Allow concurrent hrtimer_start() for self restarting timers
Date: Wed, 13 May 2015 15:54:22 +0200 [thread overview]
Message-ID: <20150513135422.GA24332@gmail.com> (raw)
In-Reply-To: <20150513134311.GW21418@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Tue, May 12, 2015 at 09:52:09AM -0400, Sasha Levin wrote:
> > Hey Peter,
> >
> > I seem to be hitting this warning with the latest -next (2015-05-11):
> >
> > [3344291.055800] WARNING: CPU: 0 PID: 9422 at kernel/time/hrtimer.c:802 hrtimer_forward+0x1f9/0x330()
>
> Indeed.
>
> So I can't seem to come up with a pretty solution :-(
I'm running into this rather frequently as well, in -tip integration
testing, on real hardware, so we need a solution :-/
Thanks,
Ingo
next prev parent reply other threads:[~2015-05-13 13:54 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-15 9:41 [PATCH 0/3] hrtimer (related) fixes Peter Zijlstra
2015-04-15 9:41 ` [PATCH 1/3] hrtimer: Fix race between hrtimer_start() and __run_hrtimer() Peter Zijlstra
2015-04-15 10:26 ` Thomas Gleixner
2015-04-15 11:31 ` Peter Zijlstra
2015-04-15 11:35 ` Thomas Gleixner
2015-04-15 11:43 ` Peter Zijlstra
2015-04-22 19:15 ` [tip:timers/core] hrtimer: Allow concurrent hrtimer_start() for self restarting timers tip-bot for Peter Zijlstra
2015-05-12 13:52 ` Sasha Levin
2015-05-13 13:43 ` Peter Zijlstra
2015-05-13 13:54 ` Ingo Molnar [this message]
2015-05-13 17:25 ` bsegall
2015-05-13 23:09 ` Sasha Levin
2015-05-14 10:23 ` Peter Zijlstra
2015-05-18 15:21 ` [tip:timers/core] sched,perf: Fix periodic timers tip-bot for Peter Zijlstra
2015-04-15 9:41 ` [PATCH 2/3] sched: Cleanup bandwidth timers Peter Zijlstra
2015-04-16 20:03 ` bsegall
2015-04-22 19:15 ` [tip:timers/core] " tip-bot for Peter Zijlstra
2015-04-15 9:41 ` [PATCH 3/3] perf: Fix mux_interval hrtimer wreckage Peter Zijlstra
2015-04-15 13:48 ` David Ahern
2015-04-15 14:20 ` Peter Zijlstra
2015-04-22 15:12 ` Thomas Gleixner
2015-04-22 19:15 ` [tip:timers/core] " tip-bot for Peter Zijlstra
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150513135422.GA24332@gmail.com \
--to=mingo@kernel.org \
--cc=bsegall@google.com \
--cc=hpa@zytor.com \
--cc=klamm@yandex-team.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=pjt@google.com \
--cc=sasha.levin@oracle.com \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.