Hi!
I'm working on a RDTSCP support on x86-64, and for that, I'll need
per-cpu time offset table in a vsyscall page. I saw the percpu.h header,
and thought - "Hey, I could use that!", but I think I really can't.
The data need to be in a vsyscall page, which is mapped to userspace via
linker magic, and the percpu stuff uses a different mapping.
I'm using a simple array instead, because the address will be different
in a vsyscall from the one the kernel sees anyway, and RDTSCP will give
me an index to that array atomically.
Is there any problem with that approach? Is there any reason using
percpu.h would be better?
--
Vojtech Pavlik
SuSE Labs, SuSE CR
-
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]
