From: Zhu Lingshan <lingshan.zhu@linux.intel.com>
To: Jason Wang <jasowang@redhat.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
mst@redhat.com, lulu@redhat.com, leonro@nvidia.com
Cc: virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 1/6] vDPA/ifcvf: get_vendor_id returns a device specific vendor id
Date: Thu, 11 Mar 2021 12:21:45 +0800 [thread overview]
Message-ID: <5f2d915f-e1b0-c9eb-9fc8-4b64f5d8cd0f@linux.intel.com> (raw)
In-Reply-To: <ff5fc8f9-f886-bd2a-60cc-771c628c6c4b@redhat.com>
On 3/11/2021 11:23 AM, Jason Wang wrote:
>
> On 2021/3/10 5:00 下午, Zhu Lingshan wrote:
>> In this commit, ifcvf_get_vendor_id() will return
>> a device specific vendor id of the probed pci device
>> than a hard code.
>>
>> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
>> ---
>> drivers/vdpa/ifcvf/ifcvf_main.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/vdpa/ifcvf/ifcvf_main.c
>> b/drivers/vdpa/ifcvf/ifcvf_main.c
>> index fa1af301cf55..e501ee07de17 100644
>> --- a/drivers/vdpa/ifcvf/ifcvf_main.c
>> +++ b/drivers/vdpa/ifcvf/ifcvf_main.c
>> @@ -324,7 +324,10 @@ static u32 ifcvf_vdpa_get_device_id(struct
>> vdpa_device *vdpa_dev)
>> static u32 ifcvf_vdpa_get_vendor_id(struct vdpa_device *vdpa_dev)
>> {
>> - return IFCVF_SUBSYS_VENDOR_ID;
>> + struct ifcvf_adapter *adapter = vdpa_to_adapter(vdpa_dev);
>> + struct pci_dev *pdev = adapter->pdev;
>> +
>> + return pdev->subsystem_vendor;
>> }
>
>
> While at this, I wonder if we can do something similar in
> get_device_id() if it could be simple deduced from some simple math
> from the pci device id?
>
> Thanks
Hi Jason,
IMHO, this implementation is just some memory read ops, I think other
implementations may not save many cpu cycles, an if cost at least three
cpu cycles.
Thanks!
>
>
>> static u32 ifcvf_vdpa_get_vq_align(struct vdpa_device *vdpa_dev)
>
next prev parent reply other threads:[~2021-03-11 4:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-10 9:00 [PATCH V3 0/6] vDPA/ifcvf: enables Intel C5000X-PL virtio-net Zhu Lingshan
2021-03-10 9:00 ` [PATCH V3 1/6] vDPA/ifcvf: get_vendor_id returns a device specific vendor id Zhu Lingshan
2021-03-11 3:23 ` Jason Wang
2021-03-11 4:21 ` Zhu Lingshan [this message]
2021-03-11 6:13 ` Jason Wang
2021-03-11 7:34 ` Zhu, Lingshan
2021-03-10 9:00 ` [PATCH V3 2/6] vDPA/ifcvf: enable Intel C5000X-PL virtio-net for vDPA Zhu Lingshan
2021-03-10 9:00 ` [PATCH V3 3/6] vDPA/ifcvf: rename original IFCVF dev ids to N3000 ids Zhu Lingshan
2021-03-11 3:25 ` Jason Wang
2021-03-11 4:23 ` Zhu Lingshan
2021-03-11 6:14 ` Jason Wang
2021-03-10 9:00 ` [PATCH V3 4/6] vDPA/ifcvf: remove the version number string Zhu Lingshan
2021-03-10 9:16 ` Leon Romanovsky
2021-03-10 9:00 ` [PATCH V3 5/6] vDPA/ifcvf: fetch device feature bits when probe Zhu Lingshan
2021-03-10 9:00 ` [PATCH V3 6/6] vDPA/ifcvf: verify mandatory feature bits for vDPA Zhu Lingshan
2021-03-11 3:20 ` Jason Wang
2021-03-11 4:16 ` Zhu Lingshan
2021-03-11 6:20 ` Jason Wang
2021-03-11 7:19 ` Zhu, Lingshan
2021-03-12 5:52 ` Jason Wang
2021-03-12 6:40 ` Zhu, Lingshan
2021-03-12 7:00 ` Jason Wang
2021-03-12 7:08 ` Zhu, Lingshan
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=5f2d915f-e1b0-c9eb-9fc8-4b64f5d8cd0f@linux.intel.com \
--to=lingshan.zhu@linux.intel.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=leonro@nvidia.com \
--cc=lingshan.zhu@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lulu@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).