Linux-remoteproc Archive on lore.kernel.org
 help / color / Atom feed
From: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Mathieu Poirier <mathieu.poirier@linaro.org>,
	linux-remoteproc@vger.kernel.org,
	Ohad Ben-Cohen <ohad@wizery.com>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	Liam Girdwood <liam.r.girdwood@linux.intel.com>
Subject: Re: [PATCH v2] rpmsg: virtio: add endianness conversions
Date: Mon, 6 Jul 2020 14:47:17 +0200
Message-ID: <20200706124716.GA5457@ubuntu> (raw)
In-Reply-To: <20200701055912-mutt-send-email-mst@kernel.org>

On Wed, Jul 01, 2020 at 06:00:30AM -0400, Michael S. Tsirkin wrote:
> On Tue, Jun 30, 2020 at 11:50:57AM -0600, Mathieu Poirier wrote:
> > On Tue, Jun 16, 2020 at 09:30:11AM +0200, Guennadi Liakhovetski wrote:
> > > According to the VirtIO 1.0 spec data, sent over virtual queues must
> > > be in little-endian format. Update the RPMsg VirtIO implementation
> > > to enforce that but let legacy configurations continue use native
> > > endianness.
> > > 
> > > Signed-off-by: Guennadi Liakhovetski <guennadi.liakhovetski@linux.intel.com>
> > > ---
> > > 
> > > v2: Following suggestions from Michael and Mathieu switch to using virtio16/32 
> > > types and conversion functions.
> > > 
> > >  drivers/rpmsg/virtio_rpmsg_bus.c | 63 ++++++++++++++++++++++------------------
> > >  1 file changed, 35 insertions(+), 28 deletions(-)
> > > 
> > > diff --git a/drivers/rpmsg/virtio_rpmsg_bus.c b/drivers/rpmsg/virtio_rpmsg_bus.c
> > > index 07d4f33..41025df 100644
> > > --- a/drivers/rpmsg/virtio_rpmsg_bus.c
> > > +++ b/drivers/rpmsg/virtio_rpmsg_bus.c
> > > @@ -11,6 +11,8 @@
> > >  
> > >  #define pr_fmt(fmt) "%s: " fmt, __func__
> > >  
> > > +#include <asm/byteorder.h>
> > > +
> > 
> > Not sure about this header - what does it provide?

It was needed for the original cpu_to_le... and friends version of the patch.

> > 
> > >  #include <linux/dma-mapping.h>
> > >  #include <linux/idr.h>
> > >  #include <linux/jiffies.h>
> > > @@ -22,6 +24,7 @@
> > >  #include <linux/scatterlist.h>
> > >  #include <linux/slab.h>
> > >  #include <linux/sched.h>
> > > +#include <linux/types.h>
> > 
> > This too... It should be fine with linux/virtio_config.h below since it 
> > already includes linux/virtio_byteorder.h
> 
> It's probably best to include linux/virtio_byteorder.h explicitly.

Yep, will do.

> > Moreover, please send another revision that applies on rproc-next.  The third
> > hunk in this patch doesn't apply.
> > 
> > With the above:
> > 
> > Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> > 
> > >  #include <linux/virtio.h>
> > >  #include <linux/virtio_ids.h>
> > >  #include <linux/virtio_config.h>

[snip]

> > > @@ -846,15 +853,15 @@ static int rpmsg_ns_cb(struct rpmsg_device *rpdev, void *data, int len,
> > >  	/* don't trust the remote processor for null terminating the name */
> > >  	msg->name[RPMSG_NAME_SIZE - 1] = '\0';
> > >  
> > > -	dev_info(dev, "%sing channel %s addr 0x%x\n",
> > > -		 msg->flags & RPMSG_NS_DESTROY ? "destroy" : "creat",
> > > -		 msg->name, msg->addr);
> > > -
> > >  	strncpy(chinfo.name, msg->name, sizeof(chinfo.name));
> > >  	chinfo.src = RPMSG_ADDR_ANY;
> > > -	chinfo.dst = msg->addr;
> > > +	chinfo.dst = virtio32_to_cpu(vrp->vdev, msg->addr);
> > > +
> > > +	dev_info(dev, "%sing channel %s addr 0x%x\n",
> 
> 
> Let's not try tricks. Just %s and destroying/creating below.
> Wastes 3 bytes of kernel space but is clearer.

Those aren't my tricks - they're already there, but sure, I can replace that while at it.

Thanks
Guennadi

> 
> > > +		 virtio32_to_cpu(vrp->vdev, msg->flags) & RPMSG_NS_DESTROY ?
> > > +		 "destroy" : "creat", msg->name, chinfo.dst);
> > >  
> > > -	if (msg->flags & RPMSG_NS_DESTROY) {
> > > +	if (virtio32_to_cpu(vrp->vdev, msg->flags) & RPMSG_NS_DESTROY) {
> > >  		ret = rpmsg_unregister_device(&vrp->vdev->dev, &chinfo);
> > >  		if (ret)
> > >  			dev_err(dev, "rpmsg_destroy_channel failed: %d\n", ret);
> > > -- 
> > > 1.9.3
> > > 
> 

  reply index

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 12:39 [PATCH] " Guennadi Liakhovetski
2020-06-08 13:13 ` Michael S. Tsirkin
2020-06-15 20:47 ` Mathieu Poirier
2020-06-16  6:14   ` Guennadi Liakhovetski
2020-06-16  7:30     ` [PATCH v2] " Guennadi Liakhovetski
2020-06-30 17:50       ` Mathieu Poirier
2020-07-01 10:00         ` Michael S. Tsirkin
2020-07-06 12:47           ` Guennadi Liakhovetski [this message]
2020-07-06 12:56             ` Guennadi Liakhovetski
2020-07-06 13:38               ` [PATCH v3] " Guennadi Liakhovetski
2020-07-07 15:11                 ` Arnaud POULIQUEN
2020-07-07 15:34                   ` [PATCH v4] " Guennadi Liakhovetski
2020-07-07 15:38                     ` Mathieu Poirier
2020-07-10  6:20                       ` Guennadi Liakhovetski
2020-07-21  8:56                       ` [PATCH RESEND " Guennadi Liakhovetski
2020-07-21 10:04                         ` Michael S. Tsirkin
2020-07-22  3:39                         ` Bjorn Andersson
2020-07-22  4:00                         ` patchwork-bot+linux-remoteproc
2020-07-27 16:07                         ` Michael S. Tsirkin
2020-07-27 16:09                           ` Mathieu Poirier
2020-07-28  9:51                             ` 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=20200706124716.GA5457@ubuntu \
    --to=guennadi.liakhovetski@linux.intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=liam.r.girdwood@linux.intel.com \
    --cc=linux-remoteproc@vger.kernel.org \
    --cc=mathieu.poirier@linaro.org \
    --cc=mst@redhat.com \
    --cc=ohad@wizery.com \
    --cc=pierre-louis.bossart@linux.intel.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

Linux-remoteproc Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-remoteproc/0 linux-remoteproc/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-remoteproc linux-remoteproc/ https://lore.kernel.org/linux-remoteproc \
		linux-remoteproc@vger.kernel.org
	public-inbox-index linux-remoteproc

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-remoteproc


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git