From: Paolo Bonzini <pbonzini@redhat.com>
To: Jim Mattson <jmattson@google.com>,
Sean Christopherson <sean.j.christopherson@intel.com>
Cc: kvm list <kvm@vger.kernel.org>,
Steve Rutherford <srutherford@google.com>,
Jacob Xu <jacobhxu@google.com>, Peter Shier <pshier@google.com>
Subject: Re: [RFC][PATCH] kvm: x86: Improve emulation of CPUID leaves 0BH and 1FH
Date: Tue, 24 Sep 2019 16:01:07 +0200 [thread overview]
Message-ID: <986c2e6d-3784-6f12-b6e8-c859a2d8c166@redhat.com> (raw)
In-Reply-To: <CALMp9eQSd8kMKEdLYTF2ugAYjQO-wAR-PoYmf0NgD2Z4ZVr5FA@mail.gmail.com>
On 18/09/19 20:22, Jim Mattson wrote:
> Aside from the fact that one should never call check_cpuid_limit on
> AMD systems (they don't do the "last basic leaf" nonsense), an
> approach like this should work.
Yeah, I agree it's enough. If there's a complex or really weird
behavior that userspace would most definitely get wrong, we should
design the API to simplify its job.
Paolo
prev parent reply other threads:[~2019-09-24 14:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-12 23:27 [RFC][PATCH] kvm: x86: Improve emulation of CPUID leaves 0BH and 1FH Jim Mattson
2019-09-18 15:32 ` Jim Mattson
2019-09-18 17:43 ` Sean Christopherson
2019-09-18 18:22 ` Jim Mattson
2019-09-18 18:41 ` Jim Mattson
2019-09-19 5:31 ` Xiaoyao Li
2019-09-19 18:26 ` Jim Mattson
2019-09-24 14:01 ` Paolo Bonzini [this message]
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=986c2e6d-3784-6f12-b6e8-c859a2d8c166@redhat.com \
--to=pbonzini@redhat.com \
--cc=jacobhxu@google.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pshier@google.com \
--cc=sean.j.christopherson@intel.com \
--cc=srutherford@google.com \
/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.