lkml.org 
[lkml]   [2006]   [Jun]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [patch 2/3] rtmutex: Propagate priority settings into PI lock chains
    On Thu, 22 Jun 2006 10:20:59 -0400 (EDT)
    Steven Rostedt <rostedt@goodmis.org> wrote:

    > > + if (!waiter || waiter->list_entry.prio == task->prio) {
    > > + spin_unlock_irqrestore(&task->pi_lock, flags);
    > > + return;
    > > + }
    > > +
    > > + /* gets dropped in rt_mutex_adjust_prio_chain()! */
    > > + get_task_struct(task);
    > > + spin_unlock_irqrestore(&task->pi_lock, flags);
    > > +
    > > + rt_mutex_adjust_prio_chain(task, 0, NULL, NULL, task);
    >
    > The above means that you cant ever call sched_setscheduler from a
    > interrupt handler (or softirq). The rt_mutex_adjust_prio_chain since that
    > grabs wait_lock which is not for interrupt use.

    Running setscheduler() from IRQ context sounds rather perverse.
    BUG_ON(in_interrupt()) would reduce the temptation.
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-06-23 04:11    [W:0.024 / U:64.556 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site