[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878rrxnd48.fsf@email.froward.int.ebiederm.org>
Date: Fri, 22 Apr 2022 14:15:35 -0500
From: "Eric W. Biederman" <ebiederm@...ssion.com>
To: Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Cc: Peter Zijlstra <peterz@...radead.org>, rjw@...ysocki.net,
oleg@...hat.com, mingo@...nel.org, vincent.guittot@...aro.org,
dietmar.eggemann@....com, rostedt@...dmis.org, mgorman@...e.de,
Will Deacon <will@...nel.org>, linux-kernel@...r.kernel.org,
tj@...nel.org, linux-pm@...r.kernel.org
Subject: Re: [PATCH v2 0/5] ptrace-vs-PREEMPT_RT and freezer rewrite
Sebastian Andrzej Siewior <bigeasy@...utronix.de> writes:
> On 2022-04-21 17:02:48 [+0200], Peter Zijlstra wrote:
>> Find here a new posting of the ptrace and freezer patches :-)
>>
>> The majority of the changes are in patch 2, which with much feedback from Oleg
>> and Eric has changed lots.
>>
>> I'm hoping we're converging on something agreeable.
>
> I tested this under RT (had to remove the preempt-disable section in
> ptrace_stop()) with ssdd [0]. It forks a few tasks and then
> PTRACE_SINGLESTEPs them for a few iterations.
Out of curiosity why did you need to remove the preempt_disable section
on PREEMPT_RT? It should have lasted for just a moment until schedule
was called.
Eric
Powered by blists - more mailing lists