Re: [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
On Wed, 2006-12-20 at 14:26 -0500, [EMAIL PROTECTED] wrote: > On Tue, 19 Dec 2006 20:20:39 EST, john stultz said: > > I didn't hear any objections (or really, any comments) on my > > last release, so as I mentioned then, I want to go ahead and push this > > to Andrew for a bit of testing in -mm. Hopefully targeting for > > inclusion in 2.6.21 or 2.6.22. > > Am running it on a Dell Latitude D820 (Core2 T7200 cpu). I had to un-do > 4 conflicting patches in -rc1-mm1 and then it applied and ran clean, I still > need to look at re-merging them: Doh. Oh right, I should have checked against -mm for conflicts. > hpet-avoid-warning-message-livelock.patch > clockevents-i386-hpet-driver.patch > get-rid-of-arch_have_xtime_lock.patch > x86_64-mm-amd-tsc-sync.patch > > It *looks* like all the pieces are there except a few lines of Kconfig > magic to wire up the dynticks/NO_HZ stuff - or did I miss something crucial? Yea, I will rework the patches ontop of -mm. thanks -john - 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/
Re: [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
On Tue, 19 Dec 2006 20:20:39 EST, john stultz said: > I didn't hear any objections (or really, any comments) on my > last release, so as I mentioned then, I want to go ahead and push this > to Andrew for a bit of testing in -mm. Hopefully targeting for > inclusion in 2.6.21 or 2.6.22. Am running it on a Dell Latitude D820 (Core2 T7200 cpu). I had to un-do 4 conflicting patches in -rc1-mm1 and then it applied and ran clean, I still need to look at re-merging them: hpet-avoid-warning-message-livelock.patch clockevents-i386-hpet-driver.patch get-rid-of-arch_have_xtime_lock.patch x86_64-mm-amd-tsc-sync.patch It *looks* like all the pieces are there except a few lines of Kconfig magic to wire up the dynticks/NO_HZ stuff - or did I miss something crucial? pgpVKaySpQIdY.pgp Description: PGP signature
Re: [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
On Tue, 19 Dec 2006 20:20:39 EST, john stultz said: I didn't hear any objections (or really, any comments) on my last release, so as I mentioned then, I want to go ahead and push this to Andrew for a bit of testing in -mm. Hopefully targeting for inclusion in 2.6.21 or 2.6.22. Am running it on a Dell Latitude D820 (Core2 T7200 cpu). I had to un-do 4 conflicting patches in -rc1-mm1 and then it applied and ran clean, I still need to look at re-merging them: hpet-avoid-warning-message-livelock.patch clockevents-i386-hpet-driver.patch get-rid-of-arch_have_xtime_lock.patch x86_64-mm-amd-tsc-sync.patch It *looks* like all the pieces are there except a few lines of Kconfig magic to wire up the dynticks/NO_HZ stuff - or did I miss something crucial? pgpVKaySpQIdY.pgp Description: PGP signature
Re: [PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
On Wed, 2006-12-20 at 14:26 -0500, [EMAIL PROTECTED] wrote: On Tue, 19 Dec 2006 20:20:39 EST, john stultz said: I didn't hear any objections (or really, any comments) on my last release, so as I mentioned then, I want to go ahead and push this to Andrew for a bit of testing in -mm. Hopefully targeting for inclusion in 2.6.21 or 2.6.22. Am running it on a Dell Latitude D820 (Core2 T7200 cpu). I had to un-do 4 conflicting patches in -rc1-mm1 and then it applied and ran clean, I still need to look at re-merging them: Doh. Oh right, I should have checked against -mm for conflicts. hpet-avoid-warning-message-livelock.patch clockevents-i386-hpet-driver.patch get-rid-of-arch_have_xtime_lock.patch x86_64-mm-amd-tsc-sync.patch It *looks* like all the pieces are there except a few lines of Kconfig magic to wire up the dynticks/NO_HZ stuff - or did I miss something crucial? Yea, I will rework the patches ontop of -mm. thanks -john - 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/
[PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
Andrew, Andi, I didn't hear any objections (or really, any comments) on my last release, so as I mentioned then, I want to go ahead and push this to Andrew for a bit of testing in -mm. Hopefully targeting for inclusion in 2.6.21 or 2.6.22. Here's the performance data from the last release: Vanilla TSC: 149 nsecs per gtod call 367 nsecs per CLOCK_MONOTONIC call 288 nsecs per CLOCK_REALTIME call Vanilla ACPI PM: 1272 nsecs per gtod call 1335 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call GENERIC_TIME TSC: 149 nsecs per gtod call 304 nsecs per CLOCK_MONOTONIC call 275 nsecs per CLOCK_REALTIME call GENERIC_TIME ACPI PM: 1273 nsecs per gtod call 1275 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call So almost no performance change. New in the current C8 release: o Synced up w/ 2.6.20-rc1 o Added a few small cleanups from Ingo Let me know if you have any thoughts or comments! thanks again! -john - 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/
[PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
Andrew, Andi, I didn't hear any objections (or really, any comments) on my last release, so as I mentioned then, I want to go ahead and push this to Andrew for a bit of testing in -mm. Hopefully targeting for inclusion in 2.6.21 or 2.6.22. Here's the performance data from the last release: Vanilla TSC: 149 nsecs per gtod call 367 nsecs per CLOCK_MONOTONIC call 288 nsecs per CLOCK_REALTIME call Vanilla ACPI PM: 1272 nsecs per gtod call 1335 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call GENERIC_TIME TSC: 149 nsecs per gtod call 304 nsecs per CLOCK_MONOTONIC call 275 nsecs per CLOCK_REALTIME call GENERIC_TIME ACPI PM: 1273 nsecs per gtod call 1275 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call So almost no performance change. New in the current C8 release: o Synced up w/ 2.6.20-rc1 o Added a few small cleanups from Ingo Let me know if you have any thoughts or comments! thanks again! -john - 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/
[PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
Hey Andi, First let me apologize, I've been busy with other things and its been far too long since I last posted this. Anyway, I found some time to resync my trees and wanted to send this along. You had asked earlier about performance impact: Vanilla TSC: 149 nsecs per gtod call 367 nsecs per CLOCK_MONOTONIC call 288 nsecs per CLOCK_REALTIME call Vanilla ACPI PM: 1272 nsecs per gtod call 1335 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call GENERIC_TIME TSC: 149 nsecs per gtod call 304 nsecs per CLOCK_MONOTONIC call 275 nsecs per CLOCK_REALTIME call GENERIC_TIME ACPI PM: 1273 nsecs per gtod call 1275 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call So almost no performance change. Ingo has a few cleanups I need to merge, but otherwise I think this is getting close to ready for inclusion into -mm for testing. Please let me know if you have any major objections and if not I'll re-diff it against -mm and send it to Andrew. New in the current C7 release: o Synched up w/ 2.6.19-rc6-git11 o Reworked the patch order to be a bit more logical o Dropped the apic_runs_main_timer removal on Andi's request Let me know if you have any thoughts or comments! thanks again! -john - 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/
[PATCH 0/5][time][x86_64] GENERIC_TIME patchset for x86_64
Hey Andi, First let me apologize, I've been busy with other things and its been far too long since I last posted this. Anyway, I found some time to resync my trees and wanted to send this along. You had asked earlier about performance impact: Vanilla TSC: 149 nsecs per gtod call 367 nsecs per CLOCK_MONOTONIC call 288 nsecs per CLOCK_REALTIME call Vanilla ACPI PM: 1272 nsecs per gtod call 1335 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call GENERIC_TIME TSC: 149 nsecs per gtod call 304 nsecs per CLOCK_MONOTONIC call 275 nsecs per CLOCK_REALTIME call GENERIC_TIME ACPI PM: 1273 nsecs per gtod call 1275 nsecs per CLOCK_MONOTONIC call 1273 nsecs per CLOCK_REALTIME call So almost no performance change. Ingo has a few cleanups I need to merge, but otherwise I think this is getting close to ready for inclusion into -mm for testing. Please let me know if you have any major objections and if not I'll re-diff it against -mm and send it to Andrew. New in the current C7 release: o Synched up w/ 2.6.19-rc6-git11 o Reworked the patch order to be a bit more logical o Dropped the apic_runs_main_timer removal on Andi's request Let me know if you have any thoughts or comments! thanks again! -john - 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/
