From: Jon Doron <arilou@gmail.com>
To: "Maciej S. Szmigiero" <maciej.szmigiero@oracle.com>
Cc: "Vladimir Sementsov-Ogievskiy" <vsementsov@virtuozzo.com>,
qemu-trivial@nongnu.org, qemu-devel@nongnu.org,
"Roman Kagan" <rvkagan@yandex-team.ru>,
"Denis V. Lunev" <den@openvz.org>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>
Subject: Re: [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained?
Date: Tue, 16 Nov 2021 12:05:11 +0200 [thread overview]
Message-ID: <YZOCV1EFniPx9FLh@jondnuc> (raw)
In-Reply-To: <8caa5fb3-df36-d763-e07b-8fe1667ed7c9@oracle.com>
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.
>
>Thanks,
>Maciej
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.
prev parent reply other threads:[~2021-11-16 10:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-06 13:41 [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained? Philippe Mathieu-Daudé
2021-11-06 13:41 ` [PATCH v4 1/1] hw/hyperv/vmbus: Remove unused vmbus_load/save_req() Philippe Mathieu-Daudé
2021-11-06 19:28 ` [PATCH v4 0/1] hw/hyperv/vmbus: Is it maintained? Maciej S. Szmigiero
2021-11-08 7:30 ` Philippe Mathieu-Daudé
2021-11-13 15:23 ` Maciej S. Szmigiero
2021-11-12 18:32 ` Vladimir Sementsov-Ogievskiy
2021-11-12 20:39 ` Roman Kagan
2021-11-13 15:23 ` Maciej S. Szmigiero
2021-11-16 10:05 ` 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=YZOCV1EFniPx9FLh@jondnuc \
--to=arilou@gmail.com \
--cc=den@openvz.org \
--cc=maciej.szmigiero@oracle.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=rvkagan@yandex-team.ru \
--cc=vsementsov@virtuozzo.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).