Re: [PATCH 4/5] clocksource: Replace vread and fsys_mmio with genericarch data
From: Andrew Lutomirski
Date: Tue Jun 07 2011 - 17:18:45 EST
On Tue, Jun 7, 2011 at 5:06 PM, john stultz <johnstul@xxxxxxxxxx> wrote:
> On Tue, 2011-06-07 at 16:35 -0400, Andrew Lutomirski wrote:
>> On Tue, Jun 7, 2011 at 4:28 PM, john stultz <johnstul@xxxxxxxxxx> wrote:
>> > While having the ifdefs in the clocksource structure wasn't great, I'm
>> > not super excited about pushing all of this back into arch-specific
>> > code. The hope was that folks like ppc and ia64 would convert over from
>> > their own implementations to using more generic vread() implementations,
>> > or atleast new arches with vdso implementations would make use of it
>> > (possibly even allowing for a generic vdso gettime implementation).
>> > Are there at least some hard numbers that help justify this? Or maybe
>> > could you provide some thoughts on your future plans?
>> No numbers because there's no speedup (yet). Although I do want to
>> inline at least the TSC implementation eventually.
>> The real reason is security. Having vread be a function pointer
>> implies that userspace code can find that function at a fixed address,
>> which is a bad idea from a security POV (and I hope it's not even true
>> on any architecture except x86-64).
> Something to this effect should go into the change-log then.
>> The followup change (patch 5) changes vread on x86-64 to specify TSC,
> Oh, sorry, I didn't see the rest of the patchset. Apologies. :)
No problem. I guess I should have cc'd you on at least the interesting one.
>> HPET, or fallback to syscall, and the vDSO reads it and acts
>> accordingly. This is unfortunate in that it hardcodes assumptions
>> about the clocksources.
> Yea, that is unfortunate. Hmm.
>> The only other way I can think of to do it is to make the pointer
>> point into the vDSO. That would involve making it relative to
>> something in the vDSO, which would IMO be messier both in terms of
>> computing the pointer and in terms of calling whatever it points to.
> Hrm. I'm not super familiar with how the vDSO randomization works, so I
> can't really provide any informed insight here.
> But I'd def like to someday get the vDSO stuff to be as generic as
> possible. I already have some timekeeping changes I'd like to do which
> affect the update_vsyscall path. And that is a total pain to do, since I
> have to sync changes with x86, powerpc and ia64 (and the ia64 asm isn't
> something I'm likely to touch :) and get those changes in all at once,
> or introduce some redundant call or have lots of ifdef magic to keep
> compatibility while each arch adapts to the changes.
The vDSO is just like a regular DSO. It's a bunch of code that's the
same in every process, but it's mapped in a different place for each
process. The kernel knows how to find it if needed.
One idea: Add a directory linux/vDSO (i.e. a vDSO directory in the
root of the tree) that contains files that get compiled into the
vDSO). Then generic timekeeping code can go in there. That could
replace the duplicate clock_gettime implementation that currently
lives in the x86_64 vDSO, for example.
There could be a generic (or at least common) mechanism to compute a
"pointer" (i.e. some pointer-sized blob) to a vDSO function from the
kernel and another mechanism to resolve the pointer from the vDSO.
That pointer could go into vread.
Simpler idea: Make the clock_gettime implementation common (stick it
in a header, for example), but require the arch to supply functions to
check whether vread is available and to actually call vread.
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/