From: "Michael S. Tsirkin" <mst@redhat.com>
To: Jason Wang <jasowang@redhat.com>
Cc: Konstantin Shkolnyy <kshk@linux.ibm.com>,
eperezma@redhat.com, sgarzare@redhat.com, mjrosato@linux.ibm.com,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2] vdpa: Allow vDPA to work on big-endian machine
Date: Sun, 16 Mar 2025 20:36:49 -0400 [thread overview]
Message-ID: <20250316203639-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <CACGkMEsrFoQ9QXYPAGDE6p7FOK=a+vAUv4FePZOkTngn1izCuw@mail.gmail.com>
On Mon, Mar 17, 2025 at 08:26:37AM +0800, Jason Wang wrote:
> On Thu, Mar 13, 2025 at 11:14 PM Konstantin Shkolnyy <kshk@linux.ibm.com> wrote:
> >
> > On 2/23/2025 19:57, Jason Wang wrote:
> > > On Sat, Feb 22, 2025 at 3:08 AM Konstantin Shkolnyy <kshk@linux.ibm.com> wrote:
> > >>
> > >> Add .set_vnet_le() function that always returns success, assuming that
> > >> vDPA h/w always implements LE data format. Otherwise, QEMU disables vDPA and
> > >> outputs the message:
> > >> "backend does not support LE vnet headers; falling back on userspace virtio"
> > >>
> > >> Signed-off-by: Konstantin Shkolnyy <kshk@linux.ibm.com>
> > >> ---
> > >> Changes in V2: Add code comment.
> > >>
> > >
> > > Acked-by: Jason Wang <jasowang@redhat.com>
> >
> > Is this patch all set to be eventually integrated, or more review is needed?
> >
>
> Michael, do you want to queue this or can I do that?
>
> Thanks
Go ahead.
Reviewed-by: Michael S. Tsirkin <mst@redhat.com>
next prev parent reply other threads:[~2025-03-17 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-21 19:07 [PATCH v2] vdpa: Allow vDPA to work on big-endian machine Konstantin Shkolnyy
2025-02-24 1:57 ` Jason Wang
2025-03-13 15:13 ` Konstantin Shkolnyy
2025-03-17 0:26 ` Jason Wang
2025-03-17 0:36 ` Michael S. Tsirkin [this message]
2025-03-14 11:36 ` Eugenio Perez Martin
-- strict thread matches above, loose matches on Subject: below --
2025-06-16 13:36 [PATCH v2] vdpa: Allow VDPA " Konstantin Shkolnyy
2025-06-21 5:52 ` Akihiko Odaki
2026-02-27 18:10 ` Konstantin Shkolnyy
2026-03-04 1:56 ` Jason Wang
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=20250316203639-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=eperezma@redhat.com \
--cc=jasowang@redhat.com \
--cc=kshk@linux.ibm.com \
--cc=mjrosato@linux.ibm.com \
--cc=qemu-devel@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.