From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Jason Wang <jasowang@redhat.com>
Cc: mst@redhat.com, virtualization@lists.linux-foundation.org,
kvm@vger.kernel.org, hang.yuan@intel.com,
piotr.uminski@intel.com
Subject: Re: [PATCH 0/4] ifcvf/vDPA implement features provisioning
Date: Wed, 9 Nov 2022 16:13:32 +0800 [thread overview]
Message-ID: <0b15591f-9e49-6383-65eb-6673423f81ec@intel.com> (raw)
In-Reply-To: <CACGkMEs9af1E1pLd2t8E71YBPF=rHkhfN8qO9_3=x6HVaCMAxg@mail.gmail.com>
On 11/9/2022 2:51 PM, Jason Wang wrote:
> On Mon, Nov 7, 2022 at 5:42 PM Zhu Lingshan <lingshan.zhu@intel.com> wrote:
>> This series implements features provisioning for ifcvf.
>> By applying this series, we allow userspace to create
>> a vDPA device with selected (management device supported)
>> feature bits and mask out others.
> I don't see a direct relationship between the first 3 and the last.
> Maybe you can state the reason why the restructure is a must for the
> feature provisioning. Otherwise, we'd better split the series.
When introducing features provisioning ability to ifcvf, there is a need
to re-create vDPA devices
on a VF with different feature bits.
When remove a vDPA device, the container of struct vdpa_device (here is
ifcvf_adapter) is free-ed in
dev_del() interface, so we need to allocate ifcvf_adapter in dev_add()
than in probe(). That's
why I have re-factored the adapter/mgmt_dev code.
For re-factoring the irq related code and ifcvf_base, let them work on
struct ifcvf_hw, the
reason is that the adapter is allocated in dev_add(), if we want theses
functions to work
before dev_add(), like in probe, we need them work on ifcvf_hw than the
adapter.
Thanks
Zhu Lingshan
>
> Thanks
>
>> Please help review
>>
>> Thanks
>>
>> Zhu Lingshan (4):
>> vDPA/ifcvf: ifcvf base layer interfaces work on struct ifcvf_hw
>> vDPA/ifcvf: IRQ interfaces work on ifcvf_hw
>> vDPA/ifcvf: allocate ifcvf_adapter in dev_add()
>> vDPA/ifcvf: implement features provisioning
>>
>> drivers/vdpa/ifcvf/ifcvf_base.c | 32 ++-----
>> drivers/vdpa/ifcvf/ifcvf_base.h | 10 +-
>> drivers/vdpa/ifcvf/ifcvf_main.c | 156 +++++++++++++++-----------------
>> 3 files changed, 89 insertions(+), 109 deletions(-)
>>
>> --
>> 2.31.1
>>
next prev parent reply other threads:[~2022-11-09 8:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-07 9:33 [PATCH 0/4] ifcvf/vDPA implement features provisioning Zhu Lingshan
2022-11-07 9:33 ` [PATCH 1/4] vDPA/ifcvf: ifcvf base layer interfaces work on struct ifcvf_hw Zhu Lingshan
2022-11-07 9:33 ` [PATCH 2/4] vDPA/ifcvf: IRQ interfaces work on ifcvf_hw Zhu Lingshan
2022-11-07 9:33 ` [PATCH 3/4] vDPA/ifcvf: allocate ifcvf_adapter in dev_add() Zhu Lingshan
2022-11-07 9:33 ` [PATCH 4/4] vDPA/ifcvf: implement features provisioning Zhu Lingshan
2022-11-09 6:51 ` [PATCH 0/4] ifcvf/vDPA " Jason Wang
2022-11-09 8:13 ` Zhu, Lingshan [this message]
2022-11-09 8:59 ` Jason Wang
2022-11-09 9:06 ` Zhu, Lingshan
2022-11-10 3:49 ` Jason Wang
2022-11-10 6:20 ` Zhu, Lingshan
2022-11-10 6:29 ` Jason Wang
2022-11-10 8:58 ` Zhu, Lingshan
2022-11-10 9:13 ` Jason Wang
2022-11-10 9:27 ` 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=0b15591f-9e49-6383-65eb-6673423f81ec@intel.com \
--to=lingshan.zhu@intel.com \
--cc=hang.yuan@intel.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mst@redhat.com \
--cc=piotr.uminski@intel.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