public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Mike Galbraith <efault@gmx.de>
Cc: "Lin Ming" <ming.m.lin@intel.com>,
	mingo@elte.hu, tglx@linutronix.de,
	linux-kernel <linux-kernel@vger.kernel.org>,
	"Zhang, Yanmin" <yanmin_zhang@linux.intel.com>,
	"Frédéric Weisbecker" <fweisbec@gmail.com>
Subject: Re: tbench regression with 2.6.33-rc1
Date: Sun, 27 Dec 2009 09:59:09 +0100	[thread overview]
Message-ID: <1261904349.15854.2.camel@laptop> (raw)
In-Reply-To: <1261902760.6201.33.camel@marge.simson.net>

On Sun, 2009-12-27 at 09:32 +0100, Mike Galbraith wrote:
> Perf also isn't free, and in 33, we lost the ability to config it out,

Uhm, that's a plain bug, we should be able to build a kernel without
perf support, does the hw breakpoint support have an unfortunate select
some place or something?


  reply	other threads:[~2009-12-27  9:00 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-25 11:11 tbench regression with 2.6.33-rc1 Lin Ming
2009-12-27  8:32 ` Mike Galbraith
2009-12-27  8:59   ` Peter Zijlstra [this message]
2009-12-27  9:41     ` Mike Galbraith
2009-12-27 10:11       ` Peter Zijlstra
2010-01-02  3:56         ` Frederic Weisbecker
2009-12-29  2:09   ` Lin Ming
2009-12-29  5:24     ` Mike Galbraith
2009-12-29  5:19       ` Lin Ming
2009-12-29  5:49         ` Mike Galbraith
2010-01-06  6:01           ` Mike Galbraith
2010-01-06  5:55             ` Lin Ming
2010-01-06  6:52               ` Lin Ming
2010-01-06  7:44                 ` Mike Galbraith
2010-01-11 12:08 ` Peter Zijlstra
2010-01-11 16:16   ` Mike Galbraith
2010-01-12  1:09     ` Lin Ming
2010-01-12  2:33       ` Mike Galbraith
2010-01-12  3:13         ` Lin Ming
2010-01-12  4:14           ` Mike Galbraith
2010-01-12  8:54       ` Peter Zijlstra
2010-01-12  9:20         ` Lin Ming

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=1261904349.15854.2.camel@laptop \
    --to=peterz@infradead.org \
    --cc=efault@gmx.de \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ming.m.lin@intel.com \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    --cc=yanmin_zhang@linux.intel.com \
    /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