qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Jon Doron <arilou@gmail.com>
To: "Maciej S. Szmigiero" <mail@maciej.szmigiero.name>
Cc: Evgeny Yakovlev <eyakovlev@virtuozzo.com>,
	ehabkost@redhat.com, QEMU <qemu-devel@nongnu.org>,
	Roman Kagan <rvkagan@yandex-team.ru>,
	Liran Alon <liran.alon@oracle.com>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Vitaly Kuznetsov <vkuznets@redhat.com>
Subject: Re: [PATCH v1 5/5] i386: Hyper-V VMBus ACPI DSDT entry
Date: Wed, 8 Apr 2020 07:16:39 +0300	[thread overview]
Message-ID: <20200408041639.GA7606@jondnuc> (raw)
In-Reply-To: <8c278ea8-81c5-7458-8979-c319470440d7@maciej.szmigiero.name>

On 07/04/2020, Maciej S. Szmigiero wrote:
>On 07.04.2020 20:56, Roman Kagan wrote:
>> On Mon, Apr 06, 2020 at 11:20:39AM +0300, Jon Doron wrote:
>>> Well I want it to be merged in :-)
>>
>> Hmm I'm curious why, it has little to offer over virtio.
>>
>> Anyway the series you've posted seems to be based on a fairly old
>> version.
>>
>> The one in openvz repo is more recent.  It's still in need for
>> improvement, too, but should be testable at least.

Well I have implemented the hyperv synthetic kernel debugger interface, 
but on Windows 10 it requires to have a working VMBus (it's not really 
using it, but without a function vmbus that will answer to the initiate 
contact then the kdnet will simply be stuck in a loop.

With the synthetic kernel debugger interface you can debug older OS 
(Win7 up to latest Win10). The benefit is that its much faster than all 
other interfaces.

In addition to that Michael Kelley from Microsoft has informed us that 
Microsoft might be dropped the synthetic kernel debugger interface 
sometime in the future, and it seems like the new mode is simply to use 
hvnet device for the communication (which is again much faster).

Cheers,
-- Jon.
>
>Isn't the one at
>https://src.openvz.org/projects/UP/repos/qemu/commits?until=refs%2Fheads%2Fvmbus
>the latest one?
>
>It seems to be last changed in October 2019 - is there a
>later one?
>
>> Thanks,
>> Roman.
>
>Thanks,
>Maciej


  reply	other threads:[~2020-04-08  4:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-03 14:23 [PATCH v1 0/5] hyperv: VMBus implementation Jon Doron
2020-04-03 14:23 ` [PATCH v1 1/5] hyperv: expose API to determine if synic is enabled Jon Doron
2020-04-03 14:23 ` [PATCH v1 2/5] hyperv: SControl is optional to enable SynIc Jon Doron
2020-04-03 14:23 ` [PATCH v1 3/5] vmbus: add vmbus protocol definitions Jon Doron
2020-04-03 14:23 ` [PATCH v1 4/5] vmbus: vmbus implementation Jon Doron
2020-04-03 14:23 ` [PATCH v1 5/5] i386: Hyper-V VMBus ACPI DSDT entry Jon Doron
2020-04-03 14:56   ` Maciej S. Szmigiero
2020-04-03 15:06     ` Jon Doron
2020-04-03 15:30       ` Jon Doron
2020-04-03 15:50         ` Maciej S. Szmigiero
2020-04-03 17:18         ` Maciej S. Szmigiero
2020-04-03 21:00           ` Maciej S. Szmigiero
2020-04-06  7:32             ` Roman Kagan
2020-04-06  8:20               ` Jon Doron
2020-04-07 18:56                 ` Roman Kagan
2020-04-07 19:03                   ` Maciej S. Szmigiero
2020-04-08  4:16                     ` Jon Doron [this message]
2020-04-08 20:47                       ` Roman Kagan
2020-04-09  3:35                         ` Jon Doron
2020-05-12 14:05                           ` Roman Kagan
2020-05-12 15:01                             ` Jon Doron
2020-05-12 15:05                               ` Jon Doron
2020-04-08 20:26                     ` Roman Kagan
2020-04-08 21:42                       ` Maciej S. Szmigiero
2020-04-06 10:14   ` Igor Mammedov
2020-04-03 22:48 ` [PATCH v1 0/5] hyperv: VMBus implementation no-reply

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=20200408041639.GA7606@jondnuc \
    --to=arilou@gmail.com \
    --cc=ehabkost@redhat.com \
    --cc=eyakovlev@virtuozzo.com \
    --cc=liran.alon@oracle.com \
    --cc=mail@maciej.szmigiero.name \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rvkagan@yandex-team.ru \
    --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).