From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Yuxue Liu yuxue.liu@jaguarmicro.com" <yuxue.liu@jaguarmicro.com>
Cc: jasowang@redhat.com, lkp@intel.com, angus.chen@jaguarmicro.com,
linux-kernel@vger.kernel.org, virtualization@lists.linux.dev,
xuanzhuo@linux.alibaba.com, oe-kbuild-all@lists.linux.dev,
llvm@lists.linux.dev
Subject: Re: [PATCH v2] vdpa/vp_vdpa: implement kick_vq_with_data callback
Date: Wed, 8 Jan 2025 07:02:33 -0500 [thread overview]
Message-ID: <20250108070206-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20241203023743.1757-1-yuxue.liu@jaguarmicro.com>
On Tue, Dec 03, 2024 at 10:37:43AM +0800, Yuxue Liu yuxue.liu@jaguarmicro.com wrote:
> From: Yuxue Liu <yuxue.liu@jaguarmicro.com>
>
> Implement the kick_vq_with_data vDPA callback.
> On kick, we pass the next available data to the hardware by writing it in
> the kick offset.
>
> Signed-off-by: Yuxue Liu <yuxue.liu@jaguarmicro.com>
Pls do not send v2 as reply to v1.
I am not sure all tools test the patch if you do.
> ---
> v2: fix build error for kernel test robot
>
> drivers/vdpa/virtio_pci/vp_vdpa.c | 9 +++++++++
> 1 file changed, 9 insertions(+)
>
> diff --git a/drivers/vdpa/virtio_pci/vp_vdpa.c b/drivers/vdpa/virtio_pci/vp_vdpa.c
> index 16380764275e..8787407f75b0 100644
> --- a/drivers/vdpa/virtio_pci/vp_vdpa.c
> +++ b/drivers/vdpa/virtio_pci/vp_vdpa.c
> @@ -367,6 +367,14 @@ static void vp_vdpa_kick_vq(struct vdpa_device *vdpa, u16 qid)
> vp_iowrite16(qid, vp_vdpa->vring[qid].notify);
> }
>
> +static void vp_vdpa_kick_vq_with_data(struct vdpa_device *vdpa, u32 data)
> +{
> + struct vp_vdpa *vp_vdpa = vdpa_to_vp(vdpa);
> + u16 qid = data & 0xFFFF;
> +
> + vp_iowrite32(data, vp_vdpa->vring[qid].notify);
> +}
> +
> static u32 vp_vdpa_get_generation(struct vdpa_device *vdpa)
> {
> struct virtio_pci_modern_device *mdev = vdpa_to_mdev(vdpa);
> @@ -472,6 +480,7 @@ static const struct vdpa_config_ops vp_vdpa_ops = {
> .get_vq_size = vp_vdpa_get_vq_size,
> .set_vq_address = vp_vdpa_set_vq_address,
> .kick_vq = vp_vdpa_kick_vq,
> + .kick_vq_with_data = vp_vdpa_kick_vq_with_data,
> .get_generation = vp_vdpa_get_generation,
> .get_device_id = vp_vdpa_get_device_id,
> .get_vendor_id = vp_vdpa_get_vendor_id,
> --
> 2.34.1
next prev parent reply other threads:[~2025-01-08 12:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-02 3:36 [PATCH] vdpa/vp_vdpa: implement kick_vq_with_data callback Yuxue Liu yuxue.liu@jaguarmicro.com
2024-12-02 4:21 ` Jason Wang
2024-12-03 2:37 ` [PATCH v2] " Yuxue Liu yuxue.liu@jaguarmicro.com
2024-12-04 3:09 ` Jason Wang
2025-01-08 12:02 ` Michael S. Tsirkin [this message]
2024-12-02 12:20 ` [PATCH] " kernel test robot
2024-12-02 12:41 ` kernel test robot
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=20250108070206-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=angus.chen@jaguarmicro.com \
--cc=jasowang@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=llvm@lists.linux.dev \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=virtualization@lists.linux.dev \
--cc=xuanzhuo@linux.alibaba.com \
--cc=yuxue.liu@jaguarmicro.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;
as well as URLs for NNTP newsgroup(s).