From: Konstantin Shkolnyy <kshk@linux.ibm.com>
To: Michael Tokarev <mjt@tls.msk.ru>, eperezma@redhat.com
Cc: mst@redhat.com, sgarzare@redhat.com, mjrosato@linux.ibm.com,
qemu-devel@nongnu.org, qemu-stable <qemu-stable@nongnu.org>
Subject: Re: [PATCH v2] vdpa: Fix endian bugs in shadow virtqueue
Date: Thu, 27 Feb 2025 14:05:40 -0600 [thread overview]
Message-ID: <1f86d715-68c9-428e-9e81-02dc6513e980@linux.ibm.com> (raw)
In-Reply-To: <245054bd-685e-4261-8192-ed2e95c91994@tls.msk.ru>
On 2/27/2025 00:33, Michael Tokarev wrote:
> 25.02.2025 15:39, Konstantin Shkolnyy wrote:
>> On 2/25/2025 03:30, Michael Tokarev wrote:
>
>>> This looks like a qemu-stable material.
>>> Please let me know if it is not.
>>
>> It won't help without my other "[PATCH v2] vdpa: Allow vDPA to work on
>> big-endian machine". With both patches, VDPA works on a big-endian
>> machine.
>
> Aha. And it is not in master yet. Thank you for letting me know!
>
> How do you think, is it worth the effort to pick these up for
> older stable releases (7.2, 8.2) too?
Yes. It's legitimate bugfixes. I suspect, more and more people will use
VDPA as time goes by, so someone might try it on s390 with a stable QEMU.
prev parent reply other threads:[~2025-02-27 20:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-12 16:49 [PATCH v2] vdpa: Fix endian bugs in shadow virtqueue Konstantin Shkolnyy
2025-02-12 18:11 ` Philippe Mathieu-Daudé
2025-02-13 6:43 ` Eugenio Perez Martin
2025-02-13 12:24 ` Philippe Mathieu-Daudé
2025-02-13 6:49 ` Eugenio Perez Martin
2025-02-14 2:24 ` Lei Yang
2025-02-14 13:01 ` Konstantin Shkolnyy
2025-02-14 13:02 ` Konstantin Shkolnyy
2025-02-15 8:21 ` Lei Yang
2025-02-25 9:30 ` Michael Tokarev
2025-02-25 12:39 ` Konstantin Shkolnyy
2025-02-27 6:33 ` Michael Tokarev
2025-02-27 20:05 ` Konstantin Shkolnyy [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=1f86d715-68c9-428e-9e81-02dc6513e980@linux.ibm.com \
--to=kshk@linux.ibm.com \
--cc=eperezma@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=mjt@tls.msk.ru \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=sgarzare@redhat.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.