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]
Message-ID: <DM5PR12MB24713B1A0FB97FAF2CCCB9A895DA0@DM5PR12MB2471.namprd12.prod.outlook.com>
Date:   Wed, 21 Nov 2018 16:47:30 +0000
From:   "Moger, Babu" <Babu.Moger@....com>
To:     Borislav Petkov <bp@...en8.de>
CC:     "tglx@...utronix.de" <tglx@...utronix.de>,
        "mingo@...hat.com" <mingo@...hat.com>,
        "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 v8 06/13] arch/resctrl: Initialize the resource functions
 that are different



> -----Original Message-----
> From: Borislav Petkov <bp@...en8.de>
> Sent: Tuesday, November 20, 2018 6:05 AM
> To: Moger, Babu <Babu.Moger@....com>
> Cc: tglx@...utronix.de; mingo@...hat.com; corbet@....net;
> fenghua.yu@...el.com; reinette.chatre@...el.com; peterz@...radead.org;
> gregkh@...uxfoundation.org; davem@...emloft.net; akpm@...ux-
> foundation.org; hpa@...or.com; x86@...nel.org;
> mchehab+samsung@...nel.org; arnd@...db.de;
> kstewart@...uxfoundation.org; pombredanne@...b.com;
> rafael@...nel.org; kirill.shutemov@...ux.intel.com; tony.luck@...el.com;
> qianyue.zj@...baba-inc.com; xiaochen.shen@...el.com;
> pbonzini@...hat.com; Singh, Brijesh <brijesh.singh@....com>; Hurwitz,
> Sherry <sherry.hurwitz@....com>; dwmw2@...radead.org; Lendacky,
> Thomas <Thomas.Lendacky@....com>; luto@...nel.org; joro@...tes.org;
> jannh@...gle.com; vkuznets@...hat.com; rian@...m.mit.edu;
> jpoimboe@...hat.com; linux-kernel@...r.kernel.org; linux-
> doc@...r.kernel.org
> Subject: Re: [PATCH v8 06/13] arch/resctrl: Initialize the resource functions
> that are different
> 
> On Tue, Nov 20, 2018 at 10:59:18AM +0100, Borislav Petkov wrote:
> > So I'm wondering: instead of having mba_wrmsr_intel() and
> > mba_wrmsr_amd() and adding those per-vendor initialization functions,
> > why don't you push down the vendor differentiation into mba_wrmsr()?
> >
> > Then in that function you do
> >
> > 	if (vendor == X86_VENDOR_INTEL)
> > 		__mba_wrmsr_intel();
> > 	else if (vendor == X86_VENDOR_AMD)
> > 		__mba_wrmsr_amd();
> >
> > and so on and then you don't have to do any of that initialization dance
> > here and the struct rdt_resource assignment for the MBA will remain
> > nicely similar to the other ones...
> >
> > Hmmm?
> 
> Yeah, after having look at the patchset further, that might not be a
> good idea as you need to assign more per-vendor stuff than just an MSR
> accessor function...

Ok. No changes here. Thanks

> 
> --
> Regards/Gruss,
>     Boris.
> 
> Good mailing practices for 400: avoid top-posting and trim the reply.

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ