mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Javi Merino <javi.merino@arm.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"cw00.choi@samsung.com" <cw00.choi@samsung.com>,
	"edubezval@gmail.com" <edubezval@gmail.com>,
	Zhang Rui <rui.zhang@intel.com>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH v6 4/5] devfreq_cooling: add trace information
Date: Fri, 18 Sep 2015 10:04:28 -0400	[thread overview]
Message-ID: <20150918100428.0d2f71f5@gandalf.local.home> (raw)
In-Reply-To: <20150918135550.GA5283@e104805>

On Fri, 18 Sep 2015 14:55:51 +0100
Javi Merino <javi.merino@arm.com> wrote:


> > A tracepoint does some whacky things, and gcc may not optimize this.
> 
> I've compared the generated assembly on arm, arm64 and x86_64 and both
> options generate exactly the same code.

Thanks for checking. I was just curious, and I'm wary about trusting
gcc to optimize correctly ;-)


-- Steve

  reply	other threads:[~2015-09-18 14:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10 17:09 [PATCH v6 0/5] Devfreq cooling device Javi Merino
2015-09-10 17:09 ` [PATCH v6 1/5] PM / devfreq: cache the last call to get_dev_status() Javi Merino
2015-09-10 17:09 ` [PATCH v6 2/5] PM / OPP: get the voltage for all OPPs Javi Merino
2015-09-10 17:09 ` [PATCH v6 3/5] thermal: Add devfreq cooling Javi Merino
2015-09-10 17:09 ` [PATCH v6 4/5] devfreq_cooling: add trace information Javi Merino
2015-09-10 17:19   ` Steven Rostedt
2015-09-18 13:55     ` Javi Merino
2015-09-18 14:04       ` Steven Rostedt [this message]
2015-10-14 11:53     ` Javi Merino
2015-10-14 13:22       ` Steven Rostedt
2015-09-10 17:09 ` [PATCH v6 5/5] PM / devfreq: drop comment about thermal setting max_freq Javi Merino

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=20150918100428.0d2f71f5@gandalf.local.home \
    --to=rostedt@goodmis.org \
    --cc=cw00.choi@samsung.com \
    --cc=edubezval@gmail.com \
    --cc=javi.merino@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rui.zhang@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®