From: "Michael S. Tsirkin" <mst@redhat.com>
To: David Hildenbrand <david@redhat.com>
Cc: Daniel Verkamp <dverkamp@chromium.org>,
Halil Pasic <pasic@linux.ibm.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org,
virtualization@lists.linux.dev, kvm@vger.kernel.org,
Chandra Merla <cmerla@redhat.com>,
Stable@vger.kernel.org, Cornelia Huck <cohuck@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Eric Farman <farman@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Christian Borntraeger <borntraeger@linux.ibm.com>,
Sven Schnelle <svens@linux.ibm.com>,
Wei Wang <wei.w.wang@intel.com>
Subject: Re: [PATCH v1] s390/virtio_ccw: don't allocate/assign airqs for non-existing queues
Date: Mon, 7 Apr 2025 17:20:05 -0400 [thread overview]
Message-ID: <20250407170239-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <3bbad51d-d7d8-46f7-a28c-11cc3af6ef76@redhat.com>
On Mon, Apr 07, 2025 at 08:47:05PM +0200, David Hildenbrand wrote:
> > In my opinion, it makes the most sense to keep the spec as it is and
> > change QEMU and the kernel to match, but obviously that's not trivial
> > to do in a way that doesn't break existing devices and drivers.
>
> If only it would be limited to QEMU and Linux ... :)
>
> Out of curiosity, assuming we'd make the spec match the current QEMU/Linux
> implementation at least for the 3 involved features only, would there be a
> way to adjust crossvm without any disruption?
>
> I still have the feeling that it will be rather hard to get that all
> implementations match the spec ... For new features+queues it will be easy
> to force the usage of fixed virtqueue numbers, but for free-page-hinting and
> reporting, it's a mess :(
Still thinking about a way to fix drivers... We can discuss this
theoretically, maybe?
--
MST
next prev parent reply other threads:[~2025-04-07 21:20 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-02 20:36 [PATCH v1] s390/virtio_ccw: don't allocate/assign airqs for non-existing queues David Hildenbrand
2025-04-03 9:44 ` Thomas Huth
2025-04-03 12:45 ` Cornelia Huck
2025-04-03 12:57 ` Michael S. Tsirkin
2025-04-03 13:12 ` Christian Borntraeger
2025-04-03 14:18 ` Halil Pasic
2025-04-03 14:28 ` David Hildenbrand
2025-04-04 4:36 ` Halil Pasic
2025-04-04 10:00 ` David Hildenbrand
2025-04-04 10:55 ` David Hildenbrand
2025-04-04 13:36 ` Halil Pasic
2025-04-04 13:48 ` David Hildenbrand
2025-04-04 14:00 ` Halil Pasic
2025-04-04 14:17 ` David Hildenbrand
2025-04-04 15:39 ` Halil Pasic
2025-04-04 16:49 ` David Hildenbrand
2025-04-04 17:36 ` David Hildenbrand
2025-04-07 7:52 ` Michael S. Tsirkin
2025-04-07 8:17 ` David Hildenbrand
2025-04-07 8:34 ` Michael S. Tsirkin
2025-04-07 8:44 ` David Hildenbrand
2025-04-07 8:49 ` Michael S. Tsirkin
2025-04-07 8:54 ` David Hildenbrand
2025-04-07 8:58 ` Michael S. Tsirkin
2025-04-07 9:11 ` David Hildenbrand
2025-04-07 9:13 ` David Hildenbrand
2025-04-07 13:13 ` David Hildenbrand
2025-04-07 17:39 ` Daniel Verkamp
2025-04-07 18:47 ` David Hildenbrand
2025-04-07 21:09 ` Daniel Verkamp
2025-04-09 11:02 ` David Hildenbrand
2025-04-07 21:20 ` Michael S. Tsirkin [this message]
2025-04-09 10:46 ` David Hildenbrand
2025-04-09 10:56 ` Michael S. Tsirkin
2025-04-09 11:12 ` David Hildenbrand
2025-04-09 12:07 ` Michael S. Tsirkin
2025-04-09 12:24 ` David Hildenbrand
2025-04-09 16:08 ` Michael S. Tsirkin
2025-04-07 9:37 ` Michael S. Tsirkin
2025-04-07 13:12 ` Halil Pasic
2025-04-07 13:17 ` David Hildenbrand
2025-04-07 13:28 ` Cornelia Huck
2025-04-07 13:32 ` Michael S. Tsirkin
2025-04-07 17:26 ` Halil Pasic
2025-04-07 8:38 ` David Hildenbrand
2025-04-07 8:44 ` Michael S. Tsirkin
2025-04-07 8:50 ` David Hildenbrand
2025-04-07 9:22 ` David Hildenbrand
2025-04-07 8:41 ` Michael S. Tsirkin
2025-04-06 18:42 ` Michael S. Tsirkin
2025-04-07 7:18 ` David Hildenbrand
2025-04-07 8:54 ` Michael S. Tsirkin
2025-04-07 9:08 ` David Hildenbrand
2025-04-06 15:40 ` Michael S. Tsirkin
2025-04-03 14:35 ` Michael S. Tsirkin
2025-04-04 4:02 ` Halil Pasic
2025-04-04 5:33 ` Michael S. Tsirkin
2025-04-04 12:05 ` Halil Pasic
2025-04-10 18:44 ` David Hildenbrand
2025-04-11 11:11 ` Christian Borntraeger
2025-04-11 12:42 ` Heiko Carstens
2025-04-11 12:47 ` Christian Borntraeger
2025-04-11 13:34 ` David Hildenbrand
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=20250407170239-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Stable@vger.kernel.org \
--cc=agordeev@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cmerla@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=dverkamp@chromium.org \
--cc=farman@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pasic@linux.ibm.com \
--cc=svens@linux.ibm.com \
--cc=thuth@redhat.com \
--cc=virtualization@lists.linux.dev \
--cc=wei.w.wang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.