Re: [PATCH 11/23] clocksource: atomic signals

2007-01-31 Thread Ingo Molnar
* Daniel Walker <[EMAIL PROTECTED]> wrote: > > I see little difference between your and John's code: both poll > > something - you poll an atomic "did a new clocksource arrive" flag > > in the timer interrupt, John takes the clocksource_lock spinlock and > > checks a "did a new clocksource arr

Re: [PATCH 11/23] clocksource: atomic signals

2007-01-31 Thread Daniel Walker
On Wed, 2007-01-31 at 12:07 +0100, Ingo Molnar wrote: > * Daniel Walker <[EMAIL PROTECTED]> wrote: > > > Modifies the way clocks are switched to in the timekeeping code. The > > original code would constantly monitor the clocksource list checking > > for newly added clocksources. I modified this

Re: [PATCH 11/23] clocksource: atomic signals

2007-01-31 Thread Ingo Molnar
* Daniel Walker <[EMAIL PROTECTED]> wrote: > Modifies the way clocks are switched to in the timekeeping code. The > original code would constantly monitor the clocksource list checking > for newly added clocksources. I modified this by using atomic types to > signal when a new clock is added.