From: "stephane eranian" <eranian@googlemail.com>
To: "Metzger, Markus T" <markus.t.metzger@intel.com>
Cc: "Ingo Molnar" <mingo@elte.hu>, "Andi Kleen" <andi@firstfloor.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org,
"Markus Metzger" <markus.t.metzger@googlemail.com>
Subject: Re: debugctl msr
Date: Fri, 14 Nov 2008 22:10:35 +0100 [thread overview]
Message-ID: <7c86c4470811141310h4fd3c5fbvc6357985cf2aed0e@mail.gmail.com> (raw)
In-Reply-To: <029E5BE7F699594398CA44E3DDF5544402B595A3@swsmsx413.ger.corp.intel.com>
Markus,
I am trying another approach for connecting perfmon to ds.c. I have
added new callbacks
to perfmon to allow me to invoke ds_request_pebs, once I know the
target thread or CPU.
That seems to work, however I ran into a spinlock problem is ds_request():
static int ds_request(struct task_struct *task, void *base, size_t size,
ds_ovfl_callback_t ovfl, enum ds_qualifier qual)
{
struct ds_context *context;
unsigned long buffer, adj;
const unsigned long alignment = (1 << 3);
int error = 0;
if (!ds_cfg.sizeof_ds)
return -EOPNOTSUPP;
/* we require some space to do alignment adjustments below */
if (size < (alignment + ds_cfg.sizeof_rec[qual]))
return -EINVAL;
/* buffer overflow notification is not yet implemented */
if (ovfl)
return -EOPNOTSUPP;
spin_lock(&ds_lock);
>> if (!check_tracer(task))
>> return -EPERM;
You need to spin_unlock() before returning here!
next prev parent reply other threads:[~2008-11-14 21:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7c86c4470810300753v7d377092qbcd266178d8e7338@mail.gmail.com>
[not found] ` <029E5BE7F699594398CA44E3DDF5544402AB2C50@swsmsx413.ger.corp.intel.com>
[not found] ` <7c86c4470811040822i6745bee6mbe451284d76549be@mail.gmail.com>
[not found] ` <7c86c4470811050505j678c6929if00cceda2af8cb17@mail.gmail.com>
[not found] ` <7c86c4470811050711w3753232fk1030fb00259a7b8@mail.gmail.com>
[not found] ` <029E5BE7F699594398CA44E3DDF5544402AB350E@swsmsx413.ger.corp.intel.com>
[not found] ` <7c86c4470811060249g62666885nbaa559c1777217a0@mail.gmail.com>
[not found] ` <1226236327.6104.4.camel@raistlin>
[not found] ` <7c86c4470811111411k754887a8ic9b63163928157a6@mail.gmail.com>
[not found] ` <491A812D.9010208@gmail.com>
2008-11-12 10:10 ` stephane eranian
2008-11-12 10:59 ` Metzger, Markus T
2008-11-13 14:50 ` stephane eranian
2008-11-14 14:41 ` Metzger, Markus T
2008-11-14 21:10 ` stephane eranian [this message]
2008-11-15 10:01 ` Markus Metzger
2008-11-18 22:00 ` stephane eranian
2008-11-19 12:14 ` Metzger, Markus T
2008-11-19 12:59 ` stephane eranian
2008-11-19 15:47 ` Metzger, Markus T
2008-11-19 17:13 ` stephane eranian
2008-11-19 18:27 ` Markus Metzger
2008-11-19 19:20 ` stephane eranian
2008-11-19 20:53 ` stephane eranian
2008-11-19 22:26 ` Markus Metzger
2008-11-20 21:19 ` stephane eranian
2008-11-21 8:22 ` Metzger, Markus T
2008-11-21 8:47 ` stephane eranian
2008-11-21 8:58 ` Metzger, Markus T
2008-11-21 13:38 ` stephane eranian
2008-11-21 15:27 ` stephane eranian
2008-11-21 16:10 ` Metzger, Markus T
2008-11-21 16:33 ` stephane eranian
2008-11-21 22:47 ` stephane eranian
2008-11-22 9:51 ` Markus Metzger
2008-11-23 22:31 ` stephane eranian
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=7c86c4470811141310h4fd3c5fbvc6357985cf2aed0e@mail.gmail.com \
--to=eranian@googlemail.com \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=eranian@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=markus.t.metzger@googlemail.com \
--cc=markus.t.metzger@intel.com \
--cc=mingo@elte.hu \
/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