[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained?

From: Jon Doron
Subject: Re: [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained?
Date: Tue, 16 Nov 2021 12:05:11 +0200

On 13/11/2021, Maciej S. Szmigiero wrote:
On 12.11.2021 21:39, Roman Kagan wrote:
On Fri, Nov 12, 2021 at 09:32:31PM +0300, Vladimir Sementsov-Ogievskiy wrote:
Add Den and Roman (his new address)

Thanks, I missed it on the list indeed.

06.11.2021 16:41, Philippe Mathieu-Daudé wrote:
This is the 4th time I send this patch. Is the VMBus infrastructure
used / maintained? Should we deprecate & remove?

I think it's fair to say it's not maintained.  The whole
hw/hyperv/vmbus.c was submitted as a part of the work by Jon to enable
some obscure windows debugging feature which only worked in presence of
VMBus.  It was mostly taken from the respective branch of the (now
effectively abandoned) downstream tree with an implementation of the
core VMBus infrastructure and the devices using it; however, none of the
actual VMBus devices ever made it into the mainline tree.

The VMBus code works fine, is mostly self-contained and by being a part
of the upstream QEMU it does benefit from any improvements done there and
so it is much less likely to bit-rot with time.

I am still committed to upstreaming a Hyper-V Dynamic Memory Protocol
driver (which uses VMBus), however had been preempted by higher-priority
work for now.


Hi guys,

Sorry for the late reply, like Roman I also never got to submit the RFC for the Synth debugger device which requires the VMBus, I do hope to get to it at some point and VMBus is a required part for it.

In the last year or so I have not had much time to spend on this but I do hope to get back to finishing what I have started.

I'm not really sure I have the time or knowledge to maintain VMBus :( but I'll do my best to answer any questions as well.

-- Jon.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]