qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Denis V. Lunev" <den@openvz.org>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-devel@nongnu.org, Evgeny Yakovlev <eyakovlev@virtuozzo.com>,
	Marcelo Tosatti <mtosatti@redhat.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] fixup! cpu: report hyperv feature words through qom
Date: Thu, 7 Jul 2016 19:53:12 +0300	[thread overview]
Message-ID: <577E88F8.5010102@openvz.org> (raw)
In-Reply-To: <20160707164904.GF4131@thinpad.lan.raisama.net>

On 07/07/2016 07:49 PM, Eduardo Habkost wrote:
> On Thu, Jul 07, 2016 at 01:44:48PM -0300, Eduardo Habkost wrote:
>> Hi,
>>
>> Sorry for taking so long to review it.
>>
>> The patch in general looks good, except for:
>>
>> On Fri, Jun 24, 2016 at 01:49:36PM +0300, Denis V. Lunev wrote:
>> [...]
>>> +    if (MACHINE_GET_CLASS(current_machine)->hot_add_cpu != NULL) {
>>> +        env->features[FEAT_HYPERV_EDX] |= HV_X64_CPU_DYNAMIC_PARTITIONING_AVAILABLE;
>>> +    }
>> [...]
>>> +}
>>> +
>> [...]
>>> -        c->edx |= HV_X64_CPU_DYNAMIC_PARTITIONING_AVAILABLE;
>> If you want to change the rules for setting
>> HV_X64_CPU_DYNAMIC_PARTITIONING_AVAILABLE, please do it in a
>> separate patch.
> I will apply the patch, but with the following fixup:
>
> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
>   target-i386/kvm.c | 4 +---
>   1 file changed, 1 insertion(+), 3 deletions(-)
>
> diff --git a/target-i386/kvm.c b/target-i386/kvm.c
> index 5df4b48..4193fe1 100644
> --- a/target-i386/kvm.c
> +++ b/target-i386/kvm.c
> @@ -599,6 +599,7 @@ static int hyperv_handle_properties(CPUState *cs)
>       if (cpu->hyperv_crash && has_msr_hv_crash) {
>           env->features[FEAT_HYPERV_EDX] |= HV_X64_GUEST_CRASH_MSR_AVAILABLE;
>       }
> +    env->features[FEAT_HYPERV_EDX] |= HV_X64_CPU_DYNAMIC_PARTITIONING_AVAILABLE;
>       if (cpu->hyperv_reset && has_msr_hv_reset) {
>           env->features[FEAT_HYPERV_EAX] |= HV_X64_MSR_RESET_AVAILABLE;
>       }
> @@ -630,9 +631,6 @@ static int hyperv_handle_properties(CPUState *cs)
>           }
>           env->features[FEAT_HYPERV_EAX] |= HV_X64_MSR_SYNTIMER_AVAILABLE;
>       }
> -    if (MACHINE_GET_CLASS(current_machine)->hot_add_cpu != NULL) {
> -        env->features[FEAT_HYPERV_EDX] |= HV_X64_CPU_DYNAMIC_PARTITIONING_AVAILABLE;
> -    }
>       return 0;
>   }
>   
yes, you are right

Reviewed-by: Denis V. Lunev <den@openvz.org>

      reply	other threads:[~2016-07-08  3:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 10:49 [Qemu-devel] [PATCH v3 1/1] cpu: report hyperv feature words through qom Denis V. Lunev
2016-06-30 16:25 ` Denis V. Lunev
2016-07-05 10:26 ` Denis V. Lunev
2016-07-07 16:44 ` Eduardo Habkost
2016-07-07 16:49   ` [Qemu-devel] [PATCH] fixup! " Eduardo Habkost
2016-07-07 16:53     ` Denis V. Lunev [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=577E88F8.5010102@openvz.org \
    --to=den@openvz.org \
    --cc=ehabkost@redhat.com \
    --cc=eyakovlev@virtuozzo.com \
    --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).