Re: [PATCH -v5][RFC]: mutex: implement adaptive spinning

From: KAMEZAWA Hiroyuki
Date: Wed Jan 07 2009 - 21:50:33 EST


On Wed, 7 Jan 2009 21:33:31 -0500 (EST)
Steven Rostedt <rostedt@xxxxxxxxxxx> wrote:

>
> On Wed, 7 Jan 2009, Linus Torvalds wrote:
> > > Should that be:
> > >
> > > #if defined(CONFIG_DEBUG_PAGEALLOC) || defined(CONFIG_MEMORY_HOTPLUG)
> >
> > Well, probably CONFIG_MEMORY_HOTREMOVE, no? And I'd actually suggest that
> > unplugging should have a stop-machine if it doesn't already, just because
> > it's such a special case - like module removal.
>
> I do not think stop-machine will help, unless that spinning is protected
> by preempt-disable. If the task gets preempted after grabbing the owner
> thread_info, and then stop-machine runs, the memory disappears, the task
> is scheduled back, accesses the owner thread_info and then page-fault.
>
How about recording "cpu" into mutex at locking explicitly ?
too bad ?

-Kame

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/