[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20201118142002.GB279436@lothringen>
Date: Wed, 18 Nov 2020 15:20:02 +0100
From: Frederic Weisbecker <frederic@...nel.org>
To: Peter Zijlstra <peterz@...radead.org>
Cc: LKML <linux-kernel@...r.kernel.org>,
"Paul E . McKenney" <paulmck@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
Phil Auld <pauld@...hat.com>,
Marcelo Tosatti <mtosatti@...hat.com>
Subject: Re: [PATCH 0/5] context_tracking: Flatter archs not using
exception_enter/exit() v3
On Wed, Nov 18, 2020 at 03:05:03PM +0100, Peter Zijlstra wrote:
> On Wed, Nov 18, 2020 at 02:48:26PM +0100, Frederic Weisbecker wrote:
> > On Wed, Nov 18, 2020 at 08:39:47AM +0100, Peter Zijlstra wrote:
> > > On Tue, Nov 17, 2020 at 04:16:32PM +0100, Frederic Weisbecker wrote:
> > > > Frederic Weisbecker (5):
> > > > context_tracking: Introduce HAVE_CONTEXT_TRACKING_OFFSTACK
> > > > context_tracking: Don't implement exception_enter/exit() on CONFIG_HAVE_CONTEXT_TRACKING_OFFSTACK
> > > > sched: Detect call to schedule from critical entry code
> > > > context_tracking: Only define schedule_user() on !HAVE_CONTEXT_TRACKING_OFFSTACK archs
> > > > x86: Support HAVE_CONTEXT_TRACKING_OFFSTACK
> > >
> > > Thanks!
> > >
> > > Acked-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> >
> > Thanks! Probably this should go through your branches?
>
> Fair enough; these are now headed for tip/core/entry.
Thanks a lot! :)
Powered by blists - more mailing lists