From: Yury Norov <yury.norov@gmail.com>
To: Alex Belits <abelits@marvell.com>
Cc: yury.norov@gmail.com, "frederic@kernel.org" <frederic@kernel.org>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
"mingo@kernel.org" <mingo@kernel.org>,
"peterz@infradead.org" <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Prasun Kapoor <pkapoor@marvell.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"linux-mm@vger.kernel.org" <linux-mm@vger.kernel.org>,
"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>
Subject: Re: [PATCH 00/12] "Task_isolation" mode
Date: Tue, 21 Apr 2020 08:21:48 -0700 [thread overview]
Message-ID: <20200421152148.GA16576@yury-thinkpad> (raw)
> This is an update of task isolation work that was originally done by
> Chris Metcalf <cmetcalf@mellanox.com> and maintained by him until
> November 2017. It is adapted to the current kernel and cleaned up to
> make this functionality both more complete (as in, prevent isolation
> breaking in situations that were not covered before) and cleaner (as
> in, avoid any dubious or fragile use of kernel interfaces, and provide
> clean and reliable isolation breaking procedure).
>
> I guess, I have to explain why such a thing exists.
>
> ...
>
> My thanks to Chris Metcalf for design and maintenance of the original
> task isolation patch, Francis Giraldeau <francis.giraldeau@gmail.com>
> and Yuri Norov <ynorov@marvell.com> for various contributions to this
> work, and Frederic Weisbecker <frederic@kernel.org> for his work on
> CPU isolation and housekeeping that made possible to remove some less
> elegant solutions that I had to devise for earlier, <4.17 kernels.
>
> The previous patch (v16 by Chris Metcalf) is at:
>
> https://lore.kernel.org/lkml/1509728692-10460-1-git-send-email-cmetcalf@mellanox.com
Alex,
For patches that are not authored by you, you removed authors' SOB, like in
patch 8 of this series.
Please CC me for next revisions.
Thanks,
Yury
next reply other threads:[~2020-04-21 15:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-21 15:21 Yury Norov [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-03-04 16:01 [PATCH 00/12] "Task_isolation" mode Alex Belits
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200421152148.GA16576@yury-thinkpad \
--to=yury.norov@gmail.com \
--cc=4473787e1b6bc3cc226067e8d122092a678b63de.camel@marvell.com \
--cc=abelits@marvell.com \
--cc=frederic@kernel.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=pkapoor@marvell.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.