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] [thread-next>] [day] [month] [year] [list]
Message-ID: <562F990C.6080805@amd.com>
Date:	Tue, 27 Oct 2015 10:32:28 -0500
From:	Aravind Gopalakrishnan <aravind.gopalakrishnan@....com>
To:	Borislav Petkov <bp@...en8.de>
CC:	<tglx@...utronix.de>, <mingo@...hat.com>, <hpa@...or.com>,
	<tony.luck@...el.com>, <x86@...nel.org>, <ashok.raj@...el.com>,
	<linux-kernel@...r.kernel.org>, <linux-edac@...r.kernel.org>,
	<peterz@...radead.org>, <luto@...nel.org>, <dvlasenk@...hat.com>,
	<ross.zwisler@...ux.intel.com>, <dirk.j.brandewie@...el.com>,
	Wan Zongshun <Vincent.Wan@....com>
Subject: Re: [PATCH 2/2] x86/cpufeature: Add CLZERO feature

On 10/26/2015 8:09 PM, Borislav Petkov wrote:
> On Mon, Oct 26, 2015 at 05:50:47PM -0500, Aravind Gopalakrishnan wrote:
>> How do you prefer a V2 for this to be sent though-
>> Shall I wait until your fixes are in tip.git and resend?
>> Or send a V2 on top of current tip.git?
> Actually, I just showed it to hpa and he says those CPUID leafs are
> going to be filled at some point so no need to add them to the scattered
> features list.
>
> If that AMD CPUID leaf 0x80000008 is going to be containing more CPUID
> feature bits - and it sounded like it will because you called it "AMD
> extended features 2" - then those should really go into into the
> x86_capability array, i.e., like you've done it in your initial version.
>
> So please fix the SOB chain of your initial patch and send that one out.
>

Okay, Will do.

Thanks,
-Aravind.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ