From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1423823AbcBQQd1 (ORCPT ); Wed, 17 Feb 2016 11:33:27 -0500 Received: from mail-wm0-f54.google.com ([74.125.82.54]:38868 "EHLO mail-wm0-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1423664AbcBQQdZ (ORCPT ); Wed, 17 Feb 2016 11:33:25 -0500 Date: Wed, 17 Feb 2016 17:33:51 +0100 From: Daniel Vetter To: Peter Zijlstra Cc: Joonas Lahtinen , Oleg Nesterov , Intel graphics driver community testing & development , Linux kernel development , Ingo Molnar , David Hildenbrand , "Paul E. McKenney" , "Gautham R. Shenoy" , Chris Wilson Subject: Re: [Intel-gfx] [PATCH] [RFC] kernel/cpu: Use lockref for online CPU reference counting Message-ID: <20160217163351.GP32705@phenom.ffwll.local> Mail-Followup-To: Peter Zijlstra , Joonas Lahtinen , Oleg Nesterov , Intel graphics driver community testing & development , Linux kernel development , Ingo Molnar , David Hildenbrand , "Paul E. McKenney" , "Gautham R. Shenoy" , Chris Wilson References: <20160215141755.GG6357@twins.programming.kicks-ass.net> <20160215170618.GL6375@twins.programming.kicks-ass.net> <1455612576.4977.11.camel@linux.intel.com> <20160216091440.GT6357@twins.programming.kicks-ass.net> <1455619863.4977.29.camel@linux.intel.com> <20160216110732.GU6357@twins.programming.kicks-ass.net> <1455713251.5622.9.camel@linux.intel.com> <20160217142005.GD6357@twins.programming.kicks-ass.net> <20160217161320.GL32705@phenom.ffwll.local> <20160217161457.GH6357@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160217161457.GH6357@twins.programming.kicks-ass.net> X-Operating-System: Linux phenom 4.3.0-1-amd64 User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Feb 17, 2016 at 05:14:57PM +0100, Peter Zijlstra wrote: > On Wed, Feb 17, 2016 at 05:13:21PM +0100, Daniel Vetter wrote: > > And for context we're hitting this on CI in a bunch of our machines, which > > What's CI ? Continuous integration, aka our own farm of machines dedicated to running i915.ko testcases. Kinda like 0day (it does pre-merge testing on the m-l and also post-merge on our own little integration tree), but for just the graphics team and our needs. -Daniel -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch