From: Alexander Graf <graf@amazon.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
"Denis V. Lunev" <den@openvz.org>,
Sean Christopherson <seanjc@google.com>,
Valeriy Vdovin <valeriy.vdovin@virtuozzo.com>
Cc: <linux-kernel@vger.kernel.org>, Jonathan Corbet <corbet@lwn.net>,
"Vitaly Kuznetsov" <vkuznets@redhat.com>,
Wanpeng Li <wanpengli@tencent.com>,
"Jim Mattson" <jmattson@google.com>,
Joerg Roedel <joro@8bytes.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "Borislav Petkov" <bp@alien8.de>,
<x86@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Shuah Khan <shuah@kernel.org>,
Aaron Lewis <aaronlewis@google.com>,
"Andrew Jones" <drjones@redhat.com>,
Oliver Upton <oupton@google.com>,
Like Xu <like.xu@linux.intel.com>, <kvm@vger.kernel.org>,
<linux-doc@vger.kernel.org>, <linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v4] KVM: x86: Fix KVM_GET_CPUID2 ioctl to return cpuid entries count
Date: Tue, 4 May 2021 11:26:20 +0200 [thread overview]
Message-ID: <b4434730-9cd1-1d41-d012-f7beff7e351b@amazon.com> (raw)
In-Reply-To: <514b5373-c07b-ad34-5fba-f8850faf6d68@redhat.com>
On 04.05.21 10:21, Paolo Bonzini wrote:
>
> On 04/05/21 10:15, Denis V. Lunev wrote:
>> As far as I understand only some testing within kernel now.
>> Though we have plans to expose it for QAPI as the series
>> in QEMU
>> [PATCH 1/2] qapi: fix error handling for x-vz-query-cpu-model-cpuid
>> [PATCH 2/2] qapi: blacklisted x-vz-query-cpu-model-cpuid in tests
>> is not coming in a good way.
>> The idea was to avoid manual code rework in QEMU and
>> expose collected model at least for debug.
>
> KVM_GET_CPUID2 as a VM ioctl cannot expose the whole truth about CPUID
> either, since it doesn't handle the TSX_CTRL_CPUID_CLEAR bit. Given
> that QEMU doesn't need KVM_GET_CPUID2; it only needs to save whatever it
> passed to KVM_SET_CPUID2.
What if we instead deflect CPUID into user space so it can emulate it in
whatever way it likes? Is the performance difference going to be
relevant? Are people still using cpuid as barrier these days?
Alex
Amazon Development Center Germany GmbH
Krausenstr. 38
10117 Berlin
Geschaeftsfuehrung: Christian Schlaeger, Jonathan Weiss
Eingetragen am Amtsgericht Charlottenburg unter HRB 149173 B
Sitz: Berlin
Ust-ID: DE 289 237 879
next prev parent reply other threads:[~2021-05-04 9:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 17:27 [PATCH v4] KVM: x86: Fix KVM_GET_CPUID2 ioctl to return cpuid entries count Valeriy Vdovin
2021-04-29 1:00 ` Sean Christopherson
2021-05-03 14:54 ` Paolo Bonzini
2021-05-03 19:18 ` Denis V. Lunev
2021-05-04 7:23 ` Paolo Bonzini
2021-05-04 8:15 ` Denis V. Lunev
2021-05-04 8:21 ` Paolo Bonzini
2021-05-04 9:26 ` Alexander Graf [this message]
2021-05-04 9:50 ` Paolo Bonzini
2021-05-04 16:52 ` Jim Mattson
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=b4434730-9cd1-1d41-d012-f7beff7e351b@amazon.com \
--to=graf@amazon.com \
--cc=aaronlewis@google.com \
--cc=bp@alien8.de \
--cc=corbet@lwn.net \
--cc=den@openvz.org \
--cc=drjones@redhat.com \
--cc=hpa@zytor.com \
--cc=jmattson@google.com \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=like.xu@linux.intel.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=oupton@google.com \
--cc=pbonzini@redhat.com \
--cc=seanjc@google.com \
--cc=shuah@kernel.org \
--cc=tglx@linutronix.de \
--cc=valeriy.vdovin@virtuozzo.com \
--cc=vkuznets@redhat.com \
--cc=wanpengli@tencent.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).