Re: [PATCH 1/2] non-string based tsc unstable reasons

2007-05-25 Thread Daniel Walker
On Fri, 2007-05-25 at 23:05 +0200, Andi Kleen wrote: > On Fri, May 25, 2007 at 12:32:10PM -0700, Daniel Walker wrote: > > Just passing a string to mark_tsc_unstable() doesn't allow real code to > > change > > based on the reason for the instablility. I changed mark_tsc_unstable() > > to accept a s

Re: [PATCH 1/2] non-string based tsc unstable reasons

2007-05-25 Thread Andi Kleen
On Fri, May 25, 2007 at 12:32:10PM -0700, Daniel Walker wrote: > Just passing a string to mark_tsc_unstable() doesn't allow real code to change > based on the reason for the instablility. I changed mark_tsc_unstable() > to accept a string and a flag which denotes a general reason why the tsc > is u

Re: [PATCH 1/2] non-string based tsc unstable reasons

2007-05-12 Thread Daniel Walker
On Sat, 2007-05-12 at 20:56 +0200, Andi Kleen wrote: > On Saturday 12 May 2007 17:43:45 Daniel Walker wrote: > > Just passing a string to mark_tsc_unstable() doesn't allow real code to > > change > > based on the reason for the instablility. I changed mark_tsc_unstable() > > to accept a string and

Re: [PATCH 1/2] non-string based tsc unstable reasons

2007-05-12 Thread Andi Kleen
On Saturday 12 May 2007 17:43:45 Daniel Walker wrote: > Just passing a string to mark_tsc_unstable() doesn't allow real code to change > based on the reason for the instablility. I changed mark_tsc_unstable() > to accept a string and a flag which denotes a general reason why the tsc > is unstable,