From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1755950AbcGHTfI (ORCPT <rfc822;w@1wt.eu>);
	Fri, 8 Jul 2016 15:35:08 -0400
Received: from mail-wm0-f42.google.com ([74.125.82.42]:34504 "EHLO
	mail-wm0-f42.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
	with ESMTP id S1755400AbcGHTfC (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Fri, 8 Jul 2016 15:35:02 -0400
Date: Fri, 8 Jul 2016 21:34:57 +0200
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@suse.de>
Cc: "Luck, Tony" <tony.luck@intel.com>, "Yu, Fenghua" <fenghua.yu@intel.com>,
        Thomas Gleixner <tglx@linutronix.de>,
        "Anvin, H Peter" <h.peter.anvin@intel.com>,
        Ingo Molnar <mingo@elte.hu>, Stephane Eranian <eranian@google.com>,
        Peter Zijlstra <peterz@infradead.org>,
        Vikas Shivappa <vikas.shivappa@linux.intel.com>,
        "Shankar, Ravi V" <ravi.v.shankar@intel.com>,
        linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [PATCH v2 2/3] Documentation, ABI: Add a document entry for
 cache id
Message-ID: <20160708193457.GA18734@gmail.com>
References: <1467842838-57246-1-git-send-email-fenghua.yu@intel.com>
 <1467842838-57246-3-git-send-email-fenghua.yu@intel.com>
 <20160708084146.GA4508@gmail.com>
 <3E5A0FA7E9CA944F9D5414FEC6C712205DFD3208@ORSMSX106.amr.corp.intel.com>
 <3908561D78D1C84285E8C5FCA982C28F3A15599C@ORSMSX114.amr.corp.intel.com>
 <20160708180746.GB4429@gmail.com>
 <20160708184110.GD3938@pd.tnic>
 <3908561D78D1C84285E8C5FCA982C28F3A155BD7@ORSMSX114.amr.corp.intel.com>
 <20160708185541.GE3938@pd.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20160708185541.GE3938@pd.tnic>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


Yeah, so if the 'cache index' naming has already been settled, then I suspect 
we'll have to live with it - but at least let's name it 'cache-index' when we 
refer to it, not just 'index' which is super confusing (to me!).

I.e. instead:

  The id identifies a cache in the platform. In same index, the id
  is unique across the platform.

Something like this is more readable I think:

  The cache-id identifies a hardware cache of the system within a given
  cache-index category of caches. The (cache-index,cache-id) pair is
  unique for the whole system.

agreed?

Thanks,

	Ingo