Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp3786666imu;
        Sun, 11 Nov 2018 23:55:46 -0800 (PST)
X-Google-Smtp-Source: AJdET5dhzw8wz5qR8AILiTasG/3O8V5sXRtx1aJ8fqrXtFCx5KkNFoUvPvySYuCW3iy7gwCWYJ4b
X-Received: by 2002:aa7:8685:: with SMTP id d5-v6mr18784991pfo.58.1542009346150;
        Sun, 11 Nov 2018 23:55:46 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1542009346; cv=none;
        d=google.com; s=arc-20160816;
        b=CxaXqHJutyrwX+Sva7uZMHbrdTQu7lxfyMW7G96lkd+VfFrRkheOaFsjpyvHMg9QLY
         kjkxm5nALKt0TxlQCuVCVVwtpLM8u3mA6/UAF88vtyEuEajIpwBr3Uullo7k2Ya8lkmP
         Hwey0cVjGdNJ0pKIPD8+JFVF/ANMygNAHDf8I1gMYbhO9zqNYw47vCn4VQ0J55BsxgBF
         lhd1BLjYtwAeIRX/gC7HHIzYw3IZ6FehBCxu30XLtPBdn1qS4sshQuFoZFuiRerfYCQL
         Vrw/cSuE1MRqq4HovFmdMVg62e70k+hbxtZNOCpdqlvc8dnLnvn5LtTxhnnKIPUdOeHr
         1CmQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
        h=list-id:precedence:sender:content-transfer-encoding
         :content-language:in-reply-to:mime-version:user-agent:date
         :message-id:from:references:cc:to:subject;
        bh=8zBBH9c5t8lp0tMksj613sDylMECye7fyEXlmWDq0Gw=;
        b=k9Za9PHAz054QmE91fcavjmKxp5hA1wqWqNLg0L7h3EVPJOoQeMdgz8IBunkIoZtFE
         rIXv73lNG1f3vfmyVexu5XP9YJsqqDaTVN/Yfdh15B4+4Qo4ads4p35yv3+nQAxvUszq
         e/OaDqpLM6rQNUqgSwApOir7t/JPCQFf/goI1L6nqVeZ8ZRC8k+LQS5WwhQ0amSg9Emj
         PgyODRtaP+n/aGXNN4Vuji8jOCMbOeK1gtJXwy/Q/f3eqWJq/WshuZ6DYkgCaExOPSRg
         HwW1Rfh1VgQ+gpd9Xn8KBzbZ59j0NCEbxT3Yp6dbMpGmMaeFFz/DJr+TDvQtxxoudjwC
         nw7Q==
ARC-Authentication-Results: i=1; mx.google.com;
       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;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67])
        by mx.google.com with ESMTP id h34-v6si17663613pld.358.2018.11.11.23.55.24;
        Sun, 11 Nov 2018 23:55:46 -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;
       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;
       dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1728040AbeKLRpe (ORCPT <rfc822;peterpeng024@gmail.com>
        + 99 others); Mon, 12 Nov 2018 12:45:34 -0500
Received: from mga04.intel.com ([192.55.52.120]:59604 "EHLO mga04.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S1725871AbeKLRpe (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 12 Nov 2018 12:45:34 -0500
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga001.jf.intel.com ([10.7.209.18])
  by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 11 Nov 2018 23:53:31 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.54,494,1534834800"; 
   d="scan'208";a="107493833"
Received: from cli6-desk1.ccr.corp.intel.com (HELO [10.239.161.118]) ([10.239.161.118])
  by orsmga001.jf.intel.com with ESMTP; 11 Nov 2018 23:53:28 -0800
Subject: Re: [RFC PATCH v1 2/2] proc: add /proc/<pid>/thread_state
To:     Ingo Molnar <mingo@kernel.org>,
        Peter Zijlstra <peterz@infradead.org>
Cc:     Aubrey Li <aubrey.li@intel.com>, 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
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>
 <20181108101729.GP9761@hirez.programming.kicks-ass.net>
 <20181112053147.GA78520@gmail.com>
From:   "Li, Aubrey" <aubrey.li@linux.intel.com>
Message-ID: <a9da1af4-a71a-1188-9806-f3832359d07f@linux.intel.com>
Date:   Mon, 12 Nov 2018 15:53:28 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101
 Thunderbird/52.1.1
MIME-Version: 1.0
In-Reply-To: <20181112053147.GA78520@gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

On 2018/11/12 13:31, Ingo Molnar wrote:
> 
> * Peter Zijlstra <peterz@infradead.org> wrote:
> 
>> On Thu, Nov 08, 2018 at 07:32:46AM +0100, Ingo Molnar wrote:
>>>
>>> * Aubrey Li <aubrey.li@intel.com> 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.
> 
> I'd prefer the kernel to do such clustering...
> 
Some userland application projects like Kubernetes request an interface of 
such information, we could do the clustering either in the kernel or from
userland, does it make sense we expose the information via the proposed 
interface first?

Thanks,
-Aubrey