From: Borislav Petkov <bp@alien8.de>
To: Fenghua Yu <fenghua.yu@intel.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, H Peter Anvin <hpa@zytor.com>,
Ravi V Shankar <ravi.v.shankar@intel.com>,
linux-kernel <linux-kernel@vger.kernel.org>, x86 <x86@kernel.org>
Subject: Re: [RFC PATCH] x86/cpufeatures: Enumerate new AVX512 bfloat16 instructions
Date: Wed, 12 Jun 2019 06:02:59 +0200 [thread overview]
Message-ID: <20190612040259.GC32652@zn.tnic> (raw)
In-Reply-To: <20190612033259.GE180343@romley-ivt3.sc.intel.com>
On Tue, Jun 11, 2019 at 08:32:59PM -0700, Fenghua Yu wrote:
> Currently KVM doesn't simulate scattered features (the ones in CPUID_LNX_*
> in cpuid_leafs) as reverse_cpuid[] doesn't contain CPUID_LNX_*.
43500e6f294d ("x86/cpufeatures: Remove get_scattered_cpuid_leaf()")
> After the X86_FEATURES_CQM_* features are changed to scattered features,
> they will not be simulated by KVM any more as CPUID_F_0_EDX and CPUID_F_1_EDX
> are removed.
Does KVM even support resctrl? I doubt only exporting a couple of CPUID
bits into the guest is enough...
> Should patch #1 simulate X86_FEATURE_CQM_* in KVM? Or let KVM guys handle
> the scattered features?
Right, the scattered thing was removed as KVM didn't need it,
apparently, see above.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2019-06-12 4:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-10 17:02 [RFC PATCH] x86/cpufeatures: Enumerate new AVX512 bfloat16 instructions Fenghua Yu
2019-06-10 19:20 ` Borislav Petkov
2019-06-11 18:19 ` Fenghua Yu
2019-06-11 19:47 ` Borislav Petkov
2019-06-11 22:28 ` Fenghua Yu
2019-06-12 3:29 ` Yu, Fenghua
2019-06-12 3:59 ` Borislav Petkov
2019-06-12 17:41 ` Fenghua Yu
2019-06-12 3:32 ` Fenghua Yu
2019-06-12 4:02 ` Borislav Petkov [this message]
2019-06-12 14:10 ` Sean Christopherson
2019-06-12 17:04 ` Fenghua Yu
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=20190612040259.GC32652@zn.tnic \
--to=bp@alien8.de \
--cc=fenghua.yu@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=ravi.v.shankar@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.