From: Peter Zijlstra <peterz@infradead.org>
To: Cyrill Gorcunov <gorcunov@openvz.org>
Cc: Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
ming.m.lin@intel.com, eranian@google.com
Subject: Re: [rfc 3/3] perf, x86: P4 PMU -- export ABI part of event config to userspace
Date: Wed, 24 Nov 2010 10:02:36 +0100 [thread overview]
Message-ID: <1290589356.2072.433.camel@laptop> (raw)
In-Reply-To: <AANLkTinac7XwdARsLSeLmbc4Kj6my5MHQ=hAgV+A7o-W@mail.gmail.com>
On Wed, 2010-11-24 at 11:48 +0300, Cyrill Gorcunov wrote:
> On 11/24/10, Peter Zijlstra <peterz@infradead.org> wrote:
> > On Wed, 2010-11-24 at 01:46 +0300, Cyrill Gorcunov wrote:
> >> plain text document attachment (x86-perf-export-abi)
> >> Due to tight 64 bit size of event config field (where we have to track
> >> pretty lot of info during event lifetime) some bits are to be exported
> >> via header into userspace.
> >>
> >> Signed-off-by: Cyrill Gorcunov <gorcunov@openvz.org>
> >> CC: Lin Ming <ming.m.lin@intel.com>
> >> CC: Stephane Eranian <eranian@google.com>
> >> CC: Peter Zijlstra <peterz@infradead.org>
> >> ---
> >>
> >> Note that I don't like much the idea to export anything into userspace
> >> but it seems there is no other choise. So there is a minimum which should
> >> be exported.
> >
> >
> > Could you say what exactly is exposed to userspace and why?
>
> yes, we need two enums to be exported, because we use custom encoding,
> which is described in first patch. peter i'll describe more detailed
> in a couple of hours, ok?
Sure, but have you seen my sysfs patches? wouldn't describing the format
in there suffice?
http://lkml.org/lkml/2010/11/17/154
next prev parent reply other threads:[~2010-11-24 9:02 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-23 22:46 [rfc 0/3] perf,x86: p4 pmu series Cyrill Gorcunov
2010-11-23 22:46 ` [rfc 1/3] perf, x86: P4 PMU - describe config format Cyrill Gorcunov
2010-11-26 10:57 ` Stephane Eranian
2010-11-26 11:14 ` Cyrill Gorcunov
2010-11-26 11:32 ` Cyrill Gorcunov
2010-11-26 11:35 ` Stephane Eranian
2010-11-26 11:58 ` Cyrill Gorcunov
2010-11-26 12:46 ` Stephane Eranian
2010-11-26 13:04 ` Cyrill Gorcunov
2010-11-26 13:06 ` Peter Zijlstra
2010-11-26 13:47 ` Cyrill Gorcunov
2010-11-26 13:10 ` Stephane Eranian
2010-11-26 13:50 ` Cyrill Gorcunov
2010-11-26 13:54 ` Stephane Eranian
2010-11-26 15:27 ` Cyrill Gorcunov
2010-11-26 16:22 ` Stephane Eranian
2010-11-26 17:16 ` Cyrill Gorcunov
2010-11-26 18:05 ` Stephane Eranian
2010-11-26 20:11 ` Cyrill Gorcunov
2010-11-26 12:48 ` Stephane Eranian
2010-11-26 12:59 ` Peter Zijlstra
2010-11-26 13:07 ` Stephane Eranian
2010-11-26 13:07 ` Cyrill Gorcunov
2010-11-23 22:46 ` [rfc 2/3] perf, x86: P4 PMU - Fix unflagged overflows handling v4 Cyrill Gorcunov
2010-11-23 22:46 ` [rfc 3/3] perf, x86: P4 PMU -- export ABI part of event config to userspace Cyrill Gorcunov
2010-11-24 8:32 ` Peter Zijlstra
2010-11-24 8:48 ` Cyrill Gorcunov
2010-11-24 9:02 ` Peter Zijlstra [this message]
2010-11-24 9:39 ` Cyrill Gorcunov
2010-11-24 11:46 ` Cyrill Gorcunov
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=1290589356.2072.433.camel@laptop \
--to=peterz@infradead.org \
--cc=eranian@google.com \
--cc=gorcunov@openvz.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.m.lin@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 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.