mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mischa Jonker <Mischa.Jonker@synopsys.com>
To: Peter Zijlstra <peterz@infradead.org>,
	Mischa Jonker <Mischa.Jonker@synopsys.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"Vineet.Gupta1@synopsys.com" <Vineet.Gupta1@synopsys.com>,
	"mingo@redhat.com" <mingo@redhat.com>
Subject: RE: [PATCH v3 0/2] ARC: Add perf support for ARC700 cores
Date: Tue, 12 Nov 2013 09:44:34 +0000	[thread overview]
Message-ID: <E6BF041E97966E4DB955F0DF883AD2D685F17293@de02wembxa.internal.synopsys.com> (raw)
In-Reply-To: <20131111163042.GA10977@twins.programming.kicks-ass.net>

> Ah, so its one of those that cannot sample; you might want to fail when we
> try and create a sampling event.

Good suggestion, I'll create a separate patch for that!

> Also, you could consider running an (hr)timer to periodically update the
> events so that you don't miss a hardware counter wrap around -- if that is a
> distinct possibility.

It's a theoretical possibility: the counters are 48 bits. Unlikely to happen
during application development/performance analysis on an embedded core.

Thanks,

Mischa

  reply	other threads:[~2013-11-12  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-07 13:55 Mischa Jonker
2013-11-07 13:55 ` [PATCH v3 1/2] " Mischa Jonker
2013-11-11 16:27   ` Peter Zijlstra
2013-11-12  4:36     ` Vineet Gupta
2013-11-07 13:55 ` [PATCH v3 2/2] ARC: Add documentation on DT binding for ARC700 PMU Mischa Jonker
2013-11-11 16:27 ` [PATCH v3 0/2] ARC: Add perf support for ARC700 cores Peter Zijlstra
2013-11-11 16:30   ` Peter Zijlstra
2013-11-12  9:44     ` Mischa Jonker [this message]
2013-11-12  9:15   ` Mischa Jonker

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=E6BF041E97966E4DB955F0DF883AD2D685F17293@de02wembxa.internal.synopsys.com \
    --to=mischa.jonker@synopsys.com \
    --cc=Vineet.Gupta1@synopsys.com \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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
all inboxes | Powered by JetHome®