Received: by 2002:a05:6a10:f3d0:0:0:0:0 with SMTP id a16csp3613876pxv; Mon, 28 Jun 2021 08:36:42 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzpFyBySCh6hxUgkl+iHNc3tQZEAtJAgW2fFnwOh/1wcYQ7hzIqTZFmNewYMKoaQlQu5QPv X-Received: by 2002:a17:906:384c:: with SMTP id w12mr7288317ejc.445.1624894602059; Mon, 28 Jun 2021 08:36:42 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624894602; cv=none; d=google.com; s=arc-20160816; b=wiYZroFXSaQ9uTBTJwWjA3RGzWnhBMesJK36hEZnC3Tv1DPBh1j1aglL7i5EHNzXZ6 lK74DGrNh9qxI3KIy/f9+pfo8ctPOzLCetlZ0cEw5MpBr7fonlCxcfxdIkh4ePE2yfgN p7T5o779SNnxLNHVHVuqcVNq3EHz2mrm2siaAkTjTjw3ah21fAm4uR2uk8tn9H1Lr0+v xW8MQAxGvisWImSUOXowDeGAAUZRDVSMv0+WVkqK9AWAi0PbRgk5cHT0eTLfEiotkLb9 bQf4ElrSLDycTJaBadM0eKq9FJG3reSkDJM4Uh2VBI1ELoYtPUgBHiPPEK1xWGq3tru2 xeEg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-language:content-transfer-encoding :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject; bh=UOFYvba95agHDCbDYU3KV8lXFgvsBT7DMMMCrn6X+GY=; b=vIz3JG/uEnSP2bfCMNiibM1cJbx3v6+nF26ab2OEz4DftxENQKof7lrENQe4TIg6up tQrWGgv+a8larZtVtd/nxDBEX+hYkSRwN4LLK69fAg8rE8ZMXliKBL/QQShAKfElKrAx 0jbvLbgO9F2WHlnsdna4odlExYuXf/8n8SEGF6FJqhcwShH1kyriF0ffYBH+OrLj3tUV G5rk8garxPYIFEMCcvq5I2KV+R5Gpag4vh8Ok0c/LMKAmOQa42AJD3Ai6UFyA/FY2nYI pSZ7Yn/q51I6oNLwBgTOmV2bNZS12e9XIdQEtG+rPl7aQ0JkBk3cQdA0XfFTOg6bWDw0 v9iA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id e5si13903323edu.539.2021.06.28.08.36.17; Mon, 28 Jun 2021 08:36:42 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 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 S238103AbhF1PeH (ORCPT + 99 others); Mon, 28 Jun 2021 11:34:07 -0400 Received: from mga12.intel.com ([192.55.52.136]:24075 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236583AbhF1PLq (ORCPT ); Mon, 28 Jun 2021 11:11:46 -0400 X-IronPort-AV: E=McAfee;i="6200,9189,10029"; a="187657388" X-IronPort-AV: E=Sophos;i="5.83,306,1616482800"; d="scan'208";a="187657388" Received: from fmsmga005.fm.intel.com ([10.253.24.32]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jun 2021 08:00:05 -0700 X-IronPort-AV: E=Sophos;i="5.83,306,1616482800"; d="scan'208";a="643361063" Received: from ngminuti-mobl.amr.corp.intel.com (HELO [10.212.174.12]) ([10.212.174.12]) by fmsmga005-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 28 Jun 2021 08:00:05 -0700 Subject: Re: [PATCH 2/7] perf: Create a symlink for a PMU To: Greg KH Cc: kan.liang@linux.intel.com, peterz@infradead.org, mingo@redhat.com, linux-kernel@vger.kernel.org, eranian@google.com, namhyung@kernel.org, acme@kernel.org, jolsa@redhat.com References: <1e536604-cf93-0f09-401e-2073924c5582@linux.intel.com> <29d5f315-578f-103c-9523-ae890e29c7e7@linux.intel.com> <540d8a38-da12-56c8-8306-8d3d61ae1d6b@linux.intel.com> From: Andi Kleen Message-ID: Date: Mon, 28 Jun 2021 08:00:05 -0700 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.11.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 6/27/2021 11:55 PM, Greg KH wrote: > On Sun, Jun 27, 2021 at 09:30:53AM -0700, Andi Kleen wrote: >>> Then do not break things by renaming the device name, as you all have >>> now stated that this name is part of the user/kernel api. >> The renaming comes from the fallback mode on future systems. In the fallback >> mode the driver doesn't know the true name, so it has to useĀ  the numeric >> name. If you don't use the fallback mode and have the full driver then yes >> you'll get the same names as always (or at least as they make sense for the >> hardware). >> >> But we would like to have the fallback mode too to allow more people use >> uncore monitoring, and that's where the need to for the second name comes >> in. > So then just always use the "fallback" name if that is going to be the > name you have for this hardware device. Why would you want it to be > renamed later on to a "fancier" name if there is only going to be > one-per-chipset-type anyway? It's an ugly numeric name, difficult to use perf stat -e uncore_0_2// instead of perf stat -e uncore_cha// It wouldn't exactly be an improvement for the full driver. -Andi