public inbox for virtualization@lists.linux-foundation.org
 help / color / mirror / Atom feed
From: Yui Washizu <yui.washidu@gmail.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, xuanzhuo@linux.alibaba.com, eperezma@redhat.com,
	virtualization@lists.linux.dev
Subject: Re: [PATCH] virtio: add num_vf callback to virtio_bus
Date: Mon, 9 Mar 2026 15:19:39 +0900	[thread overview]
Message-ID: <d6161d2e-066e-4d85-bc5a-0129a5f116b8@gmail.com> (raw)
In-Reply-To: <CACGkMEu+fd91yCwmSPNj0fTXw5v3ZON7F4kL_PVUz6TbG-iT4g@mail.gmail.com>


On 3/9/2026 12:33 PM, Jason Wang wrote:
> On Mon, Mar 9, 2026 at 10:37 AM Yui Washizu <yui.washidu@gmail.com> wrote:
>> Recent QEMU versions added support for virtio SR-IOV emulation,
>> allowing virtio devices to expose SR-IOV VFs to the guest.
>> However, virtio_bus does not implement the num_vf callback of bus_type,
>> causing dev_num_vf() to return 0 for virtio devices even when
>> SR-IOV VFs are active.
>>
>> net/core/rtnetlink.c calls dev_num_vf(dev->dev.parent) to populate
>> IFLA_NUM_VF and IFLA_VFINFO_LIST
> Patch looks good but,
>
> If I understand correctly, ndo_get_vf_config is needed for
> IFLA_VFINFO_LIST but not implemeted in this patch?

Thank you for your comment.

I submitted this patch because I confirmed
that "ip link show" returns the correct VF IDs with this implementation.

In the current implementation,
I believe there is no information that would need to be referenced 
through IFLA_VFINFO_LIST.
Therefore, I did not include ndo_get_vf_config in this patch,
as it did not seem essential at this stage.

Would it be better to implement IFLA_VFINFO_LIST support together with this?

Regards,


>> in RTM_GETLINK responses.  For a
>> virtio-net device, dev.parent points to the virtio_device, whose bus
>> is virtio_bus.  Without num_vf, SR-IOV VF information is silently
>> omitted from tools that rely on rtnetlink, such as 'ip link show'.
>>
>> Add a num_vf callback that delegates to dev_num_vf(dev->parent),
>> which in turn reaches the underlying transport (pci_bus_type for
>> virtio-pci) where the actual VF count is tracked.  Non-PCI transports
>> are unaffected as dev_num_vf() returns 0 when no num_vf callback is
>> present.
>>
>> Signed-off-by: Yui Washizu <yui.washidu@gmail.com>
>> ---
>>   drivers/virtio/virtio.c | 9 +++++++++
>>   1 file changed, 9 insertions(+)
>>
>> diff --git a/drivers/virtio/virtio.c b/drivers/virtio/virtio.c
>> index 5bdc6b82b30b..299fa83be1d5 100644
>> --- a/drivers/virtio/virtio.c
>> +++ b/drivers/virtio/virtio.c
>> @@ -435,6 +435,14 @@ static void virtio_dev_shutdown(struct device *_d)
>>          dev->config->reset(dev);
>>   }
>>
>> +static int virtio_dev_num_vf(struct device *dev)
>> +{
>> +       struct virtio_device *vdev = dev_to_virtio(dev);
>> +
>> +       return dev_num_vf(vdev->dev.parent);
>> +}
>> +
>> +
>>   static const struct bus_type virtio_bus = {
>>          .name  = "virtio",
>>          .match = virtio_dev_match,
>> @@ -444,6 +452,7 @@ static const struct bus_type virtio_bus = {
>>          .remove = virtio_dev_remove,
>>          .irq_get_affinity = virtio_irq_get_affinity,
>>          .shutdown = virtio_dev_shutdown,
>> +       .num_vf = virtio_dev_num_vf,
>>   };
>>
>>   int __register_virtio_driver(struct virtio_driver *driver, struct module *owner)
>> --
>> 2.47.3
>>
> Thanks
>

  reply	other threads:[~2026-03-09  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-09  2:33 [PATCH] virtio: add num_vf callback to virtio_bus Yui Washizu
2026-03-09  3:33 ` Jason Wang
2026-03-09  6:19   ` Yui Washizu [this message]
2026-03-10  3:02     ` Jason Wang
2026-03-10  5:34       ` Washizu Yui

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=d6161d2e-066e-4d85-bc5a-0129a5f116b8@gmail.com \
    --to=yui.washidu@gmail.com \
    --cc=eperezma@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=mst@redhat.com \
    --cc=virtualization@lists.linux.dev \
    --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