Re: broken local_t on i386
- From: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>
- Date: Mon, 12 Jun 2006 21:12:41 +0100
Ar Llu, 2006-06-12 am 20:11 +0200, ysgrifennodd Andi Kleen:
The segment register needs an offset. So you need the linker to generate
the offset from the base of the per cpu segment somehow. At compile time the
address is not known so it cannot be done then.
What happens if you put a section at zero and a section at non-fixed
address (aligned). In the asm macros you stick the variable in both,
using the zero based one for linker symbols and the non zero based one
for data, then discard the zero based one.
That used to work for old binutils which didn't care/spot if you were
discarding material you actually linked against. Not sure what todays
binutils does with it.
Alan
-
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: broken local_t on i386
- From: Andi Kleen
- Re: broken local_t on i386
- References:
- 2.6.16-rc6-mm2
- From: Andrew Morton
- Re: broken local_t on i386
- From: Andi Kleen
- Re: broken local_t on i386
- From: Christoph Lameter
- Re: broken local_t on i386
- From: Andi Kleen
- 2.6.16-rc6-mm2
- Prev by Date: Re: [PATCH] tmpfs time granularity fix for [acm]time going backwards. Also VFS time granularity bug on creat(). (Repost, more content)
- Next by Date: Re: VGER does gradual SPF activation (FAQ matter)
- Previous by thread: Re: broken local_t on i386
- Next by thread: Re: broken local_t on i386
- Index(es):
Relevant Pages
|