From: Ingo Molnar <mingo@elte.hu>
To: "K.Prasad" <prasad@linux.vnet.ibm.com>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Steven Rostedt <rostedt@goodmis.org>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
Alan Stern <stern@rowland.harvard.edu>
Subject: Re: [Patch 0/1] HW-BKPT: Allow per-cpu kernel-space Hardware Breakpoint requests
Date: Fri, 21 Aug 2009 16:28:11 +0200 [thread overview]
Message-ID: <20090821142811.GF11098@elte.hu> (raw)
In-Reply-To: <20090820172719.GA16499@in.ibm.com>
* K.Prasad <prasad@linux.vnet.ibm.com> wrote:
> > Providing those would let us build a pmu struct on top of this
> > high level API, hopefully.
Note that there's a PMU struct already in
arch/x86/kernel/cpu/perf_counter.c. Could debug-register ops be
tacked on to it?
> > All that would be a benefit in both sides. It avoids us building
> > a low level PMU that reinvent the wheel, ie: the hardware
> > breakpoints API handles a lot of things both in arch and core
> > sides (debug register setting tricks with dr7 and co, cpu
> > hotplug, kexec, etc...). In the bp API it brings more power
> > (register switching only if needed, per cpu support, clone
> > inheritance support, etc...)
> >
> > And in the end we have a pmu (which unifies the control of this
> > profiling unit through a well established and known object for
> > perfcounter) controlled by a high level API that could also
> > benefit to other debugging subsystems.
> >
> > What do you think? It would be also nice to have Peter's and
> > Ingo opinion about it, to be sure we are not going in the wrong
> > direction.
>
> Indeed, it will be nice to know from Ingo and Peter that we are
> heading right.
If you do this proper perfcounters integration then i'm certainly
happy.
Ingo
next prev parent reply other threads:[~2009-08-21 14:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-17 12:46 K.Prasad
2009-08-19 16:11 ` K.Prasad
2009-08-19 17:33 ` Frederic Weisbecker
2009-08-20 17:27 ` K.Prasad
2009-08-21 14:28 ` Ingo Molnar [this message]
2009-08-26 3:36 ` Frederic Weisbecker
2009-08-26 9:16 ` Ingo Molnar
2009-08-26 11:49 ` Frederic Weisbecker
2009-08-26 18:02 ` K.Prasad
2009-08-29 13:41 ` Ingo Molnar
2009-09-01 6:38 ` K.Prasad
2009-09-01 23:51 ` Frederic Weisbecker
2009-09-03 18:28 ` K.Prasad
2009-09-03 19:22 ` Ingo Molnar
2009-08-25 20:33 ` K.Prasad
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=20090821142811.GF11098@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=peterz@infradead.org \
--cc=prasad@linux.vnet.ibm.com \
--cc=rostedt@goodmis.org \
--cc=stern@rowland.harvard.edu \
/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
Powered by JetHome