lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:   Tue, 6 Nov 2018 19:03:01 +0000
From:   "Moger, Babu" <Babu.Moger@....com>
To:     Matthew Wilcox <willy@...radead.org>
CC:     "tglx@...utronix.de" <tglx@...utronix.de>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "bp@...en8.de" <bp@...en8.de>, "corbet@....net" <corbet@....net>,
        "fenghua.yu@...el.com" <fenghua.yu@...el.com>,
        "reinette.chatre@...el.com" <reinette.chatre@...el.com>,
        "peterz@...radead.org" <peterz@...radead.org>,
        "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
        "hpa@...or.com" <hpa@...or.com>, "x86@...nel.org" <x86@...nel.org>,
        "mchehab+samsung@...nel.org" <mchehab+samsung@...nel.org>,
        "arnd@...db.de" <arnd@...db.de>,
        "kstewart@...uxfoundation.org" <kstewart@...uxfoundation.org>,
        "pombredanne@...b.com" <pombredanne@...b.com>,
        "rafael@...nel.org" <rafael@...nel.org>,
        "kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
        "tony.luck@...el.com" <tony.luck@...el.com>,
        "qianyue.zj@...baba-inc.com" <qianyue.zj@...baba-inc.com>,
        "xiaochen.shen@...el.com" <xiaochen.shen@...el.com>,
        "pbonzini@...hat.com" <pbonzini@...hat.com>,
        "Singh, Brijesh" <brijesh.singh@....com>,
        "Hurwitz, Sherry" <sherry.hurwitz@....com>,
        "dwmw2@...radead.org" <dwmw2@...radead.org>,
        "Lendacky, Thomas" <Thomas.Lendacky@....com>,
        "luto@...nel.org" <luto@...nel.org>,
        "joro@...tes.org" <joro@...tes.org>,
        "jannh@...gle.com" <jannh@...gle.com>,
        "vkuznets@...hat.com" <vkuznets@...hat.com>,
        "rian@...m.mit.edu" <rian@...m.mit.edu>,
        "jpoimboe@...hat.com" <jpoimboe@...hat.com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v6 13/14] Documentation/x86: Rename and update
 intel_rdt_ui.txt

Hi Matthew,

On 11/6/18 11:41 AM, Matthew Wilcox wrote:
> On Tue, Nov 06, 2018 at 07:53:05AM -0800, Matthew Wilcox wrote:
>>> -This feature is enabled by the CONFIG_INTEL_RDT Kconfig and the
>>> -X86 /proc/cpuinfo flag bits:
>>> +This feature is enabled by the CONFIG_INTEL_RDT Kconfig(for Intel) or
>>> +CONFIG_AMD_QOS(for AMD) and the X86 /proc/cpuinfo flag bits:
>>
>> Now I'm curious why we have two different Kconfig options for the same
>> feature.  I should go and read the other patches, I suppose.
> 
> Now that I've read through them, I find nowhere that the choices:
> 
> AMQ_QOS=y INTEL_RDT=n
> AMD_QOS=n INTEL_RDT=y
> AMD_QOS=y INTEL_RDT=y
> 
> have any difference to the resulting code.  Thus, this looks like a
> vanity config option; please don't do this.  Rename the config option
> to be vendor-neutral if you must, but please no new options unless
> absolutely necessary.
> 

Yes. That is right. Code does not change with any of these combinations.
We can go with only one neutral parameter which is config RESCTRL. I will
remove AMD_QOS and INTEL_RDT. This also requires some text changes to
cover both Intel and AMD. Will send the updated patches.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ