lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <506EC363.9050201@citrix.com>
Date:	Fri, 5 Oct 2012 12:24:19 +0100
From:	David Vrabel <david.vrabel@...rix.com>
To:	David Vrabel <david.vrabel@...rix.com>
CC:	"x86@...nel.org" <x86@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] x86: allow tracing of functions in arch/x86/kernel/rtc.c

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;

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ