qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jon Doron <arilou@gmail.com>
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, vkuznets@redhat.com
Subject: Re: [PATCH v1 0/4] HyperV: Synthetic Debugging device
Date: Sun, 13 Feb 2022 09:49:04 +0200	[thread overview]
Message-ID: <Ygi38JDSYmh0ALZ9@jondnuc> (raw)
In-Reply-To: <20220204100723.406121-1-arilou@gmail.com>

On 04/02/2022, Jon Doron wrote:

Ping

>This patchset adds support for the synthetic debugging device.
>
>HyperV supports a special transport layer for the kernel debugger when
>running in HyperV.
>
>This patchset add supports for this device so you could have a setup
>fast windows kernel debugging.
>
>At this point of time, DHCP is not implmeneted so to set this up few
>things need to be noted.
>
>The scenario I used to test is having 2 VMs in the same virtual network
>i.e a Debugger VM with the NIC:
>-nic tap,model=virtio,mac=02:ca:01:01:01:01,script=/etc/qemu-ifup
>And it's IP is going to be static 192.168.53.12
>And the VM we want to debug, to which we need to have the englightments
>and vmbus configured:
> -cpu host,hv-relaxed,hv_spinlocks=0x1fff,hv_time,+vmx,invtsc,hv-vapic,hv-vpindex,hv-synic,hv-syndbg \
> -device vmbus-bridge \
> -device hv-syndbg,host_ip=192.168.53.12,host_port=50000,use_hcalls=false \
> -nic tap,model=virtio,mac=02:ca:01:01:01:02,script=/etc/qemu-ifup \
>
>Then in the debuggee VM we would setup the kernel debugging in the
>following way:
>
>If the VM is older than Win8:
>* Copy the proper platform kdvm.dll (make sure it's called kdvm.dll even if platform is 32bit)
>bcdedit /set {GUID} dbgtransport kdvm.dll
>bcdedit /set {GUID} loadoptions host_ip="1.2.3.4",host_port="50000",nodhcp
>bcdedit /set {GUID} debug on
>bcdedit /set {GUID} halbreakpoint on
>
>Win8 and late:
>bcdedit /dbgsettings net hostip:7.7.7.7 port:50000 nodhcp
>
>This is all the setup that is required to get the synthetic debugger
>configured correctly.
>
>Jon Doron (4):
>  hyperv: SControl is optional to enable SynIc
>  hyperv: Add definitions for syndbg
>  hyperv: Add support to process syndbg commands
>  hw: hyperv: Initial commit for Synthetic Debugging device
>
> docs/hyperv.txt                  |  15 +
> hw/hyperv/Kconfig                |   5 +
> hw/hyperv/hyperv.c               | 475 +++++++++++++++++++++++++------
> hw/hyperv/meson.build            |   1 +
> hw/hyperv/syndbg.c               | 407 ++++++++++++++++++++++++++
> include/hw/hyperv/hyperv-proto.h |  52 ++++
> include/hw/hyperv/hyperv.h       |  60 ++++
> target/i386/cpu.c                |   2 +
> target/i386/cpu.h                |   7 +
> target/i386/kvm/hyperv-proto.h   |  37 +++
> target/i386/kvm/hyperv-stub.c    |   6 +
> target/i386/kvm/hyperv.c         |  52 +++-
> target/i386/kvm/kvm.c            |  76 ++++-
> 13 files changed, 1105 insertions(+), 90 deletions(-)
> create mode 100644 hw/hyperv/syndbg.c
>
>-- 
>2.34.1
>


      parent reply	other threads:[~2022-02-13  7:51 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-04 10:07 [PATCH v1 0/4] HyperV: Synthetic Debugging device Jon Doron
2022-02-04 10:07 ` [PATCH v1 1/4] hyperv: SControl is optional to enable SynIc Jon Doron
2022-02-16  9:10   ` Emanuele Giuseppe Esposito
2022-02-16 10:27     ` Jon Doron
2022-02-04 10:07 ` [PATCH v1 2/4] hyperv: Add definitions for syndbg Jon Doron
2022-02-16  9:10   ` Emanuele Giuseppe Esposito
2022-02-16 10:27     ` Jon Doron
2022-02-04 10:07 ` [PATCH v1 3/4] hyperv: Add support to process syndbg commands Jon Doron
2022-02-16  9:10   ` Emanuele Giuseppe Esposito
2022-02-16 10:28     ` Jon Doron
2022-02-04 10:07 ` [PATCH v1 4/4] hw: hyperv: Initial commit for Synthetic Debugging device Jon Doron
2022-02-16  9:11   ` Emanuele Giuseppe Esposito
2022-02-16 10:28     ` Jon Doron
2022-02-13  7:49 ` Jon Doron [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=Ygi38JDSYmh0ALZ9@jondnuc \
    --to=arilou@gmail.com \
    --cc=pbonzini@redhat.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).