Hi,
On Sun, Aug 27, 2006 at 08:04:38PM +0200, Andi Kleen wrote:
>
> > Something like that had to be done eventually about the inefficient
> > current_thread_info() mechanism,
>
> Inefficient? It's two fast instructions. I won't call that inefficient.
And that AGI stall?
> > I guess it's due to having tried that on an older installation with gcc 3.2,
> > which probably does less efficient opcode merging of current_thread_info()
> > requests compared to a current gcc version.
>
> gcc normally doesn't merge inline assembly at all.
Depends on use of volatile, right?
OK, so probably there was no merging of separate requests,
but opcode intermingling could have played a role.
Andreas Mohr
-
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/
[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]
