From: Megha Dey <megha.dey@intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: x86@kernel.org, linux-kernel@vger.kernel.org,
linux-doc@vger.kernel.org, tglx@linutronix.de, mingo@redhat.com,
hpa@zytor.com, andriy.shevchenko@linux.intel.com,
kstewart@linuxfoundation.org, yu-cheng.yu@intel.com,
len.brown@intel.com, gregkh@linuxfoundation.org, acme@kernel.org,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, vikas.shivappa@linux.intel.com,
pombredanne@nexb.com, me@kylehuey.com, bp@suse.de,
grzegorz.andrejczuk@intel.com, tony.luck@intel.com,
corbet@lwn.net, ravi.v.shankar@intel.com,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH V2 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support
Date: Wed, 04 Apr 2018 14:33:25 -0700 [thread overview]
Message-ID: <1522877605.3367.2.camel@megha-Z97X-UD7-TH> (raw)
In-Reply-To: <1513805032.31684.2.camel@megha-Z97X-UD7-TH>
On Wed, 2017-12-20 at 13:23 -0800, Megha Dey wrote:
> On Wed, 2017-12-13 at 08:21 +0100, Peter Zijlstra wrote:
> > On Tue, Dec 12, 2017 at 03:08:00PM -0800, Megha Dey wrote:
> > > >
> > > > There's work on the way to allow multiple HW PMUs. You'll either have to
> > > > wait for that or help in making that happen. What you do not do is
> > > > silently hack around it.
> > >
> > > Could I get a pointer to the code implementing this?
> > >
> >
> > There isn't much code now; but it could be build on top of the stuff
> > here:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git perf/core
> >
> > It was mostly Mark I think who wanted this for big litte stuffs.
>
> Could you give us an estimate on the amount of time it could take to
> implement this?
>
> I am not sure what the current status is or if Mark has been working on
> it.
>
Hi Peter,
Is there anyone currently working on this?
next prev parent reply other threads:[~2018-04-04 21:33 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-18 1:54 [PATCH V2 0/3] perf/x86/intel: Add " Megha Dey
2017-11-18 1:54 ` [PATCH V2 1/3] x86/cpu/intel: Add Cannonlake to Intel family Megha Dey
2017-11-18 1:54 ` [PATCH V2 2/3] perf/x86/intel/bm.c: Add Intel Branch Monitoring support Megha Dey
2017-11-20 11:57 ` Peter Zijlstra
2017-12-12 21:10 ` Megha Dey
2017-12-12 22:32 ` Peter Zijlstra
2017-12-12 23:08 ` Megha Dey
2017-12-13 7:21 ` Peter Zijlstra
2017-12-20 21:23 ` Megha Dey
2018-04-04 21:33 ` Megha Dey [this message]
2017-11-20 14:10 ` Jiri Olsa
2017-12-12 21:03 ` Megha Dey
2017-11-18 1:54 ` [PATCH V2 3/3] x86, bm: Add documentation on Intel Branch Monitoring Megha Dey
2017-11-20 14:07 ` Jiri Olsa
2017-12-12 21:05 ` Megha Dey
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=1522877605.3367.2.camel@megha-Z97X-UD7-TH \
--to=megha.dey@intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=bp@suse.de \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=grzegorz.andrejczuk@intel.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=len.brown@intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=me@kylehuey.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=pombredanne@nexb.com \
--cc=ravi.v.shankar@intel.com \
--cc=tglx@linutronix.de \
--cc=tony.luck@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=x86@kernel.org \
--cc=yu-cheng.yu@intel.com \
/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
all inboxes | Powered by JetHome®