From: Paolo Abeni <pabeni@redhat.com>
To: virtio-comment@lists.linux.dev
Cc: Jason Wang <jasowang@redhat.com>,
Willem de Bruijn <willemb@google.com>,
mst@redhat.com, Parav Pandit <parav@nvidia.com>,
mvaralar@redhat.com, cohuck@redhat.com
Subject: Re: [PATCH v2] virtio-net: clarify guest offloads <> features mapping
Date: Mon, 9 Mar 2026 09:03:50 +0100 [thread overview]
Message-ID: <561fbba3-ea26-41e1-bb83-23fc0e1d5110@redhat.com> (raw)
In-Reply-To: <6af50c9ada76d8168d248827e4af7c44bdfa34a8.1747826378.git.pabeni@redhat.com>
Hi,
On 5/21/25 1:20 PM, Paolo Abeni wrote:
> The guest offloads, as specified by 'Setting Offloads State,' use a
> 64-bit wide space, while some of the corresponding virtio net features
> are in the upper 64 bits of a 128-bit wide space.
>
> Clarify the relevant mapping as somewhat implied by the current text.
> Also rename the offload definitions to avoid referring to different
> numeric values with the same name in the features table and in the
> offload table.
>
> Fixes: https://github.com/oasis-tcs/virtio-spec/issues/225
> Signed-off-by: Paolo Abeni <pabeni@redhat.com>
> ---
> v1 -> v2:
> - restrict the mapped range to the guest offload (Parav)
> v1: https://lore.kernel.org/virtio-comment/a30de484ff56065f56e37446e08dcdfa4850f101.1747649330.git.pabeni@redhat.com/
I'm sorry for the very long delay here. It was not clear to me I should
have explicitly asked a ballot on v2, too. Let me do that now:
Fixes: https://github.com/oasis-tcs/virtio-spec/issues/225
I would like to ask a vote on this issues, thanks!
Paolo
prev parent reply other threads:[~2026-03-09 8:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 11:20 [PATCH v2] virtio-net: clarify guest offloads <> features mapping Paolo Abeni
2025-05-29 6:11 ` Jason Wang
2026-03-09 8:03 ` Paolo Abeni [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=561fbba3-ea26-41e1-bb83-23fc0e1d5110@redhat.com \
--to=pabeni@redhat.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=mvaralar@redhat.com \
--cc=parav@nvidia.com \
--cc=virtio-comment@lists.linux.dev \
--cc=willemb@google.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