From: Jason Wang <jasowang@redhat.com>
To: David Ahern <dsahern@kernel.org>
Cc: mst@redhat.com, netdev@vger.kernel.org,
virtualization@lists.linux-foundation.org, eperezma@redhat.com,
elic@nvidia.com
Subject: Re: [PATCH V2] vdpa: allow provisioning device features
Date: Wed, 23 Nov 2022 13:50:09 +0800 [thread overview]
Message-ID: <CACGkMEv+LiT_pH9Km5_OW3EpdOoh7ifM85KwLog570hPAQBsqQ@mail.gmail.com> (raw)
In-Reply-To: <f9b35219-ba26-1251-5c78-d96ac91b0995@kernel.org>
On Wed, Nov 23, 2022 at 3:53 AM David Ahern <dsahern@kernel.org> wrote:
>
> On 11/16/22 8:33 PM, Jason Wang wrote:
> > diff --git a/vdpa/include/uapi/linux/vdpa.h b/vdpa/include/uapi/linux/vdpa.h
> > index 94e4dad1..7c961991 100644
> > --- a/vdpa/include/uapi/linux/vdpa.h
> > +++ b/vdpa/include/uapi/linux/vdpa.h
> > @@ -51,6 +51,7 @@ enum vdpa_attr {
> > VDPA_ATTR_DEV_QUEUE_INDEX, /* u32 */
> > VDPA_ATTR_DEV_VENDOR_ATTR_NAME, /* string */
> > VDPA_ATTR_DEV_VENDOR_ATTR_VALUE, /* u64 */
> > + VDPA_ATTR_DEV_FEATURES, /* u64 */
> >
> > /* new attributes must be added above here */
> > VDPA_ATTR_MAX,
>
> this header file already has:
> ...
> VDPA_ATTR_DEV_QUEUE_INDEX, /* u32 */
> VDPA_ATTR_DEV_VENDOR_ATTR_NAME, /* string */
> VDPA_ATTR_DEV_VENDOR_ATTR_VALUE, /* u64 */
>
> VDPA_ATTR_DEV_FEATURES, /* u64 */
>
> /* virtio features that are supported by the vDPA device */
> VDPA_ATTR_VDPA_DEV_SUPPORTED_FEATURES, /* u64 */
>
> /* new attributes must be added above here */
> VDPA_ATTR_MAX,
>
> in which case your diff is not needed. More importantly it raises
> questions about the status of the uapi file (is it correct as is or is
> an update needed) and which tree you are creating patches against?
I'm using git://git.kernel.org/pub/scm/network/iproute2/iproute2 main.
But I don't pull the new codes before sending the patches. Will fix
this.
>
> > @@ -615,8 +640,9 @@ static int cmd_mgmtdev(struct vdpa *vdpa, int argc, char **argv)
> > static void cmd_dev_help(void)
> > {
> > fprintf(stderr, "Usage: vdpa dev show [ DEV ]\n");
> > - fprintf(stderr, " vdpa dev add name NAME mgmtdev MANAGEMENTDEV [ mac MACADDR ] [ mtu MTU ]\n");
> > - fprintf(stderr, " [ max_vqp MAX_VQ_PAIRS ]\n");
> > + fprintf(stderr, " vdpa dev add name NAME mgmtdevMANAGEMENTDEV [ device_features DEVICE_FEATURES]\n");
>
> lost the space between mgmtdev and MANAGEMENTDEV
Will fix it.
Thanks
>
>
> > + fprintf(stderr, " [ mac MACADDR ] [ mtu MTU ]\n");
> > + fprintf(stderr, " [ max_vqp MAX_VQ_PAIRS ]\n");
> > fprintf(stderr, " vdpa dev del DEV\n");
> > fprintf(stderr, "Usage: vdpa dev config COMMAND [ OPTIONS ]\n");
> > fprintf(stderr, "Usage: vdpa dev vstats COMMAND\n");
>
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
prev parent reply other threads:[~2022-11-23 5:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-17 3:33 [PATCH V2] vdpa: allow provisioning device features Jason Wang
2022-11-22 22:29 ` Si-Wei Liu
2022-11-23 3:35 ` Jason Wang
2022-11-23 22:52 ` Si-Wei Liu
2022-11-24 7:13 ` Jason Wang
2022-12-01 0:53 ` Si-Wei Liu
2022-12-05 6:46 ` Jason Wang
2022-12-06 1:42 ` Si-Wei Liu
2022-12-06 3:14 ` Jason Wang
2022-12-07 5:12 ` Si-Wei Liu
2022-12-08 8:02 ` Jason Wang
2022-12-08 8:05 ` Michael S. Tsirkin
[not found] ` <f9b35219-ba26-1251-5c78-d96ac91b0995@kernel.org>
2022-11-23 5:50 ` Jason Wang [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=CACGkMEv+LiT_pH9Km5_OW3EpdOoh7ifM85KwLog570hPAQBsqQ@mail.gmail.com \
--to=jasowang@redhat.com \
--cc=dsahern@kernel.org \
--cc=elic@nvidia.com \
--cc=eperezma@redhat.com \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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;
as well as URLs for NNTP newsgroup(s).