Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp313282imu; Thu, 8 Nov 2018 02:19:38 -0800 (PST) X-Google-Smtp-Source: AJdET5cgJTip9D4qf4rQWJAmBOTOvk0xy610ZU6jrI9LvCCNTUh/paL2i+EmbsLNHZu8OQwA5Nxk X-Received: by 2002:a17:902:684e:: with SMTP id f14-v6mr3968624pln.242.1541672378604; Thu, 08 Nov 2018 02:19:38 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1541672378; cv=none; d=google.com; s=arc-20160816; b=XNhNu3UacGJWmNuqcorzUUx3EFwsEAgYxxwE368ayJRjPyWGZ3tkmJLeLDLo24JY8f baO14KVcwIEpa/2IM5Sav3ZGv3PNApBJp7ql1vVzSMGb5bGcBf0InoK0Fe2fAhqkICgO N/5p933pqfUnvUc6Q0D42eX3CLFcL9k/UCNgI2uPwn29OIeZDmPlE+tav+TJ3+5P2QJp 7vLYeJPMZ/WV4zIjRHNVm9lFnMtVVoIv7c223Jhu2fz3Y0olNhflMR8RIGdDMTHyqO7G pvA1bsiBS4N5vUXf5IS/Xu+ZK29kyD07cDsXc7lc21wLC5Ae2+GeNfuzARwAGBDfu0Xw lgXA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=tmRtPXjofVIj5o/lAJwKyOGggGTVfDB2eg0zVqw8p5g=; b=l1t4GdQLH06xNSpho5ZoIyeWokgrsYIw+auuaBqfOdh6AQRdPnTqFkFDRJ/1tkRq5A PKy70gH3nmplVd0Cs1fiHKi922KD+uoKYPnyfWFQpY2EOwZNrbTT59F7tRiadIbe2/0c hOX6kilZVv59eucBhpJuZvrtfoi3MuGPyxKwB+K8yL2rt7FR8x9C4A18CuqlthqvDXiE gCTmIE3LpvrMQFh02vH4W/xNTJaZb5z6JdTHpVhW0HEsyNYQAdh6Ivtr4ZXVm1akR1Gx dEactZS3D6WSpEoGMVfsGr8u9bkHfX6v+hjNo709kZ8RSwVlYUMLbYygvu+4XGseYkph MxJQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=PauAGUcC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j10si3628823pgt.155.2018.11.08.02.19.22; Thu, 08 Nov 2018 02:19:38 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=fail header.i=@infradead.org header.s=merlin.20170209 header.b=PauAGUcC; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726941AbeKHTwZ (ORCPT + 99 others); Thu, 8 Nov 2018 14:52:25 -0500 Received: from merlin.infradead.org ([205.233.59.134]:58448 "EHLO merlin.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726435AbeKHTwY (ORCPT ); Thu, 8 Nov 2018 14:52:24 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=infradead.org; s=merlin.20170209; h=In-Reply-To:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=tmRtPXjofVIj5o/lAJwKyOGggGTVfDB2eg0zVqw8p5g=; b=PauAGUcCB7E5u5Rddo6IMYZ+F WWCuIhpi5B77NQ3NAJTNTxZUWyQt8+aUk+THjemh/FoA76CK0f5whBYKfCIEhWZbAn9iCFFvsQWbe 7vUIwGATxblqCW+91ajBXFy7KPGO9fIj94wzxhFdinCx6KQkRnwNWJV2DufZVXX5E+KwmdwUsJbVl kmzfpH2CzU8kWWxaDQK7XoKG27Me0sFW5YF5YJcz1T1rGikgzivEK1M3esUlXGEwPbQxp4T/XgzP2 ksPrl7mtQ/KfS8JeIoV0Tr0+5VGdNi/hFyrn1owo/L1buH3VmAorpvu6DrGJ7EbslLp7Ep7a/HK5V jKhMIH0tA==; Received: from j217100.upc-j.chello.nl ([24.132.217.100] helo=hirez.programming.kicks-ass.net) by merlin.infradead.org with esmtpsa (Exim 4.90_1 #2 (Red Hat Linux)) id 1gKhNU-0008TV-7N; Thu, 08 Nov 2018 10:17:32 +0000 Received: by hirez.programming.kicks-ass.net (Postfix, from userid 1000) id D36B520284F98; Thu, 8 Nov 2018 11:17:29 +0100 (CET) Date: Thu, 8 Nov 2018 11:17:29 +0100 From: Peter Zijlstra To: Ingo Molnar Cc: Aubrey Li , tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, ak@linux.intel.com, tim.c.chen@linux.intel.com, arjan@linux.intel.com, linux-kernel@vger.kernel.org, Aubrey Li Subject: Re: [RFC PATCH v1 2/2] proc: add /proc//thread_state Message-ID: <20181108101729.GP9761@hirez.programming.kicks-ass.net> References: <1541528590-30296-1-git-send-email-aubrey.li@intel.com> <1541528590-30296-2-git-send-email-aubrey.li@intel.com> <20181108063246.GA13233@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20181108063246.GA13233@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 08, 2018 at 07:32:46AM +0100, Ingo Molnar wrote: > > * Aubrey Li wrote: > > > Expose the per-task cpu specific thread state value, it's helpful > > for userland to classify and schedule the tasks by different policies > > That's pretty vague - what exactly would use this information? I'm sure > you have a usecase in mind - could you please describe it? Yeah, "thread_state" is a pretty terrible name for this. The use-case is detectoring which tasks use AVX3 such that a userspace component (think job scheduler) can cluster them together. The 'problem' is that running AVX2+ code drops the max clock, because you light up the massive wide (and thus large area) paths. So maybe something like "simd_active" is a better name, dunno. Or maybe "simd_class" and we can write out 0,1,2,3 depending on the AVX class being used, dunno. It might make sense to look at what other arch SIMD stuff looks like to form this interface.