qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Hanna Czenczek <hreitz@redhat.com>
To: zhenwei pi <pizhenwei@bytedance.com>,
	berto@igalia.com, kwolf@redhat.com,  groug@kaod.org,
	qemu_oss@crudebyte.com
Cc: arei.gonglei@huawei.com, qemu-devel@nongnu.org,
	qemu-block@nongnu.org, berrange@redhat.com
Subject: Re: [PATCH v3 5/6] cryptodev: use NULL throttle timer cb for read direction
Date: Fri, 21 Jul 2023 17:42:15 +0200	[thread overview]
Message-ID: <a1eb5f47-60c4-9d52-7df7-16e0cfc44783@redhat.com> (raw)
In-Reply-To: <20230713064111.558652-6-pizhenwei@bytedance.com>

On 13.07.23 08:41, zhenwei pi wrote:
> Operations on a crytpodev are considered as *write* only, the callback

s/crytpodev/cryptodev/

> of read direction is never invoked. Use NULL instead of an unreachable
> path(cryptodev_backend_throttle_timer_cb on read direction).
>
> Reviewed-by: Alberto Garcia <berto@igalia.com>
> Signed-off-by: zhenwei pi <pizhenwei@bytedance.com>
> ---
>   backends/cryptodev.c | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/backends/cryptodev.c b/backends/cryptodev.c
> index 7d29517843..5cfa25c61c 100644
> --- a/backends/cryptodev.c
> +++ b/backends/cryptodev.c
> @@ -331,8 +331,7 @@ static void cryptodev_backend_set_throttle(CryptoDevBackend *backend, int field,
>       if (!enabled) {
>           throttle_init(&backend->ts);
>           throttle_timers_init(&backend->tt, qemu_get_aio_context(),
> -                             QEMU_CLOCK_REALTIME,
> -                             cryptodev_backend_throttle_timer_cb, /* FIXME */

Now it’ll be gone (good), but if you happen to add a FIXME again, it 
would be nice to explain in the same comment in the code what exactly 
needs fixing, and why it isn‘t being fixed at this point.

> +                             QEMU_CLOCK_REALTIME, NULL,
>                                cryptodev_backend_throttle_timer_cb, backend);
>       }

With the typo in the commit message fixed:

Reviewed-by: Hanna Czenczek <hreitz@redhat.com>



  reply	other threads:[~2023-07-21 15:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13  6:41 [PATCH v3 0/6] Misc fixes for throttle zhenwei pi
2023-07-13  6:41 ` [PATCH v3 1/6] throttle: introduce enum ThrottleType zhenwei pi
2023-07-21 15:42   ` Hanna Czenczek
2023-07-13  6:41 ` [PATCH v3 2/6] test-throttle: use " zhenwei pi
2023-07-21 15:43   ` Hanna Czenczek
2023-07-13  6:41 ` [PATCH v3 3/6] throttle: support read-only and write-only zhenwei pi
2023-07-21 15:42   ` Hanna Czenczek
2023-07-13  6:41 ` [PATCH v3 4/6] test-throttle: test read only and write only zhenwei pi
2023-07-21 15:43   ` Hanna Czenczek
2023-07-13  6:41 ` [PATCH v3 5/6] cryptodev: use NULL throttle timer cb for read direction zhenwei pi
2023-07-21 15:42   ` Hanna Czenczek [this message]
2023-07-13  6:41 ` [PATCH v3 6/6] throttle: use enum ThrottleType instead of bool is_write zhenwei pi
2023-07-21 16:03   ` Hanna Czenczek
2023-07-21  1:28 ` PING: [PATCH v3 0/6] Misc fixes for throttle zhenwei pi

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=a1eb5f47-60c4-9d52-7df7-16e0cfc44783@redhat.com \
    --to=hreitz@redhat.com \
    --cc=arei.gonglei@huawei.com \
    --cc=berrange@redhat.com \
    --cc=berto@igalia.com \
    --cc=groug@kaod.org \
    --cc=kwolf@redhat.com \
    --cc=pizhenwei@bytedance.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu_oss@crudebyte.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).