From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Haozhong Zhang <haozhong.zhang@intel.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
kvm@vger.kernel.org, Marcelo Tosatti <mtosatti@redhat.com>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH 1/3] target-i386: add a subsection of vcpu's TSC rate in vmstate_x86_cpu
Date: Tue, 29 Sep 2015 20:00:13 +0100 [thread overview]
Message-ID: <20150929190013.GO3810@work-vm> (raw)
In-Reply-To: <1443418711-24106-2-git-send-email-haozhong.zhang@intel.com>
* Haozhong Zhang (haozhong.zhang@intel.com) wrote:
> The newly added subsection 'vmstate_tsc_khz' in this patch results in
> vcpu's TSC rate being saved on the source machine and loaded on the
> target machine during the migration.
>
> Signed-off-by: Haozhong Zhang <haozhong.zhang@intel.com>
Hi,
I'd appreciate it if you could tie this to only do it on newer
machine types; that way it won't break back migration.
Dave
> ---
> target-i386/machine.c | 20 ++++++++++++++++++++
> 1 file changed, 20 insertions(+)
>
> diff --git a/target-i386/machine.c b/target-i386/machine.c
> index 9fa0563..80108a3 100644
> --- a/target-i386/machine.c
> +++ b/target-i386/machine.c
> @@ -752,6 +752,25 @@ static const VMStateDescription vmstate_xss = {
> }
> };
>
> +static bool tsc_khz_needed(void *opaque)
> +{
> + X86CPU *cpu = opaque;
> + CPUX86State *env = &cpu->env;
> +
> + return env->tsc_khz != 0;
> +}
> +
> +static const VMStateDescription vmstate_tsc_khz = {
> + .name = "cpu/tsc_khz",
> + .version_id = 1,
> + .minimum_version_id = 1,
> + .needed = tsc_khz_needed,
> + .fields = (VMStateField[]) {
> + VMSTATE_INT64(env.tsc_khz, X86CPU),
> + VMSTATE_END_OF_LIST()
> + }
> +};
> +
> VMStateDescription vmstate_x86_cpu = {
> .name = "cpu",
> .version_id = 12,
> @@ -871,6 +890,7 @@ VMStateDescription vmstate_x86_cpu = {
> &vmstate_msr_hyperv_crash,
> &vmstate_avx512,
> &vmstate_xss,
> + &vmstate_tsc_khz,
> NULL
> }
> };
> --
> 2.4.8
>
>
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2015-09-29 19:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-28 5:38 [Qemu-devel] [PATCH 0/3] target-i386: save/restore vcpu's TSC rate during migration Haozhong Zhang
2015-09-28 5:38 ` [Qemu-devel] [PATCH 1/3] target-i386: add a subsection of vcpu's TSC rate in vmstate_x86_cpu Haozhong Zhang
2015-09-29 19:00 ` Dr. David Alan Gilbert [this message]
2015-09-30 1:17 ` Haozhong Zhang
2015-09-30 8:07 ` Dr. David Alan Gilbert
2015-10-06 1:24 ` Haozhong Zhang
2015-09-28 5:38 ` [Qemu-devel] [PATCH 2/3] target-i386: initialize vcpu's TSC rate to the value from KVM Haozhong Zhang
2015-09-28 16:17 ` Eduardo Habkost
2015-09-29 1:23 ` Haozhong Zhang
2015-09-29 1:46 ` Haozhong Zhang
2015-09-28 5:38 ` [Qemu-devel] [PATCH 3/3] kvm-all: notice KVM of vcpu's TSC rate after migration Haozhong Zhang
2015-09-28 16:37 ` Eduardo Habkost
2015-09-29 3:43 ` Haozhong Zhang
2015-09-29 18:02 ` Eduardo Habkost
2015-09-30 0:32 ` Haozhong Zhang
2015-09-30 20:36 ` Eduardo Habkost
2015-10-06 1:20 ` Haozhong Zhang
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=20150929190013.GO3810@work-vm \
--to=dgilbert@redhat.com \
--cc=ehabkost@redhat.com \
--cc=haozhong.zhang@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=pbonzini@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).