From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Stefano Garzarella <sgarzare@redhat.com>
Cc: jasowang@redhat.com, mst@redhat.com, virtualization@lists.linux.dev
Subject: Re: [PATCH 02/10] vDPA: report virtio-block max segment size to user space
Date: Fri, 29 Mar 2024 22:48:25 +0800 [thread overview]
Message-ID: <bfd9be81-d84d-424f-bed0-2e2cfe945bf4@intel.com> (raw)
In-Reply-To: <etmgf3zcsnuz5hoj26g2nr7qunc7dxqg5p5hb43oe2mefkgyk5@4dofowgn4vcy>
On 3/20/2024 12:04 AM, Stefano Garzarella wrote:
> On Mon, Feb 19, 2024 at 02:55:58AM +0800, Zhu Lingshan wrote:
>> This commit allows reporting the max size of any
>> single segment of virtio-block devices to user space.
>>
>> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
>> ---
>> drivers/vdpa/vdpa.c | 17 +++++++++++++++++
>> include/uapi/linux/vdpa.h | 1 +
>> 2 files changed, 18 insertions(+)
>>
>> diff --git a/drivers/vdpa/vdpa.c b/drivers/vdpa/vdpa.c
>> index d5ccb618de2b..ee1472d32b0d 100644
>> --- a/drivers/vdpa/vdpa.c
>> +++ b/drivers/vdpa/vdpa.c
>> @@ -956,6 +956,20 @@ vdpa_dev_blk_capacity_config_fill(struct sk_buff
>> *msg,
>> val_u64, VDPA_ATTR_PAD);
>> }
>>
>> +static int
>> +vdpa_dev_blk_seg_size_config_fill(struct sk_buff *msg, u64 features,
>> + const struct virtio_blk_config *config)
>> +{
>> + u32 val_u32;
>> +
>> + if ((features & BIT_ULL(VIRTIO_BLK_F_SIZE_MAX)) == 0)
>> + return 0;
>> +
>> + val_u32 = __virtio32_to_cpu(true, config->size_max);
>> +
>> + return nla_put_u32(msg, VDPA_ATTR_DEV_BLK_CFG_SEG_SIZE, val_u32);
>
> Should we call this VDPA_ATTR_DEV_BLK_CFG_SIZE_MAX ?
I have tried this before, but this macro is too long causing a odd
format in the header file.
I can change this since you point this out. This is uapi means we should
merge the
fix during the RC release before 6.9 official.
@MST, does the process work for you?
>
>> +}
>> +
>> static int vdpa_dev_blk_config_fill(struct vdpa_device *vdev,
>> struct sk_buff *msg)
>> {
>> @@ -973,6 +987,9 @@ static int vdpa_dev_blk_config_fill(struct
>> vdpa_device *vdev,
>> if (vdpa_dev_blk_capacity_config_fill(msg, &config))
>> return -EMSGSIZE;
>>
>> + if (vdpa_dev_blk_seg_size_config_fill(msg, features_device,
>> &config))
>> + return -EMSGSIZE;
>> +
>> return 0;
>> }
>>
>> diff --git a/include/uapi/linux/vdpa.h b/include/uapi/linux/vdpa.h
>> index 1bf69226cb96..586bce3c906a 100644
>> --- a/include/uapi/linux/vdpa.h
>> +++ b/include/uapi/linux/vdpa.h
>> @@ -57,6 +57,7 @@ enum vdpa_attr {
>> VDPA_ATTR_DEV_FEATURES, /* u64 */
>>
>> VDPA_ATTR_DEV_BLK_CFG_CAPACITY, /* u64 */
>> + VDPA_ATTR_DEV_BLK_CFG_SEG_SIZE, /* u32 */
>>
>> /* new attributes must be added above here */
>> VDPA_ATTR_MAX,
>> --
>> 2.39.3
>>
>>
>
>
next prev parent reply other threads:[~2024-03-29 14:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-18 18:55 [PATCH 00/10] vDPA: allow userspace query virito-block device Zhu Lingshan
2024-02-18 18:55 ` [PATCH 01/10] vDPA: report virtio-block capacity to user space Zhu Lingshan
2024-03-19 16:43 ` Stefano Garzarella
2024-02-18 18:55 ` [PATCH 02/10] vDPA: report virtio-block max segment size " Zhu Lingshan
2024-03-19 16:04 ` Stefano Garzarella
2024-03-29 14:48 ` Zhu, Lingshan [this message]
2024-03-31 20:03 ` Michael S. Tsirkin
2024-02-18 18:55 ` [PATCH 03/10] vDPA: report virtio-block block-size " Zhu Lingshan
2024-03-19 16:43 ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 04/10] vDPA: report virtio-block max segments in a request " Zhu Lingshan
2024-03-19 16:43 ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 05/10] vDPA: report virtio-block MQ info " Zhu Lingshan
2024-03-19 16:44 ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 06/10] vDPA: report virtio-block topology " Zhu Lingshan
2024-03-19 16:44 ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 07/10] vDPA: report virtio-block discarding configuration " Zhu Lingshan
2024-03-19 16:44 ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 08/10] vDPA: report virtio-block write zeroes " Zhu Lingshan
2024-03-19 16:36 ` Stefano Garzarella
2024-03-19 17:02 ` Michael S. Tsirkin
2024-03-19 17:08 ` Stefano Garzarella
2024-03-19 17:57 ` Michael S. Tsirkin
2024-02-18 18:56 ` [PATCH 09/10] vDPA: report virtio-block read-only info " Zhu Lingshan
2024-03-19 16:40 ` Stefano Garzarella
2024-04-09 8:37 ` Zhu, Lingshan
2024-05-03 12:18 ` Stefano Garzarella
2024-02-18 18:56 ` [PATCH 10/10] vDPA: report virtio-blk flush " Zhu Lingshan
2024-03-19 16:42 ` Stefano Garzarella
2024-03-19 6:39 ` [PATCH 00/10] vDPA: allow userspace query virito-block device Michael S. Tsirkin
2024-03-20 3:30 ` Jason Wang
2024-03-20 7:00 ` Michael S. Tsirkin
2024-03-19 16:49 ` Stefano Garzarella
2024-03-20 10:31 ` Zhu, Lingshan
2024-03-20 10:53 ` Stefano Garzarella
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=bfd9be81-d84d-424f-bed0-2e2cfe945bf4@intel.com \
--to=lingshan.zhu@intel.com \
--cc=jasowang@redhat.com \
--cc=mst@redhat.com \
--cc=sgarzare@redhat.com \
--cc=virtualization@lists.linux.dev \
/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).