Received: by 2002:ac0:a582:0:0:0:0:0 with SMTP id m2-v6csp125439imm; Tue, 9 Oct 2018 15:02:34 -0700 (PDT) X-Google-Smtp-Source: ACcGV60PriY86VyKyCpq6EnN7FkulDRVDYDugiM2fLQKPzexNXcFnHNxymj5sH/MJYC0CTdN18U1 X-Received: by 2002:a62:5698:: with SMTP id h24-v6mr5176364pfj.42.1539122554626; Tue, 09 Oct 2018 15:02:34 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1539122554; cv=none; d=google.com; s=arc-20160816; b=uL7PWxOH6zTdV5q0TwohnWa/ygQTQb5FUTJnqkKMagl7UXMU8hcV+oMr2ED6mOp+ev 0BBPxWtGXlY6ylctrZSn0aJtW9BKK4znk8o9iHRuwWMCrzQNa56KdCM8c9K3e2Ztwa+x 6FUvbpt++EoB4k35MwRMu6RVGinTD6FzwY8wiVJcrFM0QrdBYnCqOWek5ExF+iVYkXCe 1VKFPsTtpRie+9eNYe6cyMeHd8ZuNSO9Qqn9sGllR9aZHRY3JdiGXgaGT9CWiGkTPls9 AamcYJo8jd7sg7m9r5KBLwqqTPWeI+B8C/QwOThdVCYCcx30ECl/j4JXiVUKv3NpaRYc rdVg== 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=6tUT7VSbUNuD2s9VeHMJflMT/jY75ECgVZGAGPUnA7U=; b=jjHZqWTY9k+GRr4L+2K41XLLsevvPItrVNcf0e1Hwd+XBj6C8sGAfCo/H6V/UAUAB4 MV6SJFpjpoyynFhQohyae5AxXZr1h5VasA+VU3Ltym6YHFIGemkeonpAtIeZrIXzUmsg 5I+nugL+wBTI4MpLGaOskDSQKDrZD8PetsxyMEiNLmT9Tw02xPjL8mrRH+j1tB4j77Ep gEyo9UM/pex1Pq3mhfWjRNgnLJ0BVklk0R5sP7h9y4rv1+xveC77HFZDc76UbvXw5p5V unH0e03SkbZ1qrhwZozfcGBO0awIGCrl+UM+qsh4FGbR14koHVmWEuVlwKaUcLySrHCM XJUQ== 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: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id h7-v6si25620486pfe.72.2018.10.09.15.02.18; Tue, 09 Oct 2018 15:02:34 -0700 (PDT) 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 S1726831AbeJJFUp (ORCPT + 99 others); Wed, 10 Oct 2018 01:20:45 -0400 Received: from mga12.intel.com ([192.55.52.136]:11039 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725860AbeJJFUo (ORCPT ); Wed, 10 Oct 2018 01:20:44 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 09 Oct 2018 15:01:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.54,361,1534834800"; d="scan'208";a="97573402" Received: from rchatre-mobl.amr.corp.intel.com (HELO [10.24.14.109]) ([10.24.14.109]) by fmsmga001.fm.intel.com with ESMTP; 09 Oct 2018 15:01:09 -0700 Subject: Re: [PATCH v2 01/11] arch/x86: Start renaming the rdt files to more generic names To: "Moger, Babu" , "tglx@linutronix.de" , "mingo@redhat.com" , "hpa@zytor.com" , "fenghua.yu@intel.com" , "james.morse@arm.com" , "vikas.shivappa@linux.intel.com" , "tony.luck@intel.com" Cc: "x86@kernel.org" , "peterz@infradead.org" , "pombredanne@nexb.com" , "gregkh@linuxfoundation.org" , "kstewart@linuxfoundation.org" , "bp@suse.de" , "rafael.j.wysocki@intel.com" , "ak@linux.intel.com" , "kirill.shutemov@linux.intel.com" , "xiaochen.shen@intel.com" , "colin.king@canonical.com" , "Hurwitz, Sherry" , "Lendacky, Thomas" , "pbonzini@redhat.com" , "dwmw@amazon.co.uk" , "luto@kernel.org" , "jroedel@suse.de" , "jannh@google.com" , "dima@arista.com" , "jpoimboe@redhat.com" , "vkuznets@redhat.com" , "linux-kernel@vger.kernel.org" References: <20181005205512.29545-1-babu.moger@amd.com> <20181005205512.29545-2-babu.moger@amd.com> <2fe2e853-47ef-af2a-6906-9ad7a7b8bba9@intel.com> From: Reinette Chatre Message-ID: Date: Tue, 9 Oct 2018 15:01:09 -0700 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: 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: X-Mailing-List: linux-kernel@vger.kernel.org Hi Babu, On 10/9/2018 2:17 PM, Moger, Babu wrote: > On 10/09/2018 11:39 AM, Reinette Chatre wrote: >> Hi Babu, >> >> On 10/5/2018 1:55 PM, Moger, Babu wrote: >>> New generation of AMD processors start support RDT(or QOS) features. >>> With more than one vendors supporting these features, it seems more >>> appropriate to rename these files. >>> >>> Signed-off-by: Babu Moger >>> --- >>> arch/x86/include/asm/{intel_rdt_sched.h => rdt_sched.h} | 0 >>> arch/x86/kernel/cpu/Makefile | 6 +++--- >>> arch/x86/kernel/cpu/{intel_rdt.c => rdt.c} | 4 ++-- >>> arch/x86/kernel/cpu/{intel_rdt.h => rdt.h} | 0 >>> .../cpu/{intel_rdt_ctrlmondata.c => rdt_ctrlmondata.c} | 2 +- >>> arch/x86/kernel/cpu/{intel_rdt_monitor.c => rdt_monitor.c} | 2 +- >>> .../cpu/{intel_rdt_pseudo_lock.c => rdt_pseudo_lock.c} | 6 +++--- >>> ...ntel_rdt_pseudo_lock_event.h => rdt_pseudo_lock_event.h} | 2 +- >>> .../x86/kernel/cpu/{intel_rdt_rdtgroup.c => rdt_rdtgroup.c} | 4 ++-- >>> arch/x86/kernel/process_32.c | 2 +- >>> arch/x86/kernel/process_64.c | 2 +- >>> 11 files changed, 15 insertions(+), 15 deletions(-) >>> rename arch/x86/include/asm/{intel_rdt_sched.h => rdt_sched.h} (100%) >>> rename arch/x86/kernel/cpu/{intel_rdt.c => rdt.c} (99%) >>> rename arch/x86/kernel/cpu/{intel_rdt.h => rdt.h} (100%) >>> rename arch/x86/kernel/cpu/{intel_rdt_ctrlmondata.c => rdt_ctrlmondata.c} (99%) >>> rename arch/x86/kernel/cpu/{intel_rdt_monitor.c => rdt_monitor.c} (99%) >>> rename arch/x86/kernel/cpu/{intel_rdt_pseudo_lock.c => rdt_pseudo_lock.c} (99%) >>> rename arch/x86/kernel/cpu/{intel_rdt_pseudo_lock_event.h => rdt_pseudo_lock_event.h} (95%) >>> rename arch/x86/kernel/cpu/{intel_rdt_rdtgroup.c => rdt_rdtgroup.c} (99%) >> >> During the RFC it was agreed that "resctrl" will be the neutral name and >> "intel_rdt", "amd_qos", or "arm mpam" would be the vendor specific names. >> >> It is ok to delay that renaming but I think any renaming done from this >> point should respect this agreement. >> >> For example, if you want to rename intel_rdt.c then please rename it to >> resctrl.c instead of just rdt.c which does not represent a generic name >> as expressed as a goal in the subject of this patch. > > I knew this was going to bit tricky. I can change all the places where I > am touching the code to generic names(change from intel_rdt to "resctrl"). Yes, "intel_rdt" can be changed to the generic "resctrl" when it is not vendor specific. As far as all the code you touch is concerned it may be easier and cause less confusion for now to just follow the current naming conventions as you have done in patches 3 onwards and have it be included in the later larger restructuring. > Also lets change the "texts" which are visible to user to make it more > generic. Could you please elaborate what you mean with "texts" here? Are you referring to the pr_info() found in intel_rdt_late_init()? Here it may be good to also change to print "RESCTRL %s allocation detected"/"RESCTRL %s monitoring detected" - the resource names printed are already generic. > But "rdt" has been used generously in multiple files(like rdt_resource, > rdt_domain etc). Changing those definitions and functions will be messier. > I will not worry about it now. Thoughts? I agree. My comments were specific to the first two patches of this series that started doing the renaming but not using the agreed upon naming - especially since both those patches claim to transition to generic names. Could just these two patches be modified to change "intel_rdt" to "resctrl" instead of "intel_rdt" to "rdt" as it currently does? Reinette