[patch 0/3] rtmutex: Propagate priority setting into lock chains

Andrew,

Please add the following patches to the rtmutex / pi-futex patchset.

This ensures that asynchronous setscheduler() calls are properly propagated
into a already blocked task's lock dependency chain.
The testsuite has also been improved to verify this behaviour.

	tglx

--

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

---

• Follow-Ups:
  • [patch 3/3] rtmutex: Modify rtmutex-tester to test the setscheduler propagation
    • From: Thomas Gleixner <[email protected]>
  • [patch 1/3] Drop tasklist lock in do_sched_setscheduler
    • From: Thomas Gleixner <[email protected]>
  • [patch 2/3] rtmutex: Propagate priority settings into PI lock chains
    • From: Thomas Gleixner <[email protected]>

• Prev by Date: [patch 2/3] rtmutex: Propagate priority settings into PI lock chains
• Next by Date: [patch 1/3] Drop tasklist lock in do_sched_setscheduler
• Previous by thread: [patch] lock validator: rtmutex unlock order annotation
• Next by thread: [patch 2/3] rtmutex: Propagate priority settings into PI lock chains
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]