public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Alexander Gordeev <agordeev@redhat.com>
Cc: linux-kernel@vger.kernel.org,
	Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
	Jiri Olsa <jolsa@redhat.com>, Ingo Molnar <mingo@kernel.org>,
	Peter Zijlstra <peterz@infradead.org>,
	Andi Kleen <ak@linux.jf.intel.com>
Subject: Re: [PATCH RFC v2 0/4] perf: IRQ-bound performance events
Date: Mon, 13 Jan 2014 16:50:37 +0100	[thread overview]
Message-ID: <20140113155034.GA10355@localhost.localdomain> (raw)
In-Reply-To: <cover.1388858996.git.agordeev@redhat.com>

On Sat, Jan 04, 2014 at 07:22:32PM +0100, Alexander Gordeev wrote:
> Hello,
> 
> This is version 2 of RFC "perf: IRQ-bound performance events". That is an
> introduction of IRQ-bound performance events - ones that only count in a
> context of a hardware interrupt handler. Ingo suggested to extend this
> functionality to softirq and threaded handlers as well:

Hi Alexander,

I still strongly think we should use toggle events to achieve that:
https://lkml.org/lkml/2013/9/25/227

This will let us count not just IRQs (-e 'cycles,irq_entry/on=cycles/,irq_exit/off=cycles/') but much more. 

The patchset still needs some polishing but I think that's a better diection.

Thanks.

  parent reply	other threads:[~2014-01-13 15:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-04 18:22 [PATCH RFC v2 0/4] perf: IRQ-bound performance events Alexander Gordeev
2014-01-04 18:22 ` [PATCH RFC v2 1/4] perf/core: " Alexander Gordeev
2014-01-04 18:22 ` [PATCH RFC v2 2/4] perf/x86: " Alexander Gordeev
2014-01-04 18:22 ` [PATCH RFC v2 3/4] perf/x86/Intel: " Alexander Gordeev
2014-01-04 18:22 ` [PATCH RFC v2 4/4] perf/tool: " Alexander Gordeev
2014-01-05 17:59 ` [PATCH RFC v2 0/4] perf: " Andi Kleen
2014-01-13 13:23   ` Alexander Gordeev
2014-01-13 15:50 ` Frederic Weisbecker [this message]
2014-01-14 16:07   ` Alexander Gordeev
2014-01-14 17:09     ` Frederic Weisbecker

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=20140113155034.GA10355@localhost.localdomain \
    --to=fweisbec@gmail.com \
    --cc=acme@ghostprotocols.net \
    --cc=agordeev@redhat.com \
    --cc=ak@linux.jf.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    /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