Re: [patch 1/7] Immediate Values - Architecture Independent Code

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
From: Jason Baron
Date: Wednesday, February 27, 2008 - 10:01 am

On Tue, Feb 26, 2008 at 06:12:48PM -0500, Mathieu Desnoyers wrote:

yes. this is how stop_machine is implemented...and I believe is consistent with
the way in which your algorithm disables irqs. The logic to me, is we don't
want any cpus to see the kernel text in an inconsistent state via an irq.

-Jason

--
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[patch 1/7] Immediate Values - Architecture Independent Code, Mathieu Desnoyers, (Sat Feb 2, 2:08 pm)
Re: [patch 1/7] Immediate Values - Architecture Independen ..., Mathieu Desnoyers, (Tue Feb 26, 4:12 pm)
Re: [patch 1/7] Immediate Values - Architecture Independen ..., Mathieu Desnoyers, (Tue Feb 26, 4:34 pm)
Re: [patch 1/7] Immediate Values - Architecture Independen ..., Jason Baron, (Wed Feb 27, 10:01 am)
Re: [patch 1/7] Immediate Values - Architecture Independen ..., Mathieu Desnoyers, (Wed Feb 27, 12:05 pm)
[patch 1/2] add ALL_CPUS option to stop_machine_run(), Jason Baron, (Thu Feb 28, 9:33 am)
Re: [patch 1/2] add ALL_CPUS option to stop_machine_run(), Max Krasnyanskiy, (Thu Feb 28, 3:09 pm)
Re: [patch 1/2] add ALL_CPUS option to stop_machine_run(), Mathieu Desnoyers, (Thu Feb 28, 3:14 pm)
Re: [patch 2/2] implement immediate updating via stop_mach ..., Mathieu Desnoyers, (Fri Feb 29, 6:43 am)
Re: [patch 1/2] add ALL_CPUS option to stop_machine_run(), Max Krasnyanskiy, (Fri Feb 29, 11:24 am)
Re: [patch 1/2] add ALL_CPUS option to stop_machine_run(), Max Krasnyanskiy, (Fri Feb 29, 12:58 pm)
Re: [patch 1/2] add ALL_CPUS option to stop_machine_run(), Max Krasnyanskiy, (Mon Mar 3, 5:30 pm)
Re: [patch 1/2] add ALL_CPUS option to stop_machine_run(), Max Krasnyansky, (Mon Mar 3, 9:11 pm)