Luck, Tony wrote:
I'm guessing here ... I haven't cross-checked with the architects.I'll be glad if we can get a comment from Intel's architects.I talked this through with an architect, and I'm right. In the sequence: ld4.acq rM = [rN] ;; mov rP = ar.itc there are no dependencies, so the read of ar.itc can occur "IMMEDIATELY after the load issues". Consuming the result of the load in between will create a dependency ... so the timestamp will be taken as we want it, after the load. So I can apply this patch (moving the "and r28 = ~1,r28").
Thank you for checking it.
What other time patches are you still pushing? The time interpolator changes that were predicted still look like they are pending somewhere (kernel/timer.c hasn't been changed). -Tony
I don't know the current status of Bob's patches... I hope you don't mind applying my small patches before Bob's. Here are 2 pending patches I'm pushing : - [PATCH] ia64: Scalability improvement of gettimeofday with jitter compensation - [PATCH] fsys_gettimeofday leaps days if it runs with nojitter I confirmed that these 2 can be applied to 2.6.22 (with some offset). Let me know if you need refreshed ones. Thanks, H.Seto - To unsubscribe from this list: send the line "unsubscribe linux-ia64" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
![]() |