From: David Hildenbrand <david@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: linux-kernel@vger.kernel.org,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Xuan Zhuo <xuanzhuo@linux.alibaba.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 0/2] virtio-balloon: make it spec compliant
Date: Wed, 10 Jul 2024 05:09:16 +0200 [thread overview]
Message-ID: <df74b121-c0fd-41e1-b42f-64dd73ace352@redhat.com> (raw)
In-Reply-To: <20240705073122-mutt-send-email-mst@kernel.org>
Sorry for the late reply!
>> I understand that concern, IIUC it would imply that:
>>
>> a) In case of a hypervisor, we never ran with a Linux guest
>> b) In case of a guest, we never ran under QEMU
>
> Or maybe VIRTIO_BALLOON_F_FREE_PAGE_HINT is set.
Right, in which case it would be according to the spec.
>> It's certainly possible, although I would assume that most other
>> implementation candidates (e.g., cloud-hypervisor) would have complained by
>> now about Linux issues.
>
> They either set VIRTIO_BALLOON_F_FREE_PAGE_HINT or followed linux bug to
> work around.
Okay, in the latter case it would be the unofficial way of doing it.
>> What's your experience: if someone would actually implement it according to
>> the spec, would they watch out on the virtio mailing lists for changes (or
>> even be able to vote) and would be able to comment that adjusting the spec
>> to the real first implementation is wrong?
>
> Unfortunately my experience is that it's not that likely :(
That's what I thought, unfortunately.
>
>
> Whatever we do, we need to take existing setups into account.
>
> How would we do it in the spec without breaking working setups? I guess
> we could say that both behaviours are legal. That would still mean we
> need the qemu and linux patches, right?
That makes sense to me. Let me take a look at the patches.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2024-07-10 3:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 10:08 Michael S. Tsirkin
2024-07-05 10:08 ` [PATCH 1/2] virtio_balloon: add work around for out of spec QEMU Michael S. Tsirkin
2024-07-10 3:11 ` David Hildenbrand
2024-07-10 3:23 ` Jason Wang
2024-07-10 6:16 ` Michael S. Tsirkin
2024-07-10 7:37 ` Jason Wang
2024-07-10 11:36 ` Michael S. Tsirkin
2024-07-05 10:09 ` [PATCH 2/2] virtio: fix vq # when vq skipped Michael S. Tsirkin
2024-07-10 3:11 ` David Hildenbrand
2024-07-10 3:25 ` Jason Wang
2024-07-05 10:15 ` [PATCH 0/2] virtio-balloon: make it spec compliant David Hildenbrand
2024-07-05 10:19 ` Michael S. Tsirkin
2024-07-05 11:00 ` David Hildenbrand
2024-07-05 11:38 ` Michael S. Tsirkin
2024-07-10 3:09 ` David Hildenbrand [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=df74b121-c0fd-41e1-b42f-64dd73ace352@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.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
all inboxes | Powered by JetHome®