From: Simon Horman <simon.horman@corigine.com>
To: Shunsuke Mie <mie@igel.co.jp>
Cc: "Michael S. Tsirkin" <mst@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Rusty Russell <rusty@rustcorp.com.au>,
kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/1] vringh: IOMEM support
Date: Sat, 3 Jun 2023 16:40:09 +0200 [thread overview]
Message-ID: <ZHtQybyy3qg+xw10@corigine.com> (raw)
In-Reply-To: <20230602055211.309960-2-mie@igel.co.jp>
On Fri, Jun 02, 2023 at 02:52:11PM +0900, Shunsuke Mie wrote:
> Introduce a new memory accessor for vringh. It is able to use vringh to
> virtio rings located on io-memory region.
>
> Signed-off-by: Shunsuke Mie <mie@igel.co.jp>
...
> +/**
> + * vringh_iov_pull_iomem - copy bytes from vring_iov.
Hi Mie-san,
as it looks like there will be a v2,
please consider documenting the vrh parameter here.
> + * @riov: the riov as passed to vringh_getdesc_iomem() (updated as we consume)
> + * @dst: the place to copy.
> + * @len: the maximum length to copy.
> + *
> + * Returns the bytes copied <= len or a negative errno.
> + */
> +ssize_t vringh_iov_pull_iomem(struct vringh *vrh, struct vringh_kiov *riov,
> + void *dst, size_t len)
> +{
> + return vringh_iov_xfer(vrh, riov, dst, len, xfer_from_iomem);
> +}
> +EXPORT_SYMBOL(vringh_iov_pull_iomem);
> +
> +/**
> + * vringh_iov_push_iomem - copy bytes into vring_iov.
And here.
> + * @wiov: the wiov as passed to vringh_getdesc_iomem() (updated as we consume)
> + * @src: the place to copy from.
> + * @len: the maximum length to copy.
> + *
> + * Returns the bytes copied <= len or a negative errno.
> + */
> +ssize_t vringh_iov_push_iomem(struct vringh *vrh, struct vringh_kiov *wiov,
> + const void *src, size_t len)
> +{
> + return vringh_iov_xfer(vrh, wiov, (void *)src, len, xfer_to_iomem);
> +}
> +EXPORT_SYMBOL(vringh_iov_push_iomem);
...
next prev parent reply other threads:[~2023-06-03 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-02 5:52 [PATCH v4 0/1] Introduce a vringh accessor for IO memory Shunsuke Mie
2023-06-02 5:52 ` [PATCH v4 1/1] vringh: IOMEM support Shunsuke Mie
2023-06-02 9:56 ` kernel test robot
2023-06-02 10:59 ` Michael S. Tsirkin
2023-06-05 1:39 ` Shunsuke Mie
2023-06-02 17:19 ` kernel test robot
2023-06-02 18:13 ` kernel test robot
2023-06-03 2:50 ` kernel test robot
2023-06-03 14:40 ` Simon Horman [this message]
2023-06-05 1:51 ` Shunsuke Mie
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=ZHtQybyy3qg+xw10@corigine.com \
--to=simon.horman@corigine.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mie@igel.co.jp \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--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).