public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel@vger.kernel.org,
	Rob van der Heij <rvdheij@gmail.com>,
	Heiko Carstens <heiko.carstens@de.ibm.com>,
	Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	john stultz <johnstul@us.ibm.com>
Subject: Re: [patch 2/2] keep on ticking if oprofile is active
Date: Mon, 01 Jun 2009 10:09:27 +0200	[thread overview]
Message-ID: <87vdngcr48.fsf@basil.nowhere.org> (raw)
In-Reply-To: <20090528150502.305840931@de.ibm.com> (Martin Schwidefsky's message of "Thu, 28 May 2009 17:04:49 +0200")

Martin Schwidefsky <schwidefsky@de.ibm.com> writes:

> From: Martin Schwidefsky <schwidefsky@de.ibm.com>
>
> On a NOHZ system with oprofile enabled the timer tick should not be

The old style profile=... profiler should do that too.

-Andi
-- 
ak@linux.intel.com -- Speaking for myself only.

  parent reply	other threads:[~2009-06-01  8:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-28 15:04 [patch 0/2] NOHZ vs. profile/oprofile Martin Schwidefsky
2009-05-28 15:04 ` [patch 1/2] idle profile hits with NOHZ Martin Schwidefsky
2009-05-28 20:19   ` Thomas Gleixner
2009-05-29 12:56     ` Martin Schwidefsky
2009-05-29 13:15       ` Thomas Gleixner
2009-05-28 15:04 ` [patch 2/2] keep on ticking if oprofile is active Martin Schwidefsky
2009-05-28 20:29   ` Thomas Gleixner
2009-05-29 12:57     ` Martin Schwidefsky
2009-05-29 13:14       ` Thomas Gleixner
2009-06-01  8:09   ` Andi Kleen [this message]
2009-06-01 10:22     ` Martin Schwidefsky
  -- strict thread matches above, loose matches on Subject: below --
2009-06-03 15:22 [patch 0/2] NOHZ vs. profile/oprofile v2 Martin Schwidefsky
2009-06-03 15:22 ` [patch 2/2] keep on ticking if oprofile is active Martin Schwidefsky

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=87vdngcr48.fsf@basil.nowhere.org \
    --to=andi@firstfloor.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rvdheij@gmail.com \
    --cc=schwidefsky@de.ibm.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