Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp817287imu;
        Thu, 22 Nov 2018 05:54:02 -0800 (PST)
X-Google-Smtp-Source: AFSGD/W0eGO+eDr2IucRu+1J9aBfXvD6voQ8Z0GuBkRTJBiCckmOsPeQ5Ms51uhjP+MRL3F0TbfL
X-Received: by 2002:a17:902:74c1:: with SMTP id f1mr11176905plt.273.1542894842639;
        Thu, 22 Nov 2018 05:54:02 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1542894842; cv=none;
        d=google.com; s=arc-20160816;
        b=LuTosehx956bU8vI5tXP+J/yr+Ju81SRVNAtWk0XqmNNjZEPvwVPQ7KXtmttwf/NSI
         k99fk6Pk2lgxxHGDnKEcmVPbSjmqlmsKOr93Q8jXK6Gdh53PPcNmKrJspDGhGA3sqx9x
         hljDiRRE4NFRskHiNFJ73gYwHL0ChmhoG+6Eh1f2LMzz1YTQAL5R2Qpfk4Mh7/Anofp/
         Xz1z2BKuZuVyj77/PU3puc6dlwsHCsd7BZ5KM+VfuzaEfF+4hOqVSiK17tEePmyvJG1r
         TlF7lfY0KThsfZcLWa6lmTgqN2J0SzdgGZ9UvKGuJCXFAI4STcrNtpkzKVL4BX5flwdc
         lprw==
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=0XoYjV/C8UHL1Fmj8LQ8qo5jo/7wKLdAfhzklZmGZLQ=;
        b=X8BGk5+hGTxyZLps2Fegv/0paYZkJHPaPgVso040SzTkBNhu8hPs3Pl5jk1p4rNC1W
         YrJcyFxA5RdyPapIIziFf6Cj2Y9e9j+h41jQnOuSy0gNE++7O5WMeBUTXUF0LZ6+4i5n
         GsFGHiChfpWM5hLtWrqjyMYwJKsNik7RnlxWFykgf2O6WDzJUp7MqpqYVdZ/HSfU+y67
         v68GgSvuuLHj6kF8mGryrbhp79hT1erzSNZEdddMEhgoFqSzNDAcCC1m536QqajJf1wG
         5Wxlfri056n3KDhjFVNXCpUOqOgdwTacJ58aXC+eKpSyBgadLJoDp0bScBdLtBev7ely
         EyiA==
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 28si28831183pgw.364.2018.11.22.05.53.48;
        Thu, 22 Nov 2018 05:54:02 -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 S2391566AbeKVMRa (ORCPT <rfc822;zjuysxie86@gmail.com>
        + 99 others); Thu, 22 Nov 2018 07:17:30 -0500
Received: from mga03.intel.com ([134.134.136.65]:58032 "EHLO mga03.intel.com"
        rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
        id S2391560AbeKVMRa (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 22 Nov 2018 07:17:30 -0500
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga008.jf.intel.com ([10.7.209.65])
  by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Nov 2018 17:40:30 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.56,263,1539673200"; 
   d="scan'208";a="93937920"
Received: from cli6-desk1.ccr.corp.intel.com (HELO [10.239.161.118]) ([10.239.161.118])
  by orsmga008.jf.intel.com with ESMTP; 21 Nov 2018 17:40:27 -0800
Subject: Re: [PATCH v3 2/2] proc: add /proc/<pid>/arch_state
To:     Peter Zijlstra <peterz@infradead.org>,
        Benjamin Herrenschmidt <benh@kernel.crashing.org>,
        Paul Mackerras <paulus@samba.org>,
        Michael Ellerman <mpe@ellerman.id.au>,
        Martin Schwidefsky <schwidefsky@de.ibm.com>,
        Heiko Carstens <heiko.carstens@de.ibm.com>,
        Catalin Marinas <catalin.marinas@arm.com>,
        Will Deacon <will.deacon@arm.com>
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, dave.hansen@intel.com,
        arjan@linux.intel.com, linux-kernel@vger.kernel.org
References: <1542236407-4323-1-git-send-email-aubrey.li@intel.com>
 <1542236407-4323-2-git-send-email-aubrey.li@intel.com>
 <20181119173904.GC2131@hirez.programming.kicks-ass.net>
 <c62acf67-2529-15b1-5325-e0265b0f613d@linux.intel.com>
 <20181121081936.GH2131@hirez.programming.kicks-ass.net>
 <20181121095350.GC2149@hirez.programming.kicks-ass.net>
From:   "Li, Aubrey" <aubrey.li@linux.intel.com>
Message-ID: <7098dd35-3d7b-57c9-c450-10eee577c199@linux.intel.com>
Date:   Thu, 22 Nov 2018 09:40:24 +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: <20181121095350.GC2149@hirez.programming.kicks-ass.net>
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/21 17:53, Peter Zijlstra wrote:
> On Wed, Nov 21, 2018 at 09:19:36AM +0100, Peter Zijlstra wrote:
>> On Wed, Nov 21, 2018 at 09:39:00AM +0800, Li, Aubrey wrote:
>>>> Also; you were going to shop around with the other architectures to see
>>>> what they want/need for this interface. I see nothing on that.
>>>>
>>> I'm open for your suggestion, :)
>>
>> Well, we have linux-arch and the various maintainers are also listed in
>> MAINTAINERS. Go forth and ask..
> 
> Ok, so I googled a wee bit (you could have too).
> 
> There's not that many architectures that build big hot chips
> (powerpc,x86,arm64,s390) (mips, sparc64 and ia64 are pretty dead I
> think, although the Fujitsu Sparc M10 X+/X SIMD looked like it could be
> 'fun').
> 
> Of those, powerpc altivec doesn't seem to be very wide, but you'd have
> to ask the power folks. Same for s390 z13.
> 
> The Fujitsu/ARM64-SVE stuff looks like it can be big and hot.
> 
> And RISC-V has was vector extention, but I don't think anybody is
> actually building big hot versions of that just yet.
> 
Thanks Peter. Add more maintainers here.

On some x86 architectures, the tasks using simd instruction(AVX512 particularly)
need to be dealt with specially against the tasks not using simd instruction.
I proposed an interface to expose such CPU specific information for the user
space tools to apply different scheduling policies.

The interface can be refined to be the format as /proc/<pid>/status. Not sure
if it's useful to any other architectures.

Welcome any comments.

Thanks,
-Aubrey