Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Jakub Jelinek <jakub@xxxxxxxxxx>
- Date: Fri, 16 Jun 2006 17:58:04 +0200
On Fri, Jun 16, 2006 at 05:37:06PM +0200, Andi Kleen wrote:
On Friday 16 June 2006 17:31, Zoltan Menyhart wrote:
Andi Kleen wrote:
That is not how user space TLS works. It usually has a base a register.
Can you please give me a real life (simplified) example?
On x86-64 it's just %fs:offset. gcc is a bit dumb on this and usually
loads the base address from %fs:0 first.
GCC is not dumb, unless you force it with -mno-tls-direct-seg-refs.
Guess you are bitten by SUSE GCC hack which makes -mno-tls-direct-seg-refs
the default (especially on x86-64 it is a really bad idea).
Jakub
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Andi Kleen
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- References:
- FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Andi Kleen
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Andi Kleen
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Zoltan Menyhart
- Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- From: Andi Kleen
- FOR REVIEW: New x86-64 vsyscall vgetcpu()
- Prev by Date: Re: sock_alloc() symbol removed in 2.6.10
- Next by Date: Network performance degradation from 2.6.11.12 to 2.6.16.20
- Previous by thread: Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- Next by thread: Re: FOR REVIEW: New x86-64 vsyscall vgetcpu()
- Index(es):
Relevant Pages
|
