From: Jason Wang <jasowang@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>, mst@redhat.com
Cc: netdev@vger.kernel.org, virtualization@lists.linux-foundation.org
Subject: Re: [PATCH V4 1/4] vDPA/ifcvf: implement IO read/write helpers in the header file
Date: Mon, 14 Feb 2022 14:15:58 +0800 [thread overview]
Message-ID: <5b9e287a-08bd-10b9-4159-5b36f192a387@redhat.com> (raw)
In-Reply-To: <20220203072735.189716-2-lingshan.zhu@intel.com>
在 2022/2/3 下午3:27, Zhu Lingshan 写道:
> re-implement IO read/write helpers in the header file, so that
> they can be utilized among modules.
>
> Signed-off-by: Zhu Lingshan <lingshan.zhu@intel.com>
I wonder if we can simply use include/linux/virtio_pci_modern.h.
The accessors vp_ioreadX/writeX() there were decoupled from the
virtio_pci_modern_device structure.
Thanks
> ---
> drivers/vdpa/ifcvf/ifcvf_base.c | 36 --------------------------------
> drivers/vdpa/ifcvf/ifcvf_base.h | 37 +++++++++++++++++++++++++++++++++
> 2 files changed, 37 insertions(+), 36 deletions(-)
>
> diff --git a/drivers/vdpa/ifcvf/ifcvf_base.c b/drivers/vdpa/ifcvf/ifcvf_base.c
> index 7d41dfe48ade..397692ae671c 100644
> --- a/drivers/vdpa/ifcvf/ifcvf_base.c
> +++ b/drivers/vdpa/ifcvf/ifcvf_base.c
> @@ -10,42 +10,6 @@
>
> #include "ifcvf_base.h"
>
> -static inline u8 ifc_ioread8(u8 __iomem *addr)
> -{
> - return ioread8(addr);
> -}
> -static inline u16 ifc_ioread16 (__le16 __iomem *addr)
> -{
> - return ioread16(addr);
> -}
> -
> -static inline u32 ifc_ioread32(__le32 __iomem *addr)
> -{
> - return ioread32(addr);
> -}
> -
> -static inline void ifc_iowrite8(u8 value, u8 __iomem *addr)
> -{
> - iowrite8(value, addr);
> -}
> -
> -static inline void ifc_iowrite16(u16 value, __le16 __iomem *addr)
> -{
> - iowrite16(value, addr);
> -}
> -
> -static inline void ifc_iowrite32(u32 value, __le32 __iomem *addr)
> -{
> - iowrite32(value, addr);
> -}
> -
> -static void ifc_iowrite64_twopart(u64 val,
> - __le32 __iomem *lo, __le32 __iomem *hi)
> -{
> - ifc_iowrite32((u32)val, lo);
> - ifc_iowrite32(val >> 32, hi);
> -}
> -
> struct ifcvf_adapter *vf_to_adapter(struct ifcvf_hw *hw)
> {
> return container_of(hw, struct ifcvf_adapter, vf);
> diff --git a/drivers/vdpa/ifcvf/ifcvf_base.h b/drivers/vdpa/ifcvf/ifcvf_base.h
> index c486873f370a..949b4fb9d554 100644
> --- a/drivers/vdpa/ifcvf/ifcvf_base.h
> +++ b/drivers/vdpa/ifcvf/ifcvf_base.h
> @@ -42,6 +42,43 @@
> #define ifcvf_private_to_vf(adapter) \
> (&((struct ifcvf_adapter *)adapter)->vf)
>
> +static inline u8 ifc_ioread8(u8 __iomem *addr)
> +{
> + return ioread8(addr);
> +}
> +
> +static inline u16 ifc_ioread16(__le16 __iomem *addr)
> +{
> + return ioread16(addr);
> +}
> +
> +static inline u32 ifc_ioread32(__le32 __iomem *addr)
> +{
> + return ioread32(addr);
> +}
> +
> +static inline void ifc_iowrite8(u8 value, u8 __iomem *addr)
> +{
> + iowrite8(value, addr);
> +}
> +
> +static inline void ifc_iowrite16(u16 value, __le16 __iomem *addr)
> +{
> + iowrite16(value, addr);
> +}
> +
> +static inline void ifc_iowrite32(u32 value, __le32 __iomem *addr)
> +{
> + iowrite32(value, addr);
> +}
> +
> +static inline void ifc_iowrite64_twopart(u64 val,
> + __le32 __iomem *lo, __le32 __iomem *hi)
> +{
> + ifc_iowrite32((u32)val, lo);
> + ifc_iowrite32(val >> 32, hi);
> +}
> +
> struct vring_info {
> u64 desc;
> u64 avail;
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next parent reply other threads:[~2022-02-14 6:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20220203072735.189716-1-lingshan.zhu@intel.com>
[not found] ` <20220203072735.189716-2-lingshan.zhu@intel.com>
2022-02-14 6:15 ` Jason Wang [this message]
[not found] ` <20220203072735.189716-3-lingshan.zhu@intel.com>
2022-02-14 6:26 ` [PATCH V4 2/4] vDPA/ifcvf: implement device MSIX vector allocator Jason Wang
[not found] ` <20220203072735.189716-4-lingshan.zhu@intel.com>
2022-02-14 6:28 ` [PATCH V4 3/4] vhost_vdpa: don't setup irq offloading when irq_num < 0 Jason Wang
[not found] ` <20220203072735.189716-5-lingshan.zhu@intel.com>
2022-02-14 7:19 ` [PATCH V4 4/4] vDPA/ifcvf: implement shared IRQ feature Jason Wang
2022-02-14 10:01 ` Zhu Lingshan
2022-02-14 14:27 ` Michael S. Tsirkin
[not found] ` <4920887f-0521-9054-035d-32114301ba3a@intel.com>
2022-02-15 3:03 ` Jason Wang
[not found] ` <70ee26d4-9553-543a-ccd9-684f468e2704@intel.com>
2022-02-15 3:36 ` Jason Wang
2022-02-14 14:25 ` Michael S. Tsirkin
2022-02-15 3:34 ` Jason Wang
2022-02-15 14:29 ` 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=5b9e287a-08bd-10b9-4159-5b36f192a387@redhat.com \
--to=jasowang@redhat.com \
--cc=lingshan.zhu@intel.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).