public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Borislav Petkov <bp@alien8.de>, He Chen <he.chen@linux.intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	x86@kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"Ingo Molnar" <mingo@redhat.com>,
	"H . Peter Anvin" <hpa@zytor.com>,
	"Luwei Kang" <luwei.kang@intel.com>,
	"Piotr Luc" <Piotr.Luc@intel.com>
Subject: Re: [PATCH v3] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest
Date: Fri, 4 Nov 2016 15:53:02 +0100	[thread overview]
Message-ID: <ecdc20d5-e5c2-cab7-2973-39c811cac42c@redhat.com> (raw)
In-Reply-To: <20161104105235.qbqvmsv4ikajvjtu@pd.tnic>



On 04/11/2016 11:52, Borislav Petkov wrote:
> Please CC me on your future submissions, thanks.
> 
> On Fri, Nov 04, 2016 at 03:07:19PM +0800, He Chen wrote:
>> The spec can be found in Intel Software Developer Manual or in
>> Instruction Set Extensions Programming Reference.
> 
> This commit message is completely useless. Write commit messages in
> the way as if you're explaining to another person *why* this change is
> needed and that other person doesn't have an idea what you're doing.
> 
>> Signed-off-by: Luwei Kang <luwei.kang@intel.com>
>> Signed-off-by: He Chen <he.chen@linux.intel.com>
> 
> This SOB chain means what exactly?
> 
>> ---
>> Changes in v3:
>> * add a helper in scattered.c to get scattered leaf.
> 
> The modification to scattered et al without the kvm use should be a
> separate patch.

With no usage?  Sounds like a good use of Acked-by. :)

>> +u32 get_scattered_cpuid_leaf(unsigned int level, unsigned int sub_leaf,
>> +			     enum cpuid_regs_idx reg)
> 
> Align arguments on the opening brace.

They are aligned.

Paolo

>> +{
>> +	u32 cpuid_val = 0;
>> +	const struct cpuid_bit *cb;
> 
> 
> Please sort function local variables declaration in a reverse christmas
> tree order:
> 
> 	<type> longest_variable_name;
> 	<type> shorter_var_name;
> 	<type> even_shorter;
> 	<type> i;
> 
>> +
>> +	for (cb = cpuid_bits; cb->feature; cb++) {
>> +
>> +		if (level > cb->level)
>> +			continue;
>> +
>> +		if (level < cb->level)
>> +			break;
>> +
>> +		if (reg == cb->reg && sub_leaf == cb->sub_leaf) {
>> +			if (cpu_has(&boot_cpu_data, cb->feature))
>> +				cpuid_val |= BIT(cb->bit);
>> +		}
>> +	}
>> +
>> +	return cpuid_val;
>> +}
> 

  reply	other threads:[~2016-11-04 14:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-04  7:07 [PATCH v3] x86/cpuid: expose AVX512_4VNNIW and AVX512_4FMAPS features to kvm guest He Chen
2016-11-04 10:52 ` Borislav Petkov
2016-11-04 14:53   ` Paolo Bonzini [this message]
2016-11-04 15:06     ` Borislav Petkov
2016-11-04 15:13       ` Paolo Bonzini
2016-11-04 15:57         ` Borislav Petkov
2016-11-04 15:58           ` Paolo Bonzini
2016-11-07 16:52         ` Thomas Gleixner
2016-11-07  2:10   ` He Chen
2016-11-07  9:05     ` Borislav Petkov
2016-11-07 16:47       ` Thomas Gleixner
2016-11-07 17:07         ` Borislav Petkov

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=ecdc20d5-e5c2-cab7-2973-39c811cac42c@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=Piotr.Luc@intel.com \
    --cc=bp@alien8.de \
    --cc=he.chen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luwei.kang@intel.com \
    --cc=mingo@redhat.com \
    --cc=rkrcmar@redhat.com \
    --cc=tglx@linutronix.de \
    --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