qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Jon Doron <arilou@gmail.com>, qemu-devel@nongnu.org
Cc: vkuznets@redhat.com
Subject: Re: [PATCH v1 1/1] hyperv: Enable SCONTROL if SYNIC is enabled
Date: Mon, 10 Aug 2020 19:27:54 +0200	[thread overview]
Message-ID: <837db114-d7a3-7e0b-dfd4-db136711c120@redhat.com> (raw)
In-Reply-To: <20200717125639.1103876-2-arilou@gmail.com>

On 17/07/20 14:56, Jon Doron wrote:
> Based on an analysis of the HyperV firmwares (Gen1 and Gen2) it seems
> like the SCONTROL is not being set to the ENABLED state as like we have
> thought.
> 
> Also from a test done by Vitaly Kuznetsov, running a nested HyperV it
> was concluded that the first access to the SCONTROL MSR with a read
> resulted with the value of 0x1, aka HV_SYNIC_CONTROL_ENABLE.
> 
> It's important to note that this diverges from the value states in the
> HyperV TLFS of 0.
> 
> Signed-off-by: Jon Doron <arilou@gmail.com>
> ---
>  target/i386/kvm.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index b8455c89ed..6a62e8ae94 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -1904,6 +1904,8 @@ void kvm_arch_reset_vcpu(X86CPU *cpu)
>  
>      if (hyperv_feat_enabled(cpu, HYPERV_FEAT_SYNIC)) {
>          int i;
> +
> +        env->msr_hv_synic_control = HV_SYNIC_ENABLE;
>          for (i = 0; i < ARRAY_SIZE(env->msr_hv_synic_sint); i++) {
>              env->msr_hv_synic_sint[i] = HV_SINT_MASKED;
>          }
> 

Are both patches needed or only the Hyper-V one?

Paolo



  reply	other threads:[~2020-08-10 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-17 12:56 [PATCH v1 0/1] hyperv: Enable SCONTROL if SYNIC is enabled Jon Doron
2020-07-17 12:56 ` [PATCH v1 1/1] " Jon Doron
2020-08-10 17:27   ` Paolo Bonzini [this message]
2020-08-10 17:40     ` Jon Doron

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=837db114-d7a3-7e0b-dfd4-db136711c120@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=arilou@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=vkuznets@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 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).