From: Jiri Olsa <firstname.lastname@example.org> To: Peter Zijlstra <email@example.com> Cc: Ingo Molnar <firstname.lastname@example.org>, Frederic Weisbecker <email@example.com>, Arnaldo Carvalho de Melo <firstname.lastname@example.org>, email@example.com, Arun Sharma <firstname.lastname@example.org> Subject: Re: regarding [PATCH] Add libpfm4 support (v3) Date: Mon, 8 Aug 2011 15:03:09 +0200 [thread overview] Message-ID: <20110808130309.GA4618@jolsa.brq.redhat.com> (raw) In-Reply-To: <1312806326.10488.30.camel@twins> On Mon, Aug 08, 2011 at 02:25:25PM +0200, Peter Zijlstra wrote: > On Mon, 2011-08-08 at 14:04 +0200, Jiri Olsa wrote: > > hi, > > > > any chance of getting this included? > > http://article.gmane.org/gmane.comp.linux.perfmon2.devel/2912 > > http://article.gmane.org/gmane.comp.linux.perfmon2.devel/2912/raw > > > > it needs just some little changes to fit to current tip tree > > While I don't mind extending the current way to input events I don't > think using libpfm4 for it is desired. > > One of the ideas that has been floating about is to provide a format > file in the sysfs representation of the pmu. This format file would > describe the config space. The tool would parse this and use it to > provide better input capabilities. > > This is not an easy task however, since the format syntax needs to be > capable enough to describe all the various config muck we need to > support, think for example of the P4 mess. > > For Intel/AMD (excluding P4) its mostly simple, with Intel having a > slightly harder time for the offcore bits. > > As to the various arch event lists, again that is not something we need > a whole library for, parsing those text files isn't hard. Maintaining > the various arch event lists in a sane format is the 'hard' part and is > something I think we should push to the vendors, because they're > basically the only ones capable. ok, understood thanks, jirka
prev parent reply other threads:[~2011-08-08 13:03 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-08-08 12:04 Jiri Olsa 2011-08-08 12:25 ` Peter Zijlstra 2011-08-08 13:03 ` Jiri Olsa [this message]
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=20110808130309.GA4618@jolsa.brq.redhat.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: regarding [PATCH] Add libpfm4 support (v3)' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).