From: Jiri Olsa <jolsa@redhat.com>
To: David Ahern <david.ahern@oracle.com>
Cc: Adrian Hunter <adrian.hunter@intel.com>,
acme@kernel.org, linux-kernel@vger.kernel.org,
Jiri Olsa <jolsa@kernel.org>
Subject: Re: [PATCH] perf: Only include tsc file for x86
Date: Fri, 20 Feb 2015 19:53:19 +0100 [thread overview]
Message-ID: <20150220185318.GA817@krava.redhat.com> (raw)
In-Reply-To: <54E76399.40105@oracle.com>
On Fri, Feb 20, 2015 at 09:40:57AM -0700, David Ahern wrote:
> On 2/20/15 1:36 AM, Adrian Hunter wrote:
> >On 19/02/15 21:42, Jiri Olsa wrote:
> >>On Thu, Feb 19, 2015 at 01:22:33PM -0500, David Ahern wrote:
> >>>perf_time_to_tsc and tsc_to_perf_time are only used for x86. Make
> >>>inclusion of tsc.c dependent on x86 as well.
> >>
> >>hum, should we move it to arch/x86/util/tsc.c and remove util/tsc.c?
> >
> >It is not arch-specific because you can read a perf.data file
> >from one architecture on another architecture.
> >
> >The TSC stuff was planned for Intel PT although it might now
> >be done differently.
> >
> >Probably you should have CONFIG_X86_TSC and then select that
> >with CONFIG_X86. Later it can be selected with CONFIG_INTEL_PT
> >as well.
>
> For now let's leave it as CONFIG_X86. Right now only X86 code needs the
> functions it provides and there is no need taking any other steps until
> something is going to use it.
>
> ie., patch is good as is. Agreed?
ook, jirka
next prev parent reply other threads:[~2015-02-20 18:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 18:22 David Ahern
2015-02-19 19:42 ` Jiri Olsa
2015-02-20 8:36 ` Adrian Hunter
2015-02-20 16:40 ` David Ahern
2015-02-20 18:53 ` Jiri Olsa [this message]
2015-03-03 6:21 ` [tip:perf/core] perf tools: " tip-bot for David Ahern
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=20150220185318.GA817@krava.redhat.com \
--to=jolsa@redhat.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=david.ahern@oracle.com \
--cc=jolsa@kernel.org \
--cc=linux-kernel@vger.kernel.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
Powered by JetHome