virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Feng Liu <feliu@nvidia.com>
Cc: "virtualization@lists.linux-foundation.org"
	<virtualization@lists.linux-foundation.org>,
	"feng.liu.kernel@gmail.com" <feng.liu.kernel@gmail.com>,
	Jiri Pirko <jiri@nvidia.com>, Bodong Wang <bodong@nvidia.com>,
	Gavin Li <gavinl@nvidia.com>
Subject: Re: [PATCH 3/3] virtio_ring: Use const to annotate read-only pointer params
Date: Wed, 8 Mar 2023 09:13:59 -0500	[thread overview]
Message-ID: <20230308091321-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <4e8d1e89-9b32-8dcd-acd1-6957f13fcbb9@nvidia.com>

On Tue, Mar 07, 2023 at 09:17:55PM +0000, Feng Liu wrote:
> On 2023-03-07 04:14, David Edmondson wrote:
> > External email: Use caution opening links or attachments
> > 
> > 
> > Feng Liu via Virtualization <virtualization@lists.linux-foundation.org>
> > writes:
> > 
> >> Add const to make the read-only pointer parameters clear, similar to
> >> many existing functions.
> > 
> > In many of the modified functions the local variable that is a cast of
> > the argument could also be const. Is there a reason not to do both at
> > the same time?
> > 
> 
> Hi,David
> 
> In order to prevent the content of a pointer parameter from being 
> modified and increase the readability of the function, it is recommended 
> to add the 'const' keyword to the parameter. This is not necessary for 
> local variables and non-pointer parameters, as they are only stored on 
> the stack and do not affect the original value or structure member 
> passed into the function. Therefore, in this case, the 'const' keyword 
> is only added to pointer parameters.

This makes no sense to me. If ytou cast away the const then it is
pointless.

> 
> >> Signed-off-by: Feng Liu <feliu@nvidia.com>
> >> Reviewed-by: Jiri Pirko <jiri@nvidia.com>
> >> Reviewed-by: Parav Pandit <parav@nvidia.com>
> >> Reviewed-by: Gavin Li <gavinl@nvidia.com>
> >> Reviewed-by: Bodong Wang <bodong@nvidia.com>
> >> ---
> >>   drivers/virtio/virtio_ring.c | 25 ++++++++++++-------------
> >>   include/linux/virtio.h       | 12 ++++++------
> >>   2 files changed, 18 insertions(+), 19 deletions(-)
> >>
> >> diff --git a/drivers/virtio/virtio_ring.c b/drivers/virtio/virtio_ring.c
> >> index 806cc44eae64..8010fd1d2047 100644
> >> --- a/drivers/virtio/virtio_ring.c
> >> +++ b/drivers/virtio/virtio_ring.c
> >> @@ -233,7 +233,7 @@ static void vring_free(struct virtqueue *_vq);
> >>
> >>   #define to_vvq(_vq) container_of(_vq, struct vring_virtqueue, vq)
> >>
> >> -static bool virtqueue_use_indirect(struct vring_virtqueue *vq,
> >> +static bool virtqueue_use_indirect(const struct vring_virtqueue *vq,
> >>                                          unsigned int total_sg)
> >>   {
> >>        /*
> >> @@ -269,7 +269,7 @@ static bool virtqueue_use_indirect(struct vring_virtqueue *vq,
> >>    * unconditionally on data path.
> >>    */
> >>
> >> -static bool vring_use_dma_api(struct virtio_device *vdev)
> >> +static bool vring_use_dma_api(const struct virtio_device *vdev)
> >>   {
> >>        if (!virtio_has_dma_quirk(vdev))
> >>                return true;
> >> @@ -289,7 +289,7 @@ static bool vring_use_dma_api(struct virtio_device *vdev)
> >>        return false;
> >>   }
> >>
> >> -size_t virtio_max_dma_size(struct virtio_device *vdev)
> >> +size_t virtio_max_dma_size(const struct virtio_device *vdev)
> >>   {
> >>        size_t max_segment_size = SIZE_MAX;
> >>
> >> @@ -423,7 +423,7 @@ static void virtqueue_init(struct vring_virtqueue *vq, u32 num)
> >>    */
> >>
> >>   static void vring_unmap_one_split_indirect(const struct vring_virtqueue *vq,
> >> -                                        struct vring_desc *desc)
> >> +                                        const struct vring_desc *desc)
> >>   {
> >>        u16 flags;
> >>
> >> @@ -1183,7 +1183,7 @@ static u16 packed_last_used(u16 last_used_idx)
> >>   }
> >>
> >>   static void vring_unmap_extra_packed(const struct vring_virtqueue *vq,
> >> -                                  struct vring_desc_extra *extra)
> >> +                                  const struct vring_desc_extra *extra)
> >>   {
> >>        u16 flags;
> >>
> >> @@ -1206,7 +1206,7 @@ static void vring_unmap_extra_packed(const struct vring_virtqueue *vq,
> >>   }
> >>
> >>   static void vring_unmap_desc_packed(const struct vring_virtqueue *vq,
> >> -                                struct vring_packed_desc *desc)
> >> +                                 const struct vring_packed_desc *desc)
> >>   {
> >>        u16 flags;
> >>
> >> @@ -2786,7 +2786,7 @@ EXPORT_SYMBOL_GPL(vring_transport_features);
> >>    * Returns the size of the vring.  This is mainly used for boasting to
> >>    * userspace.  Unlike other operations, this need not be serialized.
> >>    */
> >> -unsigned int virtqueue_get_vring_size(struct virtqueue *_vq)
> >> +unsigned int virtqueue_get_vring_size(const struct virtqueue *_vq)
> >>   {
> >>
> >>        struct vring_virtqueue *vq = to_vvq(_vq);
> >> @@ -2819,7 +2819,7 @@ void __virtqueue_unbreak(struct virtqueue *_vq)
> >>   }
> >>   EXPORT_SYMBOL_GPL(__virtqueue_unbreak);
> >>
> >> -bool virtqueue_is_broken(struct virtqueue *_vq)
> >> +bool virtqueue_is_broken(const struct virtqueue *_vq)
> >>   {
> >>        struct vring_virtqueue *vq = to_vvq(_vq);
> >>
> >> @@ -2827,8 +2827,7 @@ bool virtqueue_is_broken(struct virtqueue *_vq)
> >>   }
> >>   EXPORT_SYMBOL_GPL(virtqueue_is_broken);
> >>
> >> -/*
> >> - * This should prevent the device from being used, allowing drivers to
> >> +/ This should prevent the device from being used, allowing drivers to
> >>    * recover.  You may need to grab appropriate locks to flush.
> >>    */
> >>   void virtio_break_device(struct virtio_device *dev)
> >> @@ -2881,7 +2880,7 @@ dma_addr_t virtqueue_get_desc_addr(struct virtqueue *_vq)
> >>   }
> >>   EXPORT_SYMBOL_GPL(virtqueue_get_desc_addr);
> >>
> >> -dma_addr_t virtqueue_get_avail_addr(struct virtqueue *_vq)
> >> +dma_addr_t virtqueue_get_avail_addr(const struct virtqueue *_vq)
> >>   {
> >>        struct vring_virtqueue *vq = to_vvq(_vq);
> >>
> >> @@ -2895,7 +2894,7 @@ dma_addr_t virtqueue_get_avail_addr(struct virtqueue *_vq)
> >>   }
> >>   EXPORT_SYMBOL_GPL(virtqueue_get_avail_addr);
> >>
> >> -dma_addr_t virtqueue_get_used_addr(struct virtqueue *_vq)
> >> +dma_addr_t virtqueue_get_used_addr(const struct virtqueue *_vq)
> >>   {
> >>        struct vring_virtqueue *vq = to_vvq(_vq);
> >>
> >> @@ -2910,7 +2909,7 @@ dma_addr_t virtqueue_get_used_addr(struct virtqueue *_vq)
> >>   EXPORT_SYMBOL_GPL(virtqueue_get_used_addr);
> >>
> >>   /* Only available for split ring */
> >> -const struct vring *virtqueue_get_vring(struct virtqueue *vq)
> >> +const struct vring *virtqueue_get_vring(const struct virtqueue *vq)
> >>   {
> >>        return &to_vvq(vq)->split.vring;
> >>   }
> >> diff --git a/include/linux/virtio.h b/include/linux/virtio.h
> >> index 2b472514c49b..36a79374e735 100644
> >> --- a/include/linux/virtio.h
> >> +++ b/include/linux/virtio.h
> >> @@ -84,14 +84,14 @@ bool virtqueue_enable_cb_delayed(struct virtqueue *vq);
> >>
> >>   void *virtqueue_detach_unused_buf(struct virtqueue *vq);
> >>
> >> -unsigned int virtqueue_get_vring_size(struct virtqueue *vq);
> >> +unsigned int virtqueue_get_vring_size(const struct virtqueue *vq);
> >>
> >> -bool virtqueue_is_broken(struct virtqueue *vq);
> >> +bool virtqueue_is_broken(const struct virtqueue *vq);
> >>
> >> -const struct vring *virtqueue_get_vring(struct virtqueue *vq);
> >> -dma_addr_t virtqueue_get_desc_addr(struct virtqueue *vq);
> >> -dma_addr_t virtqueue_get_avail_addr(struct virtqueue *vq);
> >> -dma_addr_t virtqueue_get_used_addr(struct virtqueue *vq);
> >> +const struct vring *virtqueue_get_vring(const struct virtqueue *vq);
> >> +dma_addr_t virtqueue_get_desc_addr(const struct virtqueue *vq);
> >> +dma_addr_t virtqueue_get_avail_addr(const struct virtqueue *vq);
> >> +dma_addr_t virtqueue_get_used_addr(const struct virtqueue *vq);
> >>
> >>   int virtqueue_resize(struct virtqueue *vq, u32 num,
> >>                     void (*recycle)(struct virtqueue *vq, void *buf));
> >> --
> >> 2.34.1
> >>
> >> _______________________________________________
> >> Virtualization mailing list
> >> Virtualization@lists.linux-foundation.org
> >> https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.linuxfoundation.org%2Fmailman%2Flistinfo%2Fvirtualization&data=05%7C01%7Cfeliu%40nvidia.com%7C6265cc6ac03e484167ba08db1eec5428%7C43083d15727340c1b7db39efd9ccc17a%7C0%7C0%7C638137772595544505%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=74eHEHUMF89nTG6hrrdMpkl43DJWvC9xCjwqNOny%2FQE%3D&reserved=0
> > --
> > Woke up in my clothes again this morning, don't know exactly where I am.
> 

_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization

  reply	other threads:[~2023-03-08 14:14 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-07  3:57 [PATCH 0/3] virtio_ring: Clean up code for virtio ring and pci Feng Liu via Virtualization
2023-03-07  3:57 ` [PATCH 1/3] virtio_pci_modern: Remove unnecessary num zero check Feng Liu via Virtualization
2023-03-07  9:10   ` David Edmondson
2023-03-08  5:52   ` Jason Wang
2023-03-08  6:57     ` Michael S. Tsirkin
2023-03-08 14:23   ` Michael S. Tsirkin
2023-03-08 14:33     ` Feng Liu via Virtualization
2023-03-07  3:57 ` [PATCH 2/3] virtio_ring: Avoid using inline for small functions Feng Liu via Virtualization
2023-03-07  9:11   ` David Edmondson
2023-03-08  5:55   ` Jason Wang
2023-03-07  3:57 ` [PATCH 3/3] virtio_ring: Use const to annotate read-only pointer params Feng Liu via Virtualization
2023-03-07  9:14   ` David Edmondson
2023-03-07 21:17     ` Feng Liu via Virtualization
2023-03-08 14:13       ` Michael S. Tsirkin [this message]
2023-03-08 15:59         ` Feng Liu via Virtualization
2023-03-08 16:25           ` Michael S. Tsirkin
2023-03-08 16:44             ` Feng Liu via Virtualization
2023-03-08 16:49             ` Michael S. Tsirkin
2023-03-08 17:26               ` Feng Liu via Virtualization
2023-03-08  5:58   ` Jason Wang
2023-03-08 14:07     ` Feng Liu via Virtualization
2023-03-08 14:13       ` Feng Liu via Virtualization
2023-03-08 14:16       ` Michael S. Tsirkin
2023-03-08 14:19         ` Feng Liu via Virtualization
2023-03-08 14:28           ` Michael S. Tsirkin
2023-03-08 14:40             ` Feng Liu via Virtualization
2023-03-08 14:47               ` Michael S. Tsirkin
2023-03-08 15:47                 ` Feng Liu via Virtualization
     [not found]             ` <ZAmlwyVfz+IK1b6T@nanopsycho>
2023-03-09 14:27               ` Michael S. Tsirkin
2023-03-08  6:59   ` Michael S. Tsirkin

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=20230308091321-mutt-send-email-mst@kernel.org \
    --to=mst@redhat.com \
    --cc=bodong@nvidia.com \
    --cc=feliu@nvidia.com \
    --cc=feng.liu.kernel@gmail.com \
    --cc=gavinl@nvidia.com \
    --cc=jiri@nvidia.com \
    --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).