From: Frederic Weisbecker <fweisbec@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Will Deacon <will.deacon@arm.com>,
Prasad <prasad@linux.vnet.ibm.com>,
Paul Mundt <lethal@linux-sh.org>,
Jason Wessel <jason.wessel@windriver.com>,
"H . Peter Anvin" <hpa@zytor.com>,
Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [PATCH 0/6] hw_breakpoint: Let the user choose not to build it (and perf too)
Date: Wed, 27 Apr 2011 19:02:58 +0200 [thread overview]
Message-ID: <20110427170253.GA1753@nowhere> (raw)
In-Reply-To: <1303923602-2923-1-git-send-email-fweisbec@gmail.com>
On Wed, Apr 27, 2011 at 06:59:56PM +0200, Frederic Weisbecker wrote:
> Hi,
>
> Until now, x86 and superh32 had to always build hw_breakpoint and perf.
> And powerpc and arm were always building hw_breakpoints when perf
> was enabled.
>
> After this patchset, one can simply disable hw_breakpoints if he
> selected CONFIG_EXPERT. Afterward the user is free to select perf
> or not. Except on SH unfortunately because that would require a
> bit of change in ptrace to support singlestep failures.
>
> Frederic Weisbecker (6):
> hw_breakpoints: Split hardware breakpoints config
> hw_breakpoints: Migrate breakpoint conditional build under new config
> x86: Allow the user not to build hw_breakpoints
> hw_breakpoints: Breakpoints arch ability don't need perf events
> hw_breakpoints: Only force perf events if breakpoints are selected
> hw_breakpoints: Drop remaining misplaced dependency on perf
Ah, and every !x86 archs touched by this patchset have been compile tested only.
next prev parent reply other threads:[~2011-04-27 17:03 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 16:59 [PATCH 0/6] hw_breakpoint: Let the user choose not to build it (and perf too) Frederic Weisbecker
2011-04-27 16:59 ` [PATCH 1/6] hw_breakpoints: Split hardware breakpoints config Frederic Weisbecker
2011-04-27 16:59 ` [PATCH 2/6] hw_breakpoints: Migrate breakpoint conditional build under new config Frederic Weisbecker
2011-04-27 16:59 ` Frederic Weisbecker
2011-04-27 16:59 ` [PATCH 3/6] x86: Allow the user not to build hw_breakpoints Frederic Weisbecker
2011-04-27 17:38 ` H. Peter Anvin
2011-04-27 18:26 ` Frederic Weisbecker
2011-04-27 19:10 ` Michael Bohan
[not found] ` <008d59a3-bd23-4cb3-8a73-1640137e3ac4@email.android.com>
2011-04-27 19:50 ` Frederic Weisbecker
2011-05-03 15:35 ` H. Peter Anvin
2011-05-03 23:12 ` Frederic Weisbecker
2011-05-03 23:40 ` H. Peter Anvin
2011-05-03 23:54 ` Frederic Weisbecker
2011-05-03 23:56 ` H. Peter Anvin
2011-05-04 0:13 ` Frederic Weisbecker
2011-04-27 17:00 ` [PATCH 4/6] hw_breakpoints: Breakpoints arch ability don't need perf events Frederic Weisbecker
2011-04-27 17:00 ` [PATCH 5/6] hw_breakpoints: Only force perf events if breakpoints are selected Frederic Weisbecker
2011-04-27 17:00 ` [PATCH 6/6] hw_breakpoints: Drop remaining misplaced dependency on perf Frederic Weisbecker
2011-04-27 17:00 ` Frederic Weisbecker
2011-04-27 17:02 ` Frederic Weisbecker [this message]
2011-05-03 11:40 ` [PATCH 0/6] hw_breakpoint: Let the user choose not to build it (and perf too) Will Deacon
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=20110427170253.GA1753@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=hpa@zytor.com \
--cc=jason.wessel@windriver.com \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=will.deacon@arm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.