From: Mike Galbraith <efault@gmx.de>
To: Markus Trippelsdorf <markus@trippelsdorf.de>
Cc: Borislav Petkov <bp@amd64.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"hpa@linux.intel.com" <hpa@linux.intel.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
Andreas Herrmann <andreas.herrmann3@amd.com>
Subject: Re: Clocksource tsc unstable (delta = -8589361717 ns) in current git
Date: Wed, 27 Oct 2010 05:24:36 +0200 [thread overview]
Message-ID: <1288149876.7296.3.camel@marge.simson.net> (raw)
In-Reply-To: <20101026135808.GB1672@arch.trippelsdorf.de>
On Tue, 2010-10-26 at 15:58 +0200, Markus Trippelsdorf wrote:
> > > Initializing cgroup subsys cpu
> > > Linux version 2.6.36-05618-gb18cae4-dirty (markus@arch.trippelsdorf.de) (gcc version 4.5.1 (GCC) ) #41 SMP PREEMPT Tue Oct 26 06:51:47 CEST 2010
> >
> > ...-dirty means you have some changes ontop of b18cae4. What are those?
>
> The SCHED_AUTOGROUP patches from Mike Galbraith.
Turns out that patch is still racy btw. Very hard to trigger, but you
should remove it for safety and test result integrity anyway.
-Mike
prev parent reply other threads:[~2010-10-27 3:24 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-26 11:20 Clocksource tsc unstable (delta = -8589361717 ns) in current git Markus Trippelsdorf
2010-10-26 13:18 ` Borislav Petkov
2010-10-26 13:58 ` Markus Trippelsdorf
2010-10-26 14:05 ` Markus Trippelsdorf
2010-10-26 14:38 ` Peter Zijlstra
2010-10-26 15:46 ` Thomas Gleixner
2010-10-26 16:41 ` Borislav Petkov
2010-10-26 15:48 ` Thomas Gleixner
2010-10-26 17:56 ` Markus Trippelsdorf
2010-10-26 18:19 ` Borislav Petkov
2010-10-26 19:18 ` john stultz
2010-10-27 14:26 ` Markus Trippelsdorf
2010-10-27 18:26 ` [bisected] Clocksource tsc unstable git markus
2010-10-27 19:36 ` Peter Zijlstra
2010-10-27 19:42 ` Markus Trippelsdorf
2010-10-27 19:58 ` Marcelo Tosatti
2010-11-09 12:58 ` Heiko Carstens
2010-11-09 13:07 ` Markus Trippelsdorf
2010-11-09 13:21 ` Markus Trippelsdorf
2010-11-09 13:28 ` Heiko Carstens
2010-11-09 13:45 ` Peter Zijlstra
2010-11-09 13:33 ` Peter Zijlstra
2010-10-29 8:18 ` Borislav Petkov
2010-10-29 8:30 ` Markus Trippelsdorf
2010-10-29 10:27 ` Borislav Petkov
2010-10-29 11:34 ` Markus Trippelsdorf
2010-10-29 11:39 ` Borislav Petkov
2010-10-29 11:54 ` Markus Trippelsdorf
2010-10-29 13:13 ` Borislav Petkov
2010-10-29 12:14 ` Thomas Gleixner
2010-10-29 17:00 ` Borislav Petkov
2010-10-29 17:26 ` Markus Trippelsdorf
2010-11-01 18:05 ` Thomas Gleixner
2010-11-01 18:45 ` Markus Trippelsdorf
2010-11-02 15:26 ` Thomas Gleixner
2010-11-05 16:09 ` Borislav Petkov
2010-11-05 16:42 ` Markus Trippelsdorf
2010-11-05 17:45 ` Markus Trippelsdorf
2010-11-05 21:27 ` Markus Trippelsdorf
2010-11-05 21:32 ` Borislav Petkov
2010-11-09 14:02 ` Thomas Gleixner
2010-11-09 14:39 ` Borislav Petkov
2010-11-17 23:21 ` Markus Trippelsdorf
2010-11-24 11:25 ` Borislav Petkov
2010-10-29 17:34 ` Thomas Gleixner
2010-10-27 3:24 ` Mike Galbraith [this message]
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=1288149876.7296.3.camel@marge.simson.net \
--to=efault@gmx.de \
--cc=andreas.herrmann3@amd.com \
--cc=bp@amd64.org \
--cc=hpa@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus@trippelsdorf.de \
--cc=mingo@elte.hu \
--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