From: Martin Schwidefsky <schwidefsky@de.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: 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>,
Andi Kleen <andi@firstfloor.org>
Subject: [patch 0/2] NOHZ vs. profile/oprofile v2
Date: Wed, 03 Jun 2009 17:22:23 +0200 [thread overview]
Message-ID: <20090603152223.083010123@de.ibm.com> (raw)
Greetings,
version 2 of the profile patches. The only change is the in_interrupt()
fix in tick_nohz_stop_idle(). I would like to know how to proceed with
the issue.
Andy, do you still prefer to handle the old style profiler analog to
the oprofile patch? If yes I would drop patch #1 and extend patch #2
with another tick_nohz_disable().
--
blue skies,
Martin.
"Reality continues to ruin my life." - Calvin.
next reply other threads:[~2009-06-03 15:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:22 Martin Schwidefsky [this message]
2009-06-03 15:22 ` [patch 1/2] idle profile hits with NOHZ Martin Schwidefsky
2009-06-03 15:22 ` [patch 2/2] keep on ticking if oprofile is active Martin Schwidefsky
2009-06-09 20:52 ` [patch 0/2] NOHZ vs. profile/oprofile v2 Thomas Gleixner
2009-06-10 17:33 ` Martin Schwidefsky
2009-06-22 14:26 ` Martin Schwidefsky
2009-06-22 14:41 ` Ingo Molnar
2009-06-22 14:59 ` Martin Schwidefsky
2009-06-22 15:05 ` Ingo Molnar
2009-06-22 15:18 ` Martin Schwidefsky
2009-06-22 15:29 ` Ingo Molnar
2009-06-22 15:36 ` Martin Schwidefsky
2009-06-22 15:40 ` Ingo Molnar
2009-06-22 16:37 ` Martin Schwidefsky
2009-06-24 16:51 ` Martin Schwidefsky
2009-06-24 17:47 ` Ingo Molnar
2010-03-02 13:57 ` Aaro Koskinen
2010-03-02 15:01 ` Martin Schwidefsky
2010-03-02 15:08 ` Thomas Gleixner
2010-03-02 15:25 ` Martin Schwidefsky
2010-03-02 15:38 ` Robert Richter
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=20090603152223.083010123@de.ibm.com \
--to=schwidefsky@de.ibm.com \
--cc=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=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