All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vrabel <david.vrabel@citrix.com>
To: David Vrabel <david.vrabel@citrix.com>
Cc: "x86@kernel.org" <x86@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] x86: allow tracing of functions in arch/x86/kernel/rtc.c
Date: Fri, 5 Oct 2012 12:24:19 +0100	[thread overview]
Message-ID: <506EC363.9050201@citrix.com> (raw)
In-Reply-To: <1349435895-21269-1-git-send-email-david.vrabel@citrix.com>

On 05/10/12 12:18, David Vrabel wrote:
> Move native_read_tsc() to tsc.c to allow profiling to be re-enabled
> for rtc.c.

Sorry, dropped the EXPORT_SYMBOL() by mistake.  I'll fix this and repost.

David

> diff --git a/arch/x86/kernel/rtc.c b/arch/x86/kernel/rtc.c
> index af6db6e..8ab7c62 100644
> --- a/arch/x86/kernel/rtc.c
> +++ b/arch/x86/kernel/rtc.c
> @@ -195,12 +195,6 @@ void read_persistent_clock(struct timespec *ts)
>  	ts->tv_nsec = 0;
>  }
>  
> -unsigned long long native_read_tsc(void)
> -{
> -	return __native_read_tsc();
> -}
> -EXPORT_SYMBOL(native_read_tsc);
> -
>  
>  static struct resource rtc_resources[] = {
>  	[0] = {
> diff --git a/arch/x86/kernel/tsc.c b/arch/x86/kernel/tsc.c
> index cfa5d4f..15e190a 100644
> --- a/arch/x86/kernel/tsc.c
> +++ b/arch/x86/kernel/tsc.c
> @@ -77,6 +77,11 @@ unsigned long long
>  sched_clock(void) __attribute__((alias("native_sched_clock")));
>  #endif
>  
> +unsigned long long native_read_tsc(void)
> +{
> +	return __native_read_tsc();
> +}
> +
>  int check_tsc_unstable(void)
>  {
>  	return tsc_unstable;


  reply	other threads:[~2012-10-05 11:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 11:18 [PATCH] x86: allow tracing of functions in arch/x86/kernel/rtc.c David Vrabel
2012-10-05 11:24 ` David Vrabel [this message]
2012-10-08 12:07 ` [PATCHv2] " David Vrabel
2012-10-24 13:00   ` [tip:perf/core] x86: Allow tracing of functions in arch/x86/kernel /rtc.c tip-bot for David Vrabel

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=506EC363.9050201@citrix.com \
    --to=david.vrabel@citrix.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.