[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <878sarn36h.fsf@nanos.tec.linutronix.de>
Date: Mon, 23 Nov 2020 23:01:10 +0100
From: Thomas Gleixner <tglx@...utronix.de>
To: Alex Belits <abelits@...vell.com>,
"nitesh\@redhat.com" <nitesh@...hat.com>,
"frederic\@kernel.org" <frederic@...nel.org>
Cc: Prasun Kapoor <pkapoor@...vell.com>,
"linux-api\@vger.kernel.org" <linux-api@...r.kernel.org>,
"davem\@davemloft.net" <davem@...emloft.net>,
"trix\@redhat.com" <trix@...hat.com>,
"mingo\@kernel.org" <mingo@...nel.org>,
"catalin.marinas\@arm.com" <catalin.marinas@....com>,
"rostedt\@goodmis.org" <rostedt@...dmis.org>,
"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>,
"peterx\@redhat.com" <peterx@...hat.com>,
"linux-arch\@vger.kernel.org" <linux-arch@...r.kernel.org>,
"mtosatti\@redhat.com" <mtosatti@...hat.com>,
"will\@kernel.org" <will@...nel.org>,
"peterz\@infradead.org" <peterz@...radead.org>,
"leon\@sidebranch.com" <leon@...ebranch.com>,
"linux-arm-kernel\@lists.infradead.org"
<linux-arm-kernel@...ts.infradead.org>,
"pauld\@redhat.com" <pauld@...hat.com>,
"netdev\@vger.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [PATCH v5 3/9] task_isolation: userspace hard isolation from kernel
Alex,
On Mon, Nov 23 2020 at 17:56, Alex Belits wrote:
> .../admin-guide/kernel-parameters.txt | 6 +
> drivers/base/cpu.c | 23 +
> include/linux/hrtimer.h | 4 +
> include/linux/isolation.h | 326 ++++++++
> include/linux/sched.h | 5 +
> include/linux/tick.h | 3 +
> include/uapi/linux/prctl.h | 6 +
> init/Kconfig | 27 +
> kernel/Makefile | 2 +
> kernel/isolation.c | 714 ++++++++++++++++++
> kernel/signal.c | 2 +
> kernel/sys.c | 6 +
> kernel/time/hrtimer.c | 27 +
> kernel/time/tick-sched.c | 18 +
I asked you before to split this up into bits and pieces and argue and
justify each change. Throwing this wholesale over the fence is going
nowhere. It's not revieable at all.
Aside of that ignoring review comments is a sure path to make yourself
ignored:
> +/*
> + * Logging
> + */
> +int task_isolation_message(int cpu, int level, bool supp, const char *fmt, ...);
> +
> +#define pr_task_isol_emerg(cpu, fmt, ...) \
> + task_isolation_message(cpu, LOGLEVEL_EMERG, false, fmt, ##__VA_ARGS__)
The comments various people made about that are not going away and none
of this is going near anything I'm responsible for unless you provide
these independent of the rest and with a reasonable justification why
you can't use any other existing mechanism or extend it for your use
case.
Thanks,
tglx
Powered by blists - more mailing lists