Received: by 2002:a25:8b91:0:0:0:0:0 with SMTP id j17csp9367731ybl; Fri, 17 Jan 2020 10:44:54 -0800 (PST) X-Google-Smtp-Source: APXvYqx4zcFhzkp0PeV7shDUL+Xbvei84j/+Ep0jgxRTNB3UpQcGObTsEHTyFru93Uuq+nsqaN0M X-Received: by 2002:a9d:6b03:: with SMTP id g3mr6975811otp.200.1579286694087; Fri, 17 Jan 2020 10:44:54 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1579286694; cv=none; d=google.com; s=arc-20160816; b=zBz4L1PHFLv01GsgS5V1lRpaahRKsofI199wNdjcrfkyJWozz1nthKZ7YlSzL37yfW dCDC6yC6mro2bz+1XA686uSxUqFyR4Ap2AkX1oeTqps8eSCZUHlY6L5MMeJC7qHwyxk3 x7HaYzVeDdJH+giwSomvCxKeZwPonnrY68Jiw6uaWNWoVb4ZlqKzirsH0q3ofTBtbFnv P9z31CDuDOuy4PSvvYUks0AIVKnSiDSW5lth7mtkUsytgrpRUM5fXXsXg9Oqy5Ezhn2z Y6cQowX46IabjonOOUOi5EB+x2GkR1Z4t+CeeNbkQeRFnqsZEVvBDJu5Vp8AY9Kq9edV 71eg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=mMXF1ZaPoCWcfoRUroMcSW6eEaFTzCYYtx/i5k6Q7Pc=; b=TnhqbUQ4bDt1667PHayy3XUMRovTzVTdbhaMOZv3qqabuzlAjlThx2RgUZMdCmRrBX 7f5hNboP9jrKiMjRvO4suX0lptIg+5YLIH6qmWKowErNHBCvrK7RZu1kNVIxv0dw7YR6 PUHI27fwE6hQgHnBzTbdPCBgmdjzGwnqbjH5oQSf/HeG5jwXkEFsQatBf1EHkCQ4k4M8 eQA42qLP5YspBtihieU7RlLoZLOrQfUA6yIfX5DUBBC6v2KPkjc6aNAiKXpA3ldkTUdF P9os2xLLb+nmYdPzF7aKm4efX84QqQoZaZk+7Hc47u4Pd+fCVrXeHEvaaMdBiIgoKJXF K/qA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wMBkHaU7; 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 l189si14379701oih.166.2020.01.17.10.44.42; Fri, 17 Jan 2020 10:44:54 -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=pass header.i=@kernel.org header.s=default header.b=wMBkHaU7; 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 S1729078AbgAQSmw (ORCPT + 99 others); Fri, 17 Jan 2020 13:42:52 -0500 Received: from mail.kernel.org ([198.145.29.99]:34590 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726603AbgAQSmw (ORCPT ); Fri, 17 Jan 2020 13:42:52 -0500 Received: from localhost (83-86-89-107.cable.dynamic.v4.ziggo.nl [83.86.89.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 151A02072B; Fri, 17 Jan 2020 18:42:51 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1579286571; bh=CR8E6lRLBE6fE2cORjU/dqghNqr4V3/7DeaKyioujBg=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=wMBkHaU7nTUa9rSxSaYqB1xdjCgYNYdIGQr3eOYpgC0BC164j13Xdd9Oj6Cvw2VbC CWbWP2Nq64c3XMw2xZ8ux6EwbKSyBQkXR2s1gx8vwdot3oh5v1tC2T3ZJNHomPGT+J 2+9ThHvcSsNigUnMp2N+KXtEnea9wVu0ofIrxmI0= Date: Fri, 17 Jan 2020 19:42:49 +0100 From: Greg KH To: Andi Kleen Cc: roman.sudarikov@linux.intel.com, peterz@infradead.org, mingo@redhat.com, acme@kernel.org, mark.rutland@arm.com, alexander.shishkin@linux.intel.com, jolsa@redhat.com, namhyung@kernel.org, linux-kernel@vger.kernel.org, eranian@google.com, bgregg@netflix.com, kan.liang@linux.intel.com, alexander.antonov@intel.com Subject: Re: [PATCH v4 2/2] perf =?iso-8859-1?Q?x86?= =?iso-8859-1?Q?=3A_Exposing_an_Uncore_unit_to_PMON_for_Intel_Xeon?= =?iso-8859-1?Q?=AE?= server platform Message-ID: <20200117184249.GB1969121@kroah.com> References: <20200117133759.5729-1-roman.sudarikov@linux.intel.com> <20200117133759.5729-3-roman.sudarikov@linux.intel.com> <20200117141944.GC1856891@kroah.com> <20200117162357.GK302770@tassilo.jf.intel.com> <20200117165406.GA1937954@kroah.com> <20200117172726.GM302770@tassilo.jf.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200117172726.GM302770@tassilo.jf.intel.com> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 17, 2020 at 09:27:26AM -0800, Andi Kleen wrote: > > > Could you suggest how such a 1:N mapping should be expressed instead in > > > sysfs? > > > > I have yet to figure out what it is you all are trying to express here > > given a lack of Documentation/ABI/ file :) > > I thought the example Roman gave was clear. > > System has multiple dies > Each die has 4 pmon ports > Each pmon port per die maps to one PCI bus. > > He mapped it to > > pmon0-3: list of pci busses indexed by die > > To be honest the approach doesn't seem unreasonable to me. It's similar > e.g. how we express lists of cpus or nodes in sysfs today. Again, you are having to parse a single line of output from sysfs that contains multiple values, one that will just keep getting bigger and bigger as time goes on until we run out of space. One value per file for sysfs, it's been the rule since the beginning. If there are files that violate this, ugh, it slips through, but as the submitter is asking for my review, I am going to actually follow the rules here. greg k-h