public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH] posix-cpu-timers: clock_gettime(CLOCK_*_CPUTIME_ID) goes backward
Date: Wed, 7 Jan 2009 18:59:03 +0100	[thread overview]
Message-ID: <20090107175903.GF24982@elte.hu> (raw)
In-Reply-To: <1230282171.9487.278.camel@twins>


* Peter Zijlstra <a.p.zijlstra@chello.nl> wrote:

> Which reminds me, why do we still have this crap in the kernel? I 
> thought we pretty much showed the per-cpu itimer thing was utter crap? 
> -- can we pretty please either revert that or apply 
> http://lkml.org/lkml/2008/11/24/183 ?
> 
> Also, I really don't like the above, we now do the per-cpu loop with the 
> RQ lock held...

ok, i've applied it to tip/timers/urgent. This should solve the original 
itimer testcase as well, correct?

	Ingo

  parent reply	other threads:[~2009-01-07 17:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-26  6:01 [PATCH] posix-cpu-timers: clock_gettime(CLOCK_*_CPUTIME_ID) goes backward Hidetoshi Seto
2008-12-26  8:43 ` Ingo Molnar
2008-12-26  9:02   ` Peter Zijlstra
2008-12-26  9:07     ` Ingo Molnar
2009-01-05  6:59       ` Hidetoshi Seto
2009-01-21  5:54         ` [PATCH] posixtimers: " Hidetoshi Seto
2009-01-21 13:18           ` Peter Zijlstra
2009-01-07 17:59     ` Ingo Molnar [this message]
2009-01-08  8:01       ` [PATCH] posix-cpu-timers: " Peter Zijlstra
2009-01-27  5:51 ` [RESEND][PATCH] posixtimers: " Hidetoshi Seto

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=20090107175903.GF24982@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=linux-kernel@vger.kernel.org \
    --cc=seto.hidetoshi@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox