From: Jie Deng <jie.deng@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: linux-i2c@vger.kernel.org,
virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, mst@redhat.com, wsa@kernel.org,
jasowang@redhat.com, wsa+renesas@sang-engineering.com,
andriy.shevchenko@linux.intel.com, conghui.chen@intel.com,
arnd@arndb.de, kblaiech@mellanox.com,
jarkko.nikula@linux.intel.com, Sergey.Semin@baikalelectronics.ru,
rppt@kernel.org, loic.poulain@linaro.org, tali.perry1@gmail.com,
u.kleine-koenig@pengutronix.de, bjorn.andersson@linaro.org,
yu1.wang@intel.com, shuo.a.liu@intel.com, stefanha@redhat.com,
pbonzini@redhat.com
Subject: Re: [PATCH v9] i2c: virtio: add a virtio i2c frontend driver
Date: Mon, 22 Mar 2021 15:53:36 +0800 [thread overview]
Message-ID: <dbb5dfe9-8ee6-e3f8-3681-d0ec83282930@intel.com> (raw)
In-Reply-To: <20210322064144.y6kpajolwh2kd3lj@vireshk-i7>
On 2021/3/22 14:41, Viresh Kumar wrote:
>
>> +/**
>> + * struct virtio_i2c - virtio I2C data
>> + * @vdev: virtio device for this controller
>> + * @completion: completion of virtio I2C message
>> + * @adap: I2C adapter for this controller
>> + * @i2c_lock: lock for virtqueue processing
> Name mismatch here.
Will fix this typo. Thank you.
>> + * @vq: the virtio virtqueue for communication
>> + */
>> +struct virtio_i2c {
>> + struct virtio_device *vdev;
>> + struct completion completion;
>> + struct i2c_adapter adap;
>> + struct mutex lock;
>> + struct virtqueue *vq;
>> +};
>
>> +static int virtio_i2c_complete_reqs(struct virtqueue *vq,
>> + struct virtio_i2c_req *reqs,
>> + struct i2c_msg *msgs, int nr,
>> + bool timeout)
>> +{
>> + struct virtio_i2c_req *req;
>> + bool err_found = false;
>> + unsigned int len;
>> + int i, j = 0;
>> +
>> + for (i = 0; i < nr; i++) {
>> + /* Detach the ith request from the vq */
>> + req = virtqueue_get_buf(vq, &len);
>> +
>> + if (timeout || err_found) {
>> + i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], false);
>> + continue;
>> + }
>> +
>> + /*
>> + * Condition (req && req == &reqs[i]) should always meet since
>> + * we have total nr requests in the vq.
>> + */
>> + if (WARN_ON(!(req && req == &reqs[i])) ||
>> + (req->in_hdr.status != VIRTIO_I2C_MSG_OK)) {
>> + err_found = true;
>> + i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], false);
>> + continue;
>> + }
>> +
>> + i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], true);
>> + ++j;
>> + }
> I think you can simplify the code like this here:
I think your optimization has problems...
> bool err_found = timeout;
>
> for (i = 0; i < nr; i++) {
> /* Detach the ith request from the vq */
> req = virtqueue_get_buf(vq, &len);
>
> /*
> * Condition (req && req == &reqs[i]) should always meet since
> * we have total nr requests in the vq.
> */
> if (!err_found &&
> (WARN_ON(!(req && req == &reqs[i])) ||
> (req->in_hdr.status != VIRTIO_I2C_MSG_OK))) {
> err_found = true;
> continue;
Just continue here, the ith buf leaks ?
> }
>
> i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], err_found);
i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], !err_found); ?
> if (!err_found)
> ++j;
>
>> +
>> + return (timeout ? -ETIMEDOUT : j);
>> +}
>> +
>> +static int virtio_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num)
>> +{
>> + struct virtio_i2c *vi = i2c_get_adapdata(adap);
>> + struct virtqueue *vq = vi->vq;
>> + struct virtio_i2c_req *reqs;
>> + unsigned long time_left;
>> + int ret, nr;
>> +
>> + reqs = kcalloc(num, sizeof(*reqs), GFP_KERNEL);
>> + if (!reqs)
>> + return -ENOMEM;
>> +
>> + mutex_lock(&vi->lock);
>> +
>> + ret = virtio_i2c_send_reqs(vq, reqs, msgs, num);
>> + if (ret == 0)
>> + goto err_unlock_free;
>> +
>> + nr = ret;
>> + reinit_completion(&vi->completion);
>> + virtqueue_kick(vq);
>> +
>> + time_left = wait_for_completion_timeout(&vi->completion, adap->timeout);
>> + if (!time_left) {
>> + dev_err(&adap->dev, "virtio i2c backend timeout.\n");
>> + ret = virtio_i2c_complete_reqs(vq, reqs, msgs, nr, true);
>> + goto err_unlock_free;
>> + }
>> +
>> + ret = virtio_i2c_complete_reqs(vq, reqs, msgs, nr, false);
> And this can be optimized as well:
>
> time_left = wait_for_completion_timeout(&vi->completion, adap->timeout);
> if (!time_left)
> dev_err(&adap->dev, "virtio i2c backend timeout.\n");
>
> ret = virtio_i2c_complete_reqs(vq, reqs, msgs, nr, !time_left);
Good optimization here.
WARNING: multiple messages have this Message-ID (diff)
From: Jie Deng <jie.deng@intel.com>
To: Viresh Kumar <viresh.kumar@linaro.org>
Cc: mst@redhat.com, bjorn.andersson@linaro.org,
wsa+renesas@sang-engineering.com, linux-i2c@vger.kernel.org,
wsa@kernel.org, andriy.shevchenko@linux.intel.com,
yu1.wang@intel.com, u.kleine-koenig@pengutronix.de,
kblaiech@mellanox.com, virtualization@lists.linux-foundation.org,
arnd@arndb.de, stefanha@redhat.com, tali.perry1@gmail.com,
conghui.chen@intel.com, loic.poulain@linaro.org,
linux-kernel@vger.kernel.org, Sergey.Semin@baikalelectronics.ru,
jarkko.nikula@linux.intel.com, shuo.a.liu@intel.com,
pbonzini@redhat.com, rppt@kernel.org
Subject: Re: [PATCH v9] i2c: virtio: add a virtio i2c frontend driver
Date: Mon, 22 Mar 2021 15:53:36 +0800 [thread overview]
Message-ID: <dbb5dfe9-8ee6-e3f8-3681-d0ec83282930@intel.com> (raw)
In-Reply-To: <20210322064144.y6kpajolwh2kd3lj@vireshk-i7>
On 2021/3/22 14:41, Viresh Kumar wrote:
>
>> +/**
>> + * struct virtio_i2c - virtio I2C data
>> + * @vdev: virtio device for this controller
>> + * @completion: completion of virtio I2C message
>> + * @adap: I2C adapter for this controller
>> + * @i2c_lock: lock for virtqueue processing
> Name mismatch here.
Will fix this typo. Thank you.
>> + * @vq: the virtio virtqueue for communication
>> + */
>> +struct virtio_i2c {
>> + struct virtio_device *vdev;
>> + struct completion completion;
>> + struct i2c_adapter adap;
>> + struct mutex lock;
>> + struct virtqueue *vq;
>> +};
>
>> +static int virtio_i2c_complete_reqs(struct virtqueue *vq,
>> + struct virtio_i2c_req *reqs,
>> + struct i2c_msg *msgs, int nr,
>> + bool timeout)
>> +{
>> + struct virtio_i2c_req *req;
>> + bool err_found = false;
>> + unsigned int len;
>> + int i, j = 0;
>> +
>> + for (i = 0; i < nr; i++) {
>> + /* Detach the ith request from the vq */
>> + req = virtqueue_get_buf(vq, &len);
>> +
>> + if (timeout || err_found) {
>> + i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], false);
>> + continue;
>> + }
>> +
>> + /*
>> + * Condition (req && req == &reqs[i]) should always meet since
>> + * we have total nr requests in the vq.
>> + */
>> + if (WARN_ON(!(req && req == &reqs[i])) ||
>> + (req->in_hdr.status != VIRTIO_I2C_MSG_OK)) {
>> + err_found = true;
>> + i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], false);
>> + continue;
>> + }
>> +
>> + i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], true);
>> + ++j;
>> + }
> I think you can simplify the code like this here:
I think your optimization has problems...
> bool err_found = timeout;
>
> for (i = 0; i < nr; i++) {
> /* Detach the ith request from the vq */
> req = virtqueue_get_buf(vq, &len);
>
> /*
> * Condition (req && req == &reqs[i]) should always meet since
> * we have total nr requests in the vq.
> */
> if (!err_found &&
> (WARN_ON(!(req && req == &reqs[i])) ||
> (req->in_hdr.status != VIRTIO_I2C_MSG_OK))) {
> err_found = true;
> continue;
Just continue here, the ith buf leaks ?
> }
>
> i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], err_found);
i2c_put_dma_safe_msg_buf(reqs[i].buf, &msgs[i], !err_found); ?
> if (!err_found)
> ++j;
>
>> +
>> + return (timeout ? -ETIMEDOUT : j);
>> +}
>> +
>> +static int virtio_i2c_xfer(struct i2c_adapter *adap, struct i2c_msg *msgs, int num)
>> +{
>> + struct virtio_i2c *vi = i2c_get_adapdata(adap);
>> + struct virtqueue *vq = vi->vq;
>> + struct virtio_i2c_req *reqs;
>> + unsigned long time_left;
>> + int ret, nr;
>> +
>> + reqs = kcalloc(num, sizeof(*reqs), GFP_KERNEL);
>> + if (!reqs)
>> + return -ENOMEM;
>> +
>> + mutex_lock(&vi->lock);
>> +
>> + ret = virtio_i2c_send_reqs(vq, reqs, msgs, num);
>> + if (ret == 0)
>> + goto err_unlock_free;
>> +
>> + nr = ret;
>> + reinit_completion(&vi->completion);
>> + virtqueue_kick(vq);
>> +
>> + time_left = wait_for_completion_timeout(&vi->completion, adap->timeout);
>> + if (!time_left) {
>> + dev_err(&adap->dev, "virtio i2c backend timeout.\n");
>> + ret = virtio_i2c_complete_reqs(vq, reqs, msgs, nr, true);
>> + goto err_unlock_free;
>> + }
>> +
>> + ret = virtio_i2c_complete_reqs(vq, reqs, msgs, nr, false);
> And this can be optimized as well:
>
> time_left = wait_for_completion_timeout(&vi->completion, adap->timeout);
> if (!time_left)
> dev_err(&adap->dev, "virtio i2c backend timeout.\n");
>
> ret = virtio_i2c_complete_reqs(vq, reqs, msgs, nr, !time_left);
Good optimization here.
_______________________________________________
Virtualization mailing list
Virtualization@lists.linux-foundation.org
https://lists.linuxfoundation.org/mailman/listinfo/virtualization
next prev parent reply other threads:[~2021-03-22 7:54 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 13:35 [PATCH v9] i2c: virtio: add a virtio i2c frontend driver Jie Deng
2021-03-22 13:35 ` Jie Deng
2021-03-22 6:41 ` Viresh Kumar
2021-03-22 7:53 ` Jie Deng [this message]
2021-03-22 7:53 ` Jie Deng
2021-03-22 7:57 ` Viresh Kumar
2021-03-22 7:58 ` Viresh Kumar
2021-03-22 8:19 ` Michael S. Tsirkin
2021-03-22 8:19 ` Michael S. Tsirkin
2021-03-22 8:28 ` Jie Deng
2021-03-22 8:28 ` Jie Deng
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=dbb5dfe9-8ee6-e3f8-3681-d0ec83282930@intel.com \
--to=jie.deng@intel.com \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=andriy.shevchenko@linux.intel.com \
--cc=arnd@arndb.de \
--cc=bjorn.andersson@linaro.org \
--cc=conghui.chen@intel.com \
--cc=jarkko.nikula@linux.intel.com \
--cc=jasowang@redhat.com \
--cc=kblaiech@mellanox.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=rppt@kernel.org \
--cc=shuo.a.liu@intel.com \
--cc=stefanha@redhat.com \
--cc=tali.perry1@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=viresh.kumar@linaro.org \
--cc=virtualization@lists.linux-foundation.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=wsa@kernel.org \
--cc=yu1.wang@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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.