Re: Inquiry: Should we remove "isolcpus= kernel boot option? (may have realtime uses)

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Dimitri Sivanich <sivanich@...>
Cc: Paul Jackson <pj@...>, <linux-kernel@...>, Con Kolivas <kernel@...>, Derek L. Fults <dfults@...>, devik <devik@...>, Dinakar Guniguntala <dino@...>, Emmanuel Pacaud <emmanuel.pacaud@...>, Frederik Deweerdt <deweerdt@...>, Ingo Molnar <mingo@...>, Matthew Dobson <colpatch@...>, Nick Piggin <nickpiggin@...>, <rostedt@...>, Oleg Nesterov <oleg@...>, Paul E. McKenney <paulmck@...>, Paul Menage <menage@...>, Peter Zijlstra <a.p.zijlstra@...>, Randy.Dunlap <rddunlap@...>, <suresh.b.siddha@...>, Thomas Gleixner <tglx@...>
Date: Tuesday, June 3, 2008 - 1:57 pm

Dimitri Sivanich wrote:
Nope. My patch was a trivial fix for not destroying scheduler domains on 
hotplug events. The problem you're seeing is different.

I'm not an expert in cpu hotplug internal machinery especially on ia64. Recent 
kernels (.22 and up) I've tried on x86 and x86-64 have no issues with cpu 
hotplug. You probably want to submit a bug report (in a separate thread) maybe 
it's a regression in the latest .26-rc series.

Max

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

Messages in current thread:
Re: Inquiry: Should we remove "isolcpus= kernel boot option?..., Michael Trimarchi, (Thu Jun 5, 10:57 am)
Re: Inquiry: Should we remove "isolcpus= kernel boot option?..., Max Krasnyanskiy, (Tue Jun 3, 1:57 pm)