From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: "Xuan Zhuo" <xuanzhuo@linux.alibaba.com>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Marcel Apfelbaum" <marcel.apfelbaum@gmail.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Yanan Wang" <wangyanan55@huawei.com>
Subject: Re: [PATCH RFC] virtio-balloon: make it spec compliant
Date: Wed, 10 Jul 2024 05:15:18 +0200 [thread overview]
Message-ID: <6f99d0dc-8cad-435c-ad58-ffa69f44b2c0@redhat.com> (raw)
In-Reply-To: <8de2d4a6407d796d4d793975fc88e2f929f6025d.1720128585.git.mst@redhat.com>
On 04.07.24 23:30, Michael S. Tsirkin wrote:
> Currently, if VIRTIO_BALLOON_F_FREE_PAGE_HINT is off but
> VIRTIO_BALLOON_F_REPORTING is on, then the reporting vq
> gets number 3 while spec says it's number 4.
> It happens to work because the linux virtio pci driver
> is *also* out of spec.
>
> To fix:
> 1. add vq4 as per spec
> 2. to help out the buggy Linux driver, in the above configuration,
> also create vq3, and handle it exactly as we do vq4.
>
> I think that some clever hack is doable to address the issue
> for existing machine types (which would get it in user's hands
> sooner), but I'm not 100% sure what, exactly.
>
> This is a simpler, straight-forward approach.
>
> Reported-by: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>
> I don't think I'll stop here, I want to fix exiting machine types,
> but sending this here for comparison.
> I'll send a Linux patch later.
The downside is that new machine types will stop working with mainline
Linux / major distros in that feature combination, right?
What's the approach that you are thinking of?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2024-07-10 3:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-04 21:30 [PATCH RFC] virtio-balloon: make it spec compliant Michael S. Tsirkin
2024-07-10 3:15 ` David Hildenbrand [this message]
2024-07-10 6:13 ` Michael S. Tsirkin
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=6f99d0dc-8cad-435c-ad58-ffa69f44b2c0@redhat.com \
--to=david@redhat.com \
--cc=eduardo@habkost.net \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wangyanan55@huawei.com \
--cc=xuanzhuo@linux.alibaba.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).