[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <87zgk7x93h.ffs@tglx>
Date: Wed, 27 Apr 2022 09:45:54 +0200
From: Thomas Gleixner <tglx@...utronix.de>
To: Marcelo Tosatti <mtosatti@...hat.com>, linux-kernel@...r.kernel.org
Cc: Nitesh Lal <nilal@...hat.com>,
Nicolas Saenz Julienne <nsaenzju@...hat.com>,
Frederic Weisbecker <frederic@...nel.org>,
Christoph Lameter <cl@...ux.com>,
Juri Lelli <juri.lelli@...hat.com>,
Peter Zijlstra <peterz@...radead.org>,
Alex Belits <abelits@...its.com>, Peter Xu <peterx@...hat.com>,
Daniel Bristot de Oliveira <bristot@...hat.com>,
Oscar Shiang <oscar0225@...email.tw>,
Marcelo Tosatti <mtosatti@...hat.com>
Subject: Re: [patch v12 13/13] task isolation: only TIF_TASK_ISOL if task
isolation is enabled
On Tue, Mar 15 2022 at 12:31, Marcelo Tosatti wrote:
$Subject does not qualify as a parseable sentence.
> This avoids processing of TIF_TASK_ISOL, when returning to userspace,
> for tasks which do not have task isolation configured.
That's how kernel development works, right:
1) Add half baken stuff
2) Apply duct tape on top
You know exactly, that this is _not_ the way it works.
This whole thing is half thought out tinkerware with [ill|un]defined
semantics.
Thanks,
tglx
Powered by blists - more mailing lists