All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jon Doron <arilou@gmail.com>
To: kvm@vger.kernel.org, linux-hyperv@vger.kernel.org
Cc: vkuznets@redhat.com, pbonzini@redhat.com
Subject: Re: [PATCH v11 0/7] x86/kvm/hyper-v: add support for synthetic debugger
Date: Thu, 7 May 2020 06:01:41 +0300	[thread overview]
Message-ID: <20200507030141.GF2862@jondnuc> (raw)
In-Reply-To: <20200424113746.3473563-1-arilou@gmail.com>

Paolo was this merged in or by any chance in the queue?

Thanks,
-- Jon.

On 24/04/2020, Jon Doron wrote:
>Add support for the synthetic debugger interface of hyper-v, the
>synthetic debugger has 2 modes.
>1. Use a set of MSRs to send/recv information (undocumented so it's not
>   going to the hyperv-tlfs.h)
>2. Use hypercalls
>
>The first mode is based the following MSRs:
>1. Control/Status MSRs which either asks for a send/recv .
>2. Send/Recv MSRs each holds GPA where the send/recv buffers are.
>3. Pending MSR, holds a GPA to a PAGE that simply has a boolean that
>   indicates if there is data pending to issue a recv VMEXIT.
>
>The first mode implementation is to simply exit to user-space when
>either the control MSR or the pending MSR are being set.
>Then it's up-to userspace to implement the rest of the logic of sending/recving.
>
>In the second mode instead of using MSRs KNet will simply issue
>Hypercalls with the information to send/recv, in this mode the data
>being transferred is UDP encapsulated, unlike in the previous mode in
>which you get just the data to send.
>
>The new hypercalls will exit to userspace which will be incharge of
>re-encapsulating if needed the UDP packets to be sent.
>
>There is an issue though in which KDNet does not respect the hypercall
>page and simply issues vmcall/vmmcall instructions depending on the cpu
>type expecting them to be handled as it a real hypercall was issued.
>
>It's important to note that part of this feature has been subject to be
>removed in future versions of Windows, which is why some of the
>defintions will not be present the the TLFS but in the kvm hyperv header
>instead.
>
>v11:
>Fixed all reviewed by and rebased on latest origin/master
>
>Jon Doron (6):
>  x86/kvm/hyper-v: Explicitly align hcall param for kvm_hyperv_exit
>  x86/kvm/hyper-v: Simplify addition for custom cpuid leafs
>  x86/hyper-v: Add synthetic debugger definitions
>  x86/kvm/hyper-v: Add support for synthetic debugger capability
>  x86/kvm/hyper-v: enable hypercalls without hypercall page with syndbg
>  x86/kvm/hyper-v: Add support for synthetic debugger via hypercalls
>
>Vitaly Kuznetsov (1):
>  KVM: selftests: update hyperv_cpuid with SynDBG tests
>
> Documentation/virt/kvm/api.rst                |  18 ++
> arch/x86/include/asm/hyperv-tlfs.h            |   6 +
> arch/x86/include/asm/kvm_host.h               |  14 +
> arch/x86/kvm/hyperv.c                         | 242 ++++++++++++++++--
> arch/x86/kvm/hyperv.h                         |  33 +++
> arch/x86/kvm/trace.h                          |  51 ++++
> arch/x86/kvm/x86.c                            |  13 +
> include/uapi/linux/kvm.h                      |  13 +
> .../selftests/kvm/x86_64/hyperv_cpuid.c       | 143 +++++++----
> 9 files changed, 468 insertions(+), 65 deletions(-)
>
>-- 
>2.24.1
>

  parent reply	other threads:[~2020-05-07  3:01 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-24 11:37 [PATCH v11 0/7] x86/kvm/hyper-v: add support for synthetic debugger Jon Doron
2020-04-24 11:37 ` [PATCH v11 1/7] x86/kvm/hyper-v: Explicitly align hcall param for kvm_hyperv_exit Jon Doron
2020-05-13  8:42   ` Roman Kagan
2020-04-24 11:37 ` [PATCH v11 2/7] x86/kvm/hyper-v: Simplify addition for custom cpuid leafs Jon Doron
2020-05-13  9:24   ` Roman Kagan
2020-05-13 12:49     ` Jon Doron
2020-05-29 11:13       ` Paolo Bonzini
2020-04-24 11:37 ` [PATCH v11 3/7] x86/hyper-v: Add synthetic debugger definitions Jon Doron
2020-04-24 11:37 ` [PATCH v11 4/7] x86/kvm/hyper-v: Add support for synthetic debugger capability Jon Doron
2020-05-29 10:46   ` Paolo Bonzini
2020-05-29 12:08     ` Vitaly Kuznetsov
2020-05-29 12:17       ` Paolo Bonzini
2020-04-24 11:37 ` [PATCH v11 5/7] x86/kvm/hyper-v: enable hypercalls without hypercall page with syndbg Jon Doron
2020-05-13  9:57   ` Roman Kagan
2020-05-13 12:37     ` Jon Doron
2020-05-29 10:48   ` Paolo Bonzini
2020-04-24 11:37 ` [PATCH v11 6/7] x86/kvm/hyper-v: Add support for synthetic debugger via hypercalls Jon Doron
2020-05-12 15:33   ` Roman Kagan
2020-05-13 12:39     ` Jon Doron
2020-04-24 11:37 ` [PATCH v11 7/7] KVM: selftests: update hyperv_cpuid with SynDBG tests Jon Doron
2020-05-07  3:01 ` Jon Doron [this message]
2020-05-07  7:57   ` [PATCH v11 0/7] x86/kvm/hyper-v: add support for synthetic debugger Paolo Bonzini

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=20200507030141.GF2862@jondnuc \
    --to=arilou@gmail.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-hyperv@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --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 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.