From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Lei Wang <lei4.wang@intel.com>
Subject: Why invtsc (CPUID_APM_INVTSC) is unmigratable?
Date: Fri, 19 Jan 2024 14:46:22 +0800 [thread overview]
Message-ID: <825f29d7-9112-45a2-b4a3-7d3b54c3c0a2@intel.com> (raw)
I'm wondering why CPUID_APM_INVTSC is set as unmigratable_flags. Could
anyone explain it?
When the host supports invtsc, it can be exposed to guest.
When the src VM has invtsc exposed, what will forbid it to be migrated
to a dest that also supports VMs with invtsc exposed?
next reply other threads:[~2024-01-19 6:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 6:46 Xiaoyao Li [this message]
2024-01-19 16:14 ` Why invtsc (CPUID_APM_INVTSC) is unmigratable? Marcelo Tosatti
2024-01-20 9:44 ` Xiaoyao Li
2024-01-23 15:39 ` Marcelo Tosatti
2024-01-24 14:52 ` Xiaoyao Li
2024-01-24 22:05 ` Marcelo Tosatti
2024-01-26 8:16 ` Xiaoyao Li
2024-01-29 20:54 ` Marcelo Tosatti
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=825f29d7-9112-45a2-b4a3-7d3b54c3c0a2@intel.com \
--to=xiaoyao.li@intel.com \
--cc=lei4.wang@intel.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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).