[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3ff1383e669b543462737b0d12c0d1fb7d409e3e.camel@marvell.com>
Date: Thu, 23 Jul 2020 16:50:37 +0000
From: Alex Belits <abelits@...vell.com>
To: "peterz@...radead.org" <peterz@...radead.org>
CC: "davem@...emloft.net" <davem@...emloft.net>,
Prasun Kapoor <pkapoor@...vell.com>,
"mingo@...nel.org" <mingo@...nel.org>,
"linux-api@...r.kernel.org" <linux-api@...r.kernel.org>,
"rostedt@...dmis.org" <rostedt@...dmis.org>,
"frederic@...nel.org" <frederic@...nel.org>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"catalin.marinas@....com" <catalin.marinas@....com>,
"linux-arch@...r.kernel.org" <linux-arch@...r.kernel.org>,
"will@...nel.org" <will@...nel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>
Subject: Re: [PATCH v4 00/13] "Task_isolation" mode
On Thu, 2020-07-23 at 17:49 +0200, Peter Zijlstra wrote:
>
> 'What does noinstr mean? and why do we have it" -- don't dare touch
> the
> entry code until you can answer that.
noinstr disables instrumentation, so there would not be calls and
dependencies on other parts of the kernel when it's not yet safe to
call them. Relevant functions already have it, and I add an inline call
to perform flags update and synchronization. Unless something else is
involved, those operations are safe, so I am not adding anything that
can break those.
--
Alex
Powered by blists - more mailing lists