Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables

Richard Henderson writes:

> How do you plan to address the compiler optimizing
> 
> 	__thread int foo;
> 	{
> 	  use(foo);
> 	  schedule();
> 	  use(foo);
> 	}
> 
> into
> 
> 	{
> 	  int *tmp = &foo;	// tls arithmetic here
> 	  use(*tmp);
> 	  schedule();
> 	  use(*tmp);
> 	}

Hmmm...  Would it be sufficient to use a RELOC_HIDE in __get_cpu_var,
like this?

#define __get_cpu_var(x)	(*(RELOC_HIDE(&per_cpu__##x, 0)))

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

---

• Follow-Ups:
  • Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
    • From: Paul Mackerras <[email protected]>

• References:
  • [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
    • From: Paul Mackerras <[email protected]>
  • Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
    • From: Richard Henderson <[email protected]>

• Prev by Date: Oops in au8830 driver on x86-64
• Next by Date: Re: [PATCH -mm] sys_semctl gcc 4.1 warning fix
• Previous by thread: Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
• Next by thread: Re: [RFC/PATCH] Make powerpc64 use __thread for per-cpu variables
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]