From: Kevin Hilman <khilman@kernel.org>
To: Andy Lutomirski <luto@amacapital.net>
Cc: "ksummit-discuss@lists.linuxfoundation.org"
<ksummit-discuss@lists.linuxfoundation.org>,
Peter Zijlstra <peterz@infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Chris Metcalf <cmetcalf@ezchip.com>,
Christoph Lameter <cl@linux.com>, Ingo Molnar <mingo@kernel.org>
Subject: Re: [Ksummit-discuss] [BELATED CORE TOPIC] context tracking / nohz / RCU state
Date: Tue, 11 Aug 2015 14:32:16 -0700 [thread overview]
Message-ID: <CAMAWPa9c6kBdJC3n5q=fCD6gEPhGgFCqN_7TS-_-WLjo5_seRA@mail.gmail.com> (raw)
In-Reply-To: <CALCETrW7OiEYFm9FLbC_pnRLMvwb0nTKRWRDMXB3PMc_0H+UoA@mail.gmail.com>
On Tue, Aug 11, 2015 at 10:49 AM, Andy Lutomirski <luto@amacapital.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
next prev parent reply other threads:[~2015-08-11 21:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 17:49 Andy Lutomirski
2015-08-11 18:33 ` Paul E. McKenney
2015-08-11 19:07 ` Andy Lutomirski
2015-08-11 21:47 ` Paul E. McKenney
2015-08-11 21:52 ` Andy Lutomirski
2015-08-12 0:51 ` Paul E. McKenney
2015-08-12 1:16 ` Andy Lutomirski
2015-08-12 13:38 ` Paul E. McKenney
2015-08-12 14:52 ` Frederic Weisbecker
2015-08-12 14:38 ` Frederic Weisbecker
2015-08-12 15:59 ` Paul E. McKenney
2015-08-11 18:42 ` Luis R. Rodriguez
2015-08-11 21:50 ` Paul E. McKenney
2015-08-12 20:17 ` Luis R. Rodriguez
2015-08-12 14:27 ` Frederic Weisbecker
2015-08-12 16:03 ` Paul E. McKenney
2015-08-13 1:29 ` Lai Jiangshan
2015-08-13 13:07 ` Frederic Weisbecker
2015-08-13 13:03 ` Frederic Weisbecker
2015-08-11 19:31 ` josh
2015-08-11 21:32 ` Kevin Hilman [this message]
2015-08-12 3:56 ` Lai Jiangshan
2015-08-12 14:20 ` Frederic Weisbecker
2015-10-12 18:40 ` Theodore Ts'o
2015-10-12 19:55 ` Thomas Gleixner
2015-10-12 20:40 ` Paul E. McKenney
2015-10-16 17:02 ` Frederic Weisbecker
2015-10-17 19:45 ` Theodore Ts'o
2015-10-19 14:14 ` Frederic Weisbecker
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='CAMAWPa9c6kBdJC3n5q=fCD6gEPhGgFCqN_7TS-_-WLjo5_seRA@mail.gmail.com' \
--to=khilman@kernel.org \
--cc=cl@linux.com \
--cc=cmetcalf@ezchip.com \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mingo@kernel.org \
--cc=peterz@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox