[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMAWPa9c6kBdJC3n5q=fCD6gEPhGgFCqN_7TS-_-WLjo5_seRA@mail.gmail.com>
Date: Tue, 11 Aug 2015 14:32:16 -0700
From: Kevin Hilman <khilman@...nel.org>
To: Andy Lutomirski <luto@...capital.net>
Cc: "ksummit-discuss@...ts.linuxfoundation.org"
<ksummit-discuss@...ts.linuxfoundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Paul McKenney <paulmck@...ux.vnet.ibm.com>,
Christoph Lameter <cl@...ux.com>,
Frédéric Weisbecker <fweisbec@...il.com>,
Ingo Molnar <mingo@...nel.org>,
Thomas Gleixner <tglx@...utronix.de>,
"H. Peter Anvin" <hpa@...or.com>,
Peter Zijlstra <peterz@...radead.org>,
Chris Metcalf <cmetcalf@...hip.com>,
Rik van Riel <riel@...hat.com>
Subject: Re: [BELATED CORE TOPIC] context tracking / nohz / RCU state
On Tue, Aug 11, 2015 at 10:49 AM, Andy Lutomirski <luto@...capital.net> wrote:
> This is a bit late, but here goes anyway.
>
> Having played with the x86 context tracking hooks for awhile, I think
> it would be nice if core code that needs to be aware of CPU context
> (kernel, user, idle, guest, etc) could come up with single,
> comprehensible, easily validated set of hooks that arch code is
> supposed to call.
Having worked on both the arm and arm64 implementations of context
tracking, I'm interested in this as well.
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists