Re: [PATCH 13/39] NLKD/x86-64 - time adjustment

[Jan Beulich]

>The magic ICH6 HPET enable code has to go. It looks far too fragile and might 
>break something else. I also don't want direct PCI config space accesses like 
>this. We'll have to wait for ACPI HPET support I think. I think I'll remove 
>the original hack for AMD 8111 too - it was only for testing anyways. If you 
>still want to use it you have to keep it as a private patch.

That's fine with me. However, it was the only way for me to test the HPET code... It's not enabled anyway by default, but if you want the whole hack go away that's fine with me.

>Please remove the ifdefs too.  64bit HPET support would be fine, but 
>only as a runtime mechanism, not compile time.

This I added only for the purpose of not affecting existing code in existing configurations. If the code is generally acceptable, then I'll be more than happy to convert it.

>Can you remove debugger_jiffies please? 
>The code has to handle long delays anyways (e.g. if someone uses a target
>probe), so we cannot rely on such hacks anyways.

As above, I introduced this only to not affect existing code. If the added latency is no problem, then of course only the overflow safe code path should be kept, and then debugger_jiffies is completely unnecessary.

>I don't quite understand why the SMP case should be different from UP
>in that ifdef. Can you explain?  It shouldn't in theory.
>
>
>/* When the TSC gets reset during AP startup, the code below would
>+			   incorrectly think we lost a huge amount of ticks. */
>That is outdated - the TSCs are not reset anymore since 2.6.12.
>Please remove code for handling that.

Good to know, I didn't notice that. The conditional was so that the reset TSC would be considered a rolled-over one, resulting in a huge number of lost ticks.

>The union in vxtime_data is ugly - can it be avoided?

Yes, if the whole code is to become overflow-safe, then it'll just need to be a 64-bit field.

Jan

-
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/