From: Paolo Bonzini <pbonzini@redhat.com>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: "Peter Krempa" <pkrempa@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
qemu-devel@nongnu.org,
"Nikolay Shirokovskiy" <nshirokovskiy@virtuozzo.com>,
"Denis V. Lunev" <den@openvz.org>,
"Jiri Denemark" <jdenemar@redhat.com>,
"Richard Henderson" <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/1] x86: add CPU flags supported inside libvirt
Date: Sat, 20 Jul 2019 00:16:21 +0200 [thread overview]
Message-ID: <2993221f-173e-490c-c556-778b627543e8@redhat.com> (raw)
In-Reply-To: <20190719220550.GC26800@habkost.net>
On 20/07/19 00:05, Eduardo Habkost wrote:
>> Actually KVM does not mark it as supported:
>>
>> const u32 kvm_cpuid_7_0_ebx_x86_features =
>> F(FSGSBASE) | F(BMI1) | F(HLE) | F(AVX2) | F(SMEP) |
>> F(BMI2) | F(ERMS) | f_invpcid | F(RTM) | f_mpx | F(RDSEED) |
>> F(ADX) | F(SMAP) | F(AVX512IFMA) | F(AVX512F) | F(AVX512PF) |
>> F(AVX512ER) | F(AVX512CD) | F(CLFLUSHOPT) | F(CLWB) | F(AVX512DQ) |
>> F(SHA_NI) | F(AVX512BW) | F(AVX512VL) | f_intel_pt;
> We can still add the feature name if we also set it on
> .unmigratable_features, but I don't see why it would be useful.
> Is anybody working to support exposing RDT-M to guests?
I don't think so.
Paolo
next prev parent reply other threads:[~2019-07-19 22:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 13:45 [Qemu-devel] [PATCH 1/1] x86: add CPU flags supported inside libvirt Denis V. Lunev
2019-07-18 13:52 ` Paolo Bonzini
2019-07-19 13:00 ` Denis V. Lunev
2019-07-19 20:53 ` Eduardo Habkost, Denis V. Lunev
2019-07-19 21:44 ` Paolo Bonzini
2019-07-19 22:05 ` Eduardo Habkost
2019-07-19 22:16 ` Paolo Bonzini [this message]
2019-08-14 11:36 ` Jiri Denemark
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=2993221f-173e-490c-c556-778b627543e8@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=jdenemar@redhat.com \
--cc=nshirokovskiy@virtuozzo.com \
--cc=pkrempa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).