From: Paolo Bonzini <pbonzini@redhat.com>
To: "Roman Kagan" <rkagan@virtuozzo.com>,
kvm@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>
Cc: Evgeny Yakovlev <eyakovlev@virtuozzo.com>,
"Denis V . Lunev" <den@openvz.org>,
Eduardo Habkost <ehabkost@redhat.com>,
Igor Mammedov <imammedo@redhat.com>
Subject: Re: [PATCH v2 2/2] x86:kvm:hyperv: make VP_INDEX managed by userspace
Date: Thu, 22 Jun 2017 14:14:48 +0200 [thread overview]
Message-ID: <50c946ce-6eda-6073-d906-18192734f646@redhat.com> (raw)
In-Reply-To: <20170616173740.23272-3-rkagan@virtuozzo.com>
On 16/06/2017 19:37, Roman Kagan wrote:
> control the value of VP_INDEX.
>
> This patch achieves that, by storing vp_index explicitly on vcpu, and
> allowing HV_X64_MSR_VP_INDEX to be set from the host side. For
> compatibility it's initialized to KVM vcpu index. Also a few variables
> are renamed to make clear distinction betweed this Hyper-V vp_index and
> KVM vcpu_id (== APIC id). Besides, a new capability,
> KVM_CAP_HYPERV_VP_INDEX, is added to allow the userspace to skip
> attempting msr writes where unsupported, to avoid spamming error logs.
>
> Signed-off-by: Roman Kagan <rkagan@virtuozzo.com>
The new capability needs documentation.
Paolo
prev parent reply other threads:[~2017-06-22 12:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-16 17:37 [PATCH v2 0/2] x86:kvm:hyperv: fix userspace interaction flaws Roman Kagan
2017-06-16 17:37 ` [PATCH v2 1/2] x86:kvm:hyperv: add KVM_CAP_HYPERV_SYNIC2 Roman Kagan
2017-06-21 20:09 ` Radim Krčmář
2017-06-22 5:14 ` Roman Kagan
2017-06-22 12:06 ` Paolo Bonzini
2017-06-22 12:13 ` Roman Kagan
2017-06-16 17:37 ` [PATCH v2 2/2] x86:kvm:hyperv: make VP_INDEX managed by userspace Roman Kagan
2017-06-22 12:14 ` Paolo Bonzini [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=50c946ce-6eda-6073-d906-18192734f646@redhat.com \
--to=pbonzini@redhat.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=eyakovlev@virtuozzo.com \
--cc=imammedo@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=rkagan@virtuozzo.com \
--cc=rkrcmar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.