[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAB0TPYFtrvfA1NrqwgygbpqyE6G5OjNe5Gch-p+58T0Cmr7OdQ@mail.gmail.com>
Date: Thu, 16 Nov 2017 10:31:25 +0100
From: Martijn Coenen <maco@...roid.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Greg KH <gregkh@...uxfoundation.org>,
John Stultz <john.stultz@...aro.org>,
Todd Kjos <tkjos@...gle.com>,
Arve Hjønnevåg <arve@...roid.com>,
Sherry Yang <sherryy@...roid.com>,
Thomas Gleixner <tglx@...utronix.de>,
Amit Pundir <amit.pundir@...aro.org>,
LKML <linux-kernel@...r.kernel.org>, devel@...verdev.osuosl.org,
Martijn Coenen <maco@...gle.com>
Subject: Re: [PATCH v3 3/6] ANDROID: binder: improve priority inheritance.
On Wed, Nov 15, 2017 at 2:03 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> On Thu, Oct 26, 2017 at 04:07:47PM +0200, Martijn Coenen wrote:
>> By raising the priority of a thread selected for
>> a transaction *before* we wake it up.
>>
>> Delay restoring the priority when doing a reply
>> until after we wake-up the process receiving
>> the reply.
>
> What happens if a thread dies?
Binder threads should never exit, but if they do, the whole process
exits. Anyway in that case we still restore the priority of this
thread - it's in the error path in the "@@ -3328,6 +3369,7 @@"
section.
Powered by blists - more mailing lists