Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932837AbbHKVcY (ORCPT ); Tue, 11 Aug 2015 17:32:24 -0400 Received: from mail.kernel.org ([198.145.29.136]:59787 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752627AbbHKVcW (ORCPT ); Tue, 11 Aug 2015 17:32:22 -0400 MIME-Version: 1.0 In-Reply-To: References: Date: Tue, 11 Aug 2015 14:32:16 -0700 Message-ID: Subject: Re: [BELATED CORE TOPIC] context tracking / nohz / RCU state From: Kevin Hilman To: Andy Lutomirski Cc: "ksummit-discuss@lists.linuxfoundation.org" , "linux-kernel@vger.kernel.org" , Paul McKenney , Christoph Lameter , =?UTF-8?B?RnLDqWTDqXJpYyBXZWlzYmVja2Vy?= , Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , Peter Zijlstra , Chris Metcalf , Rik van Riel Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 777 Lines: 18 On Tue, Aug 11, 2015 at 10:49 AM, Andy Lutomirski 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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/