From: Markus Metzger <markus.t.metzger@googlemail.com>
To: eranian@gmail.com
Cc: "Metzger, Markus T" <markus.t.metzger@intel.com>,
Markus Metzger <markus.t.metzger@googlemail.com>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: debugctl msr
Date: Sat, 22 Nov 2008 10:51:31 +0100 [thread overview]
Message-ID: <1227347491.6146.13.camel@raistlin> (raw)
In-Reply-To: <7c86c4470811211447p57b38ecy9520a9e5170d2ce1@mail.gmail.com>
On Fri, 2008-11-21 at 23:47 +0100, stephane eranian wrote:
> With the current code base, ds.c can accept a pre-allocated buffer.
> However, it does
> some adjustments for alignment and size (multiple of PEBS record
> size). That means
> that the start and end of the buffer could be different from the area
> passed to ds_request_pebs().
>
> To parse the buffer, a monitoring tools needs a start position and the
> number of samples. The start
> position can be expressed as an offset from the beginning of the
> perfmon buffer. The ds.c interface
> currently only returns indexes for current position, threshold, and
> end. Those indexes are good enough
> to derived the number of samples. But I would need one call to return
> the byte offset from the original
> buffer, or the actual address (which perfmon could then convert back
> to an offset from its buffer).
ds_access() returns the pointer into the raw buffer at a given index.
For index 0, this is the beginning of the buffer.
I plan to replace the various access functions with a single one that
returns a const pointer to the configuration.
Something like:
struct ds_config {
size_t number_of_records;
size_t size_of_a_single_record;
void *base;
void *max;
void *index;
void *threshold;
};
const struct ds_config *ds_config_pebs(struct pebs_tracer *tracer);
For BTS, I would add functions to work on this struct and translate raw
entries into an architecture-independent format.
I'm not sure whether this would make sense for PEBS, as well.
Would you be OK with such a change?
thanks and regards,
markus.
next prev parent reply other threads:[~2008-11-22 9:51 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 ` debugctl msr 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
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 [this message]
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=1227347491.6146.13.camel@raistlin \
--to=markus.t.metzger@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@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