From: Parav Pandit <parav@nvidia.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: "virtio-comment@lists.oasis-open.org"
<virtio-comment@lists.oasis-open.org>,
"virtio-dev@lists.oasis-open.org"
<virtio-dev@lists.oasis-open.org>,
"jasowang@redhat.com" <jasowang@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: [virtio-comment] RE: RE: RE: [virtio-dev] [PATCH v14 RESENT] virtio-net: support device stats
Date: Tue, 15 Aug 2023 07:25:30 +0000 [thread overview]
Message-ID: <PH0PR12MB54818284442C3DE2900F5E13DC14A@PH0PR12MB5481.namprd12.prod.outlook.com> (raw)
In-Reply-To: <1692080940.1446962-7-xuanzhuo@linux.alibaba.com>
> From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> Sent: Tuesday, August 15, 2023 11:59 AM
> On Tue, 15 Aug 2023 06:17:14 +0000, Parav Pandit <parav@nvidia.com> wrote:
> >
> > > From: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
> > > Sent: Tuesday, August 15, 2023 11:29 AM
> >
> >
> > > This version already has the bitmap. I forgot to change the commit log.
> >
> > Please move to access via DMA interface discussed under subject "virtio-net:
> support access and control the member devices".
> > For virtio net this dma interface of cvq already exists. Please relocate it to a
> cvq command.
>
>
> OK.
Forgot to mention that please keep this bitmap as an array like,
supported_stats[1];
like how Michael did,
le64 device_admin_cmd_opcodes[];
so that code will be able treat it as array + bitmap from beginning.
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
prev parent reply other threads:[~2023-08-15 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 7:49 [virtio-comment] [PATCH v14 RESENT] virtio-net: support device stats Xuan Zhuo
2023-08-07 6:15 ` [virtio-comment] Re: [virtio-dev] " Xuan Zhuo
2023-08-15 3:39 ` Xuan Zhuo
2023-08-15 4:37 ` [virtio-comment] " Parav Pandit
2023-08-15 5:59 ` [virtio-comment] " Xuan Zhuo
2023-08-15 6:17 ` [virtio-comment] " Parav Pandit
2023-08-15 6:29 ` [virtio-comment] " Xuan Zhuo
2023-08-15 7:25 ` Parav Pandit [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=PH0PR12MB54818284442C3DE2900F5E13DC14A@PH0PR12MB5481.namprd12.prod.outlook.com \
--to=parav@nvidia.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=xuanzhuo@linux.alibaba.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).