qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Qemu-devel] [PATCH] target/i386: kvm: just return after migrate_add


From: Dr. David Alan Gilbert
Subject: Re: [Qemu-devel] [PATCH] target/i386: kvm: just return after migrate_add_blocker failed
Date: Mon, 8 Oct 2018 12:12:44 +0100
User-agent: Mutt/1.10.1 (2018-07-13)

* Li Qiang (address@hidden) wrote:
> When migrate_add_blocker failed, the invtsc_mig_blocker is not
> appended so no need to remove. This can save several instructions.
> 
> Signed-off-by: Li Qiang <address@hidden>
> ---
>  target/i386/kvm.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 0b2a07d3a4..6ba84a39f3 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -1153,7 +1153,7 @@ int kvm_arch_init_vcpu(CPUState *cs)
>              if (local_err) {
>                  error_report_err(local_err);
>                  error_free(invtsc_mig_blocker);
> -                goto fail;
> +                return r;

So I think that's OK, however, I wonder if fail: should be
doing some more cleanup?
For example, I notice we've added cpu_update_state to the change state
handler's before that point, should that be removed?

Dave

>              }
>              /* for savevm */
>              vmstate_x86_cpu.unmigratable = 1;
> -- 
> 2.17.1
> 
> 
--
Dr. David Alan Gilbert / address@hidden / Manchester, UK



reply via email to

[Prev in Thread] Current Thread [Next in Thread]