From: Borislav Petkov <bp@alien8.de>
To: He Chen <he.chen@linux.intel.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"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 v5 2/3] cpuid: Add a helper in scattered.c to return cpuid
Date: Thu, 10 Nov 2016 12:07:47 +0100 [thread overview]
Message-ID: <20161110110747.t2hn3kynetkuface@pd.tnic> (raw)
In-Reply-To: <1478689528-444-3-git-send-email-he.chen@linux.intel.com>
On Wed, Nov 09, 2016 at 07:05:27PM +0800, He Chen wrote:
> Some sparse CPUID leafs are gathered in a fake leaf to save size of
> x86_capability array in current code, but sometimes, kernel or other
> modules (e.g. KVM cpuid enumeration) may need actual hardware leaf
s/cpuid/CPUID/
> information.
>
> This patch adds a helper get_scattered_cpuid_leaf() to rebuild actual
> CPUID leaf, and it can be called outside by modules.
>
> Signed-off-by: He Chen <he.chen@linux.intel.com>
Modulo $Subject and typo above, the code looks ok to me:
Reviewed-by: Borislav Petkov <bp@suse.de>
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2016-11-10 11:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 11:05 [PATCH v5 0/3] cpuid: Support AVX512_4VNNIW and AVX512_4FMAPS for KVM guest He Chen
2016-11-09 11:05 ` [PATCH v5 1/3] cpuid: cleanup cpuid_regs definitions He Chen
2016-11-10 10:45 ` Borislav Petkov
2016-11-10 11:00 ` Borislav Petkov
2016-11-09 11:05 ` [PATCH v5 2/3] cpuid: Add a helper in scattered.c to return cpuid He Chen
2016-11-10 11:07 ` Borislav Petkov [this message]
2016-11-09 11:05 ` [PATCH v5 3/3] cpuid: add AVX512_4VNNIW and AVX512_4FMAPS instructions support He Chen
2016-11-10 11:19 ` 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=20161110110747.t2hn3kynetkuface@pd.tnic \
--to=bp@alien8.de \
--cc=Piotr.Luc@intel.com \
--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=pbonzini@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
all inboxes | Powered by JetHome®