mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
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 v3] vringh: IOMEM support
Date: Wed, 26 Apr 2023 21:21:44 +0200	[thread overview]
Message-ID: <ZEl5yKYzsw/g+tQh@corigine.com> (raw)
In-Reply-To: <20230425102250.3847395-1-mie@igel.co.jp>

On Tue, Apr 25, 2023 at 07:22:50PM +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>

...

Hi Mie-san,

thanks for your patch.
One small nit from me below.

> diff --git a/include/linux/vringh.h b/include/linux/vringh.h
> index c3a8117dabe8..c03d045f7f3f 100644
> --- a/include/linux/vringh.h
> +++ b/include/linux/vringh.h
> @@ -330,4 +330,37 @@ int vringh_need_notify_iotlb(struct vringh *vrh);
>  
>  #endif /* CONFIG_VHOST_IOTLB */
>  
> +#if IS_REACHABLE(CONFIG_VHOST_RING_IOMEM)
> +
> +int vringh_init_iomem(struct vringh *vrh, u64 features,
> +		      unsigned int num, bool weak_barriers,
> +		      struct vring_desc *desc,
> +		      struct vring_avail *avail,
> +		      struct vring_used *used);
> +
> +

nit: one blank line is enough.

> +int vringh_getdesc_iomem(struct vringh *vrh,
> +			 struct vringh_kiov *riov,
> +			 struct vringh_kiov *wiov,
> +			 u16 *head,
> +			 gfp_t gfp);

...

  parent reply	other threads:[~2023-04-26 19:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-25 10:22 Shunsuke Mie
2023-04-26  6:10 ` Jason Wang
2023-04-28  2:00   ` Shunsuke Mie
2023-04-26 19:21 ` Simon Horman [this message]
2023-04-28  2:00   ` 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=ZEl5yKYzsw/g+tQh@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

all inboxes | Powered by JetHome®