From: Sean Christopherson <sean.j.christopherson@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Jim Mattson <jmattson@google.com>, kvm list <kvm@vger.kernel.org>
Subject: Re: KVM_GET_SUPPORTED_CPUID
Date: Fri, 15 Nov 2019 10:01:22 -0800 [thread overview]
Message-ID: <20191115180122.GB6055@linux.intel.com> (raw)
In-Reply-To: <a5845d60-fe38-afc6-e433-4c5a12813026@redhat.com>
On Fri, Nov 15, 2019 at 12:42:17PM +0100, Paolo Bonzini wrote:
> On 14/11/19 21:09, Jim Mattson wrote:
> > If I see "AuthenticAMD" in EBX/EDX/ECX,
> > does that mean that "GenuineIntel" is *not* supported? I thought
> > people were having reasonable success with cross-vendor migration.
>
> This is (2). But in general passing the host value is the safe choice,
> everything else has reasonable success but it's not something I would
> recommend in production (and it's something I wouldn't mind removing,
> really).
Maybe keep it but add a pr_warn_once() to inform the user that exposions
are likely? Or make it opt-in via a module param? I've found this useful
for smoke testing patches that touch AMD/Hygon/Zhaoxin/Centaur code.
next prev parent reply other threads:[~2019-11-15 18:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 20:09 KVM_GET_SUPPORTED_CPUID Jim Mattson
2019-11-15 11:42 ` KVM_GET_SUPPORTED_CPUID Paolo Bonzini
2019-11-15 18:01 ` Sean Christopherson [this message]
2019-11-15 18:33 ` KVM_GET_SUPPORTED_CPUID Jim Mattson
2019-11-15 19:15 ` KVM_GET_SUPPORTED_CPUID Paolo Bonzini
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=20191115180122.GB6055@linux.intel.com \
--to=sean.j.christopherson@intel.com \
--cc=jmattson@google.com \
--cc=kvm@vger.kernel.org \
--cc=pbonzini@redhat.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.