From: Lin Ming <ming.m.lin@intel.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>,
Ingo Molnar <mingo@elte.hu>, Andi Kleen <andi@firstfloor.org>,
Stephane Eranian <eranian@google.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: [PATCH 0/6] perf: offcore event monitoring patches
Date: Mon, 21 Feb 2011 00:56:36 +0800 [thread overview]
Message-ID: <1298220996.2318.61.camel@localhost> (raw)
Hi, all
Sorry for late update, I was mostly on vacation in the past months.
FYI, the previous version at below link
http://marc.info/?l=linux-kernel&m=129346414407543&w=2
[PATCH 0/7] perf: offcore and load latency monitoring patches
I need some time to add userspace perf tool support for load latency
monitoring, so for now I only post offcore patches here.
The most visible changes is adding a new field
perf_event_attr::event_extra for extra MSR encoding, which is the first
revision of the Andi's patch did. And also
Peter,
This version has addressed the comments against last version, could you
please consider merging this series?
Thanks,
Lin Ming
reply other threads:[~2011-02-20 16:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1298220996.2318.61.camel@localhost \
--to=ming.m.lin@intel.com \
--cc=a.p.zijlstra@chello.nl \
--cc=andi@firstfloor.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--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