linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: <tglx@linutronix.de>, <mingo@redhat.com>, <hpa@zytor.com>,
	<tony.luck@intel.com>, <x86@kernel.org>, <ashok.raj@intel.com>,
	<linux-kernel@vger.kernel.org>, <linux-edac@vger.kernel.org>,
	<peterz@infradead.org>, <luto@kernel.org>, <dvlasenk@redhat.com>,
	<ross.zwisler@linux.intel.com>, <dirk.j.brandewie@intel.com>,
	Wan Zongshun <Vincent.Wan@amd.com>
Subject: Re: [PATCH 2/2] x86/cpufeature: Add CLZERO feature
Date: Mon, 26 Oct 2015 10:13:33 -0500	[thread overview]
Message-ID: <562E431D.1070908@amd.com> (raw)
In-Reply-To: <20151025103703.GB6084@nazgul.tnic>

(removing peter.p.waskiewicz.jr@intel.com as email bounced)

On 10/25/2015 5:37 AM, Borislav Petkov wrote:
> On Fri, Oct 23, 2015 at 06:18:33AM -0500, Aravind Gopalakrishnan wrote:
>> CLZERO instruction introduced in AMD Fam17h processors
>> zero's out a 64 byte cache line specified in RAX.
>>
>> Add the bit here to allow /proc/cpuinfo to list the feature
>>
>> Signed-off-by: Wan Zongshun <Vincent.Wan@amd.com>
>> Signed-off-by: Aravind Gopalakrishnan <aravind.gopalakrishnan@amd.com>
> This SOB chain looks wrong - if Vincent is the author and you're only
> sending the patch, then his "From:" needs to appear before the commit
> message. git send-email does that correctly, provided the authorship is
> correctly set in the local branch you're sending the patch from.

For large part yes, wrapped code in patch form with commit message etc.
And modified comment a little bit.

Does that still require his address in "From"?

>>   
>>   /*
>> @@ -255,6 +255,9 @@
>>   /* Intel-defined CPU QoS Sub-leaf, CPUID level 0x0000000F:1 (edx), word 12 */
>>   #define X86_FEATURE_CQM_OCCUP_LLC (12*32+ 0) /* LLC occupancy monitoring if 1 */
>>   
>> +/* AMD extended feature extension, CPUID level 0x80000008 (ebx), word 13 */
> extended ... extension sounds like a tautology, please sanitize.

Haha. True. But looks like that's actually it's name.

If tautologies are not your thing, how about changing comments around 
0x80000001,ecx to say "AMD extended features 1" and
for 0x80000008, ebx say "AMD extended features 2"?

Thanks,
-Aravind.

      parent reply	other threads:[~2015-10-26 15:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-23 11:18 [PATCH 0/2] Add new features introduced in AMD Fam17h Aravind Gopalakrishnan
2015-10-23 11:18 ` [PATCH 1/2] x86/mcheck: Add Scalable MCA cpuid bit Aravind Gopalakrishnan
2015-10-23 11:18 ` [PATCH 2/2] x86/cpufeature: Add CLZERO feature Aravind Gopalakrishnan
2015-10-25 10:37   ` Borislav Petkov
2015-10-26 15:12     ` Aravind Gopalakrishnan
2015-10-26 20:22       ` Borislav Petkov
2015-10-26 21:01         ` [RFC PATCH] x86/cpu: Move sparsely used bit leafs into scattered features (was: Re: [PATCH 2/2] x86/cpufeature: Add CLZERO feature) Borislav Petkov
2015-10-27  2:56           ` Andy Lutomirski
2015-10-27  3:22             ` Borislav Petkov
2015-10-26 22:50         ` [PATCH 2/2] x86/cpufeature: Add CLZERO feature Aravind Gopalakrishnan
2015-10-27  1:09           ` Borislav Petkov
2015-10-27 15:32             ` Aravind Gopalakrishnan
2015-10-27 16:48             ` Aravind Gopalakrishnan
2015-10-27 22:45               ` Borislav Petkov
2015-10-26 15:13     ` Aravind Gopalakrishnan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=562E431D.1070908@amd.com \
    --to=aravind.gopalakrishnan@amd.com \
    --cc=Vincent.Wan@amd.com \
    --cc=ashok.raj@intel.com \
    --cc=bp@alien8.de \
    --cc=dirk.j.brandewie@intel.com \
    --cc=dvlasenk@redhat.com \
    --cc=hpa@zytor.com \
    --cc=linux-edac@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=tglx@linutronix.de \
    --cc=tony.luck@intel.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).