All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Alex Belits <abelits@marvell.com>
Cc: "trix@redhat.com" <trix@redhat.com>,
	Prasun Kapoor <pkapoor@marvell.com>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"peterx@redhat.com" <peterx@redhat.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"nitesh@redhat.com" <nitesh@redhat.com>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	"will@kernel.org" <will@kernel.org>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"frederic@kernel.org" <frederic@kernel.org>,
	"leon@sidebranch.com" <leon@sidebranch.com>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"pauld@redhat.com" <pauld@redhat.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [EXT] Re: [PATCH v5 0/9] "Task_isolation" mode
Date: Wed, 2 Dec 2020 14:02:33 +0000	[thread overview]
Message-ID: <20201202140233.GB66958@C02TD0UTHF1T.local> (raw)
In-Reply-To: <a31f81cfa62936ff5edc420be63a5ac0b318b594.camel@marvell.com>

On Tue, Nov 24, 2020 at 05:40:49PM +0000, Alex Belits wrote:
> 
> On Tue, 2020-11-24 at 08:36 -0800, Tom Rix wrote:
> > External Email
> > 
> > -------------------------------------------------------------------
> > ---
> > 
> > On 11/23/20 9:42 AM, Alex Belits wrote:
> > > 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
> > > implement its functionality in a more complete and cleaner manner.
> > 
> > I am having problems applying the patchset to today's linux-next.
> > 
> > Which kernel should I be using ?
> 
> The patches are against Linus' tree, in particular, commit
> a349e4c659609fd20e4beea89e5c4a4038e33a95

Is there any reason to base on that commit in particular?

Generally it's preferred that a series is based on a tag (so either a
release or an -rc kernel), and that the cover letter explains what the
base is. If you can do that in future it'll make the series much easier
to work with.

Thanks,
Mark.

WARNING: multiple messages have this Message-ID (diff)
From: Mark Rutland <mark.rutland@arm.com>
To: Alex Belits <abelits@marvell.com>
Cc: "linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	"nitesh@redhat.com" <nitesh@redhat.com>,
	"pauld@redhat.com" <pauld@redhat.com>,
	"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
	"peterz@infradead.org" <peterz@infradead.org>,
	"trix@redhat.com" <trix@redhat.com>,
	"frederic@kernel.org" <frederic@kernel.org>,
	"mtosatti@redhat.com" <mtosatti@redhat.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"rostedt@goodmis.org" <rostedt@goodmis.org>,
	"davem@davemloft.net" <davem@davemloft.net>,
	"leon@sidebranch.com" <leon@sidebranch.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"peterx@redhat.com" <peterx@redhat.com>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	Prasun Kapoor <pkapoor@marvell.com>,
	"tglx@linutronix.de" <tglx@linutronix.de>,
	"will@kernel.org" <will@kernel.org>,
	"mingo@kernel.org" <mingo@kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [EXT] Re: [PATCH v5 0/9] "Task_isolation" mode
Date: Wed, 2 Dec 2020 14:02:33 +0000	[thread overview]
Message-ID: <20201202140233.GB66958@C02TD0UTHF1T.local> (raw)
In-Reply-To: <a31f81cfa62936ff5edc420be63a5ac0b318b594.camel@marvell.com>

On Tue, Nov 24, 2020 at 05:40:49PM +0000, Alex Belits wrote:
> 
> On Tue, 2020-11-24 at 08:36 -0800, Tom Rix wrote:
> > External Email
> > 
> > -------------------------------------------------------------------
> > ---
> > 
> > On 11/23/20 9:42 AM, Alex Belits wrote:
> > > 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
> > > implement its functionality in a more complete and cleaner manner.
> > 
> > I am having problems applying the patchset to today's linux-next.
> > 
> > Which kernel should I be using ?
> 
> The patches are against Linus' tree, in particular, commit
> a349e4c659609fd20e4beea89e5c4a4038e33a95

Is there any reason to base on that commit in particular?

Generally it's preferred that a series is based on a tag (so either a
release or an -rc kernel), and that the cover letter explains what the
base is. If you can do that in future it'll make the series much easier
to work with.

Thanks,
Mark.

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-12-02 14:03 UTC|newest]

Thread overview: 74+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 17:42 [PATCH v5 0/9] "Task_isolation" mode Alex Belits
2020-11-23 17:42 ` Alex Belits
2020-11-23 17:56 ` [PATCH v5 1/9] task_isolation: vmstat: add quiet_vmstat_sync function Alex Belits
2020-11-23 17:56   ` Alex Belits
2020-11-23 21:48   ` Thomas Gleixner
2020-11-23 21:48     ` Thomas Gleixner
2020-11-23 17:56 ` [PATCH v5 2/9] task_isolation: vmstat: add vmstat_idle function Alex Belits
2020-11-23 17:56   ` Alex Belits
2020-11-23 21:49   ` Thomas Gleixner
2020-11-23 21:49     ` Thomas Gleixner
2020-11-23 17:56 ` [PATCH v5 3/9] task_isolation: userspace hard isolation from kernel Alex Belits
2020-11-23 17:56   ` Alex Belits
2020-11-23 22:01   ` Thomas Gleixner
2020-11-23 22:01     ` Thomas Gleixner
2020-11-23 17:57 ` [PATCH v5 4/9] task_isolation: Add task isolation hooks to arch-independent code Alex Belits
2020-11-23 17:57   ` Alex Belits
2020-11-23 22:31   ` Thomas Gleixner
2020-11-23 22:31     ` Thomas Gleixner
2020-11-23 17:57 ` [PATCH v5 5/9] task_isolation: Add driver-specific hooks Alex Belits
2020-11-23 17:57   ` Alex Belits
2020-12-02 14:18   ` Mark Rutland
2020-12-02 14:18     ` Mark Rutland
2020-12-04  0:43     ` [EXT] " Alex Belits
2020-12-04  0:43       ` Alex Belits
2020-11-23 17:58 ` [PATCH v5 6/9] task_isolation: arch/arm64: enable task isolation functionality Alex Belits
2020-11-23 17:58   ` Alex Belits
2020-12-02 13:59   ` Mark Rutland
2020-12-02 13:59     ` Mark Rutland
2020-12-04  0:37     ` [EXT] " Alex Belits
2020-12-04  0:37       ` Alex Belits
2020-12-07 11:57       ` Mark Rutland
2020-12-07 11:57         ` Mark Rutland
2020-11-23 17:58 ` [PATCH v5 7/9] task_isolation: don't interrupt CPUs with tick_nohz_full_kick_cpu() Alex Belits
2020-11-23 17:58   ` Alex Belits
2020-11-23 22:13   ` Frederic Weisbecker
2020-11-23 22:13     ` Frederic Weisbecker
2020-11-23 22:35     ` Alex Belits
2020-11-23 22:35       ` Alex Belits
2020-11-23 22:36   ` Thomas Gleixner
2020-11-23 22:36     ` Thomas Gleixner
2020-12-02 14:20   ` Mark Rutland
2020-12-02 14:20     ` Mark Rutland
2020-12-04  0:54     ` [EXT] " Alex Belits
2020-12-04  0:54       ` Alex Belits
2020-12-07 11:58       ` Mark Rutland
2020-12-07 11:58         ` Mark Rutland
2020-11-23 17:58 ` [PATCH v5 8/9] task_isolation: ringbuffer: don't interrupt CPUs running isolated tasks on buffer resize Alex Belits
2020-11-23 17:58   ` Alex Belits
2020-11-23 17:58 ` [PATCH v5 9/9] task_isolation: kick_all_cpus_sync: don't kick isolated cpus Alex Belits
2020-11-23 17:58   ` Alex Belits
2020-11-23 22:29   ` Frederic Weisbecker
2020-11-23 22:29     ` Frederic Weisbecker
2020-11-23 22:39     ` [EXT] " Alex Belits
2020-11-23 22:39       ` Alex Belits
2020-11-23 23:21       ` Frederic Weisbecker
2020-11-23 23:21         ` Frederic Weisbecker
2020-11-25  3:20         ` Alex Belits
2020-11-25  3:20           ` Alex Belits
2021-01-22 15:00         ` Marcelo Tosatti
2021-01-22 15:00           ` Marcelo Tosatti
2020-11-24 16:36 ` [PATCH v5 0/9] "Task_isolation" mode Tom Rix
2020-11-24 16:36   ` Tom Rix
2020-11-24 17:40   ` [EXT] " Alex Belits
2020-11-24 17:40     ` Alex Belits
2020-12-02 14:02     ` Mark Rutland [this message]
2020-12-02 14:02       ` Mark Rutland
2020-12-04  0:39       ` Alex Belits
2020-12-04  0:39         ` Alex Belits
2020-12-05 20:40 ` Pavel Machek
2020-12-05 20:40   ` Pavel Machek
2020-12-05 23:25   ` Thomas Gleixner
2020-12-05 23:25     ` Thomas Gleixner
2020-12-11 18:08     ` Yury Norov
2020-12-11 18:08       ` Yury Norov

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=20201202140233.GB66958@C02TD0UTHF1T.local \
    --to=mark.rutland@arm.com \
    --cc=abelits@marvell.com \
    --cc=catalin.marinas@arm.com \
    --cc=davem@davemloft.net \
    --cc=frederic@kernel.org \
    --cc=leon@sidebranch.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=nitesh@redhat.com \
    --cc=pauld@redhat.com \
    --cc=peterx@redhat.com \
    --cc=peterz@infradead.org \
    --cc=pkapoor@marvell.com \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --cc=trix@redhat.com \
    --cc=will@kernel.org \
    /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.