From: "Michael S. Tsirkin" <mst@redhat.com>
To: virtio-comment@lists.linux.dev,
Filip Hejsek <filip.hejsek@gmail.com>,
Maximilian Immanuel Brandtner <maxbr@linux.ibm.com>
Subject: Re: [PATCH] virtio_console: fix order of fields cols and rows
Date: Mon, 13 Oct 2025 04:01:16 -0400 [thread overview]
Message-ID: <20251013035826-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <aOyHZnkkLQBCMAa-@codewreck.org>
On Mon, Oct 13, 2025 at 02:00:22PM +0900, Dominique Martinet wrote:
> Michael S. Tsirkin wrote on Thu, Sep 18, 2025 at 12:18:47PM -0400:
> > While commit 5326ab737a47278dbd16ed3ee7380b26c7056ddd in Linux made it
> > match the spec, no one seems to have implemented it yet host side. It
> > seems better to just drop the change (it was only in 2 releases so far),
> > going back to the status quo.
>
> FWIW, there are other users of the spec e.g. bhyve, which implemented it
> "right" (cols, rows as per the spec -- since 2016):
> https://github.com/freebsd/freebsd-src/blob/main/usr.sbin/bhyve/pci_virtio_console.c#L148
>
> or crossvm (also cols,rows)
> https://github.com/google/crosvm/blob/main/devices/src/virtio/device_constants.rs#L293
>
Indeed, thanks for bringing this to our attention.
> I didn't look to see if there are others (probably some of the other
> rust hypervisor crowd?); I'm not involved in any of them but given there
> are other implementations I'd personally think it makes more sense to
> continue the work of "righting" linux (that is backport the order
> fix)...?
Yes, this is what we normally do. The reason I wanted to do it
differently here is because I did not realize we have implementations.
> I don't have any beef either way as long as the qemu patches aren't
> forgotten (thank you again Filip!); hopefully this can help reach any
> kind of decision.
>
> If this was discussed somewhere else I'd appreciate being pointed to
> it :) I "only" found the recent qemu patches, an attempt to revert the
> fix in linux that was held back, and the stble backport thread where the
> issue was raised but not really discussed either way.
>
> Thanks,
> --
> Dominique Martinet | Asmadeus
OK I guess ... let's get the ball rolling with backporting the Linux
fix?
--
MST
prev parent reply other threads:[~2025-10-13 8:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-18 16:18 [PATCH] virtio_console: fix order of fields cols and rows Michael S. Tsirkin
2025-09-18 17:17 ` Matias Ezequiel Vara Larsen
[not found] ` <aOyHZnkkLQBCMAa-@codewreck.org>
2025-10-13 8:01 ` Michael S. Tsirkin [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=20251013035826-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=filip.hejsek@gmail.com \
--cc=maxbr@linux.ibm.com \
--cc=virtio-comment@lists.linux.dev \
/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