On Wed, 2007-07-04 at 18:10 +1000, Rusty Russell wrote: > On Wed, 2007-07-04 at 16:44 +1000, Tony Breeds wrote: > > Why bother installing an lguest_clock which is the same as jiffies? > > Wouldn't it be better to just use the system provided jiffies > > clocksource in the case where you haven't been provided with > > lguest_data.tsc_khz ? > > Yes, but jiffies is the lowest-rated clock (so PIT will get chosen). I > initially mugged clocksource_jiffies.rating, but that felt wrong: it's > currently not registered when this code runs so it's a simple > assignment, but if code order was to change it would have to be a call > to clocksource_change_rating(). > > There's an internal clocksource_override which I could use, but I'd have > to make it non-static. > > Maybe John has thoughts? I tend to prefer to have many simple clocksources then a few complex ones that try to handle everything. So adding the lguest clocksource, even if its the same as jiffies, isn't an issue to me. They're small anyway, and this allows you to add changes as needed w/o affecting the normal jiffies clocksource. Hijacking the rating value would work, but that further complicates the normal selection paths (which is already complex enough), so I'd avoid it. The last apprach of making boot_override_clocksource non-static and using it to force the clocksource wanted would work. But I think that opens it up too much for abuse. thanks -john _______________________________________________ Virtualization mailing list Virtualization@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/virtualization
