public inbox for drm-ai-reviews@public-inbox.freedesktop.org
 help / color / mirror / Atom feed
From: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
To: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
Cc: srini@kernel.org, linux-arm-msm@vger.kernel.org,
	gregkh@linuxfoundation.org, quic_bkumar@quicinc.com,
	linux-kernel@vger.kernel.org, quic_chennak@quicinc.com,
	dri-devel@lists.freedesktop.org, arnd@arndb.de
Subject: Re: [PATCH v11 4/4] misc: fastrpc: Add polling mode support for fastRPC driver
Date: Wed, 20 May 2026 16:36:48 +0300	[thread overview]
Message-ID: <jtqfnly2ma56gbdstyk7exk4lhw5nild57uyokkkgrtnnqqscv@xik2phrs4v6t> (raw)
In-Reply-To: <20260520065047.3415790-5-ekansh.gupta@oss.qualcomm.com>

On Wed, May 20, 2026 at 12:20:47PM +0530, Ekansh Gupta wrote:
> For any remote call to DSP, after sending an invocation message,
> fastRPC driver waits for glink response and during this time the
> CPU can go into low power modes. This adds latency to overall fastrpc
> call as CPU wakeup and scheduling latencies are included. Add polling
> mode support with which fastRPC driver will poll continuously on a
> memory after sending a message to remote subsystem which will eliminate
> CPU wakeup and scheduling latencies and reduce fastRPC overhead. In case
> poll timeout happens, the call will fallback to normal RPC mode.  Poll
> mode can be enabled by user by using FASTRPC_IOCTL_SET_OPTION ioctl
> request with FASTRPC_POLL_MODE request id.
> 
> Signed-off-by: Ekansh Gupta <ekansh.gupta@oss.qualcomm.com>
> ---
>  drivers/misc/fastrpc.c      | 167 ++++++++++++++++++++++++++++++++++--
>  include/uapi/misc/fastrpc.h |  29 +++++++
>  2 files changed, 189 insertions(+), 7 deletions(-)
> 
> @@ -1813,6 +1907,35 @@ static int fastrpc_get_info_from_kernel(struct fastrpc_ioctl_capability *cap,
>  	return 0;
>  }
>  
> +static int fastrpc_set_option(struct fastrpc_user *fl, char __user *argp)
> +{
> +	struct fastrpc_ioctl_set_option opt = {0};
> +	int i;
> +
> +	if (!fl->cctx->poll_mode_supported)
> +		return -EOPNOTSUPP;

This is being handled too early. What if the user passes any other
option?

> +
> +	if (copy_from_user(&opt, argp, sizeof(opt)))
> +		return -EFAULT;
> +
> +	for (i = 0; i < ARRAY_SIZE(opt.reserved); i++) {
> +		if (opt.reserved[i] != 0)
> +			return -EINVAL;
> +	}
> +
> +	if (opt.request_id != FASTRPC_POLL_MODE)
> +		return -EINVAL;
> +
> +	if (opt.value == FASTRPC_POLL_MODE_ENABLE)
> +		fl->poll_mode = true;
> +	else if (opt.value == FASTRPC_POLL_MODE_DISABLE)
> +		fl->poll_mode = false;
> +	else
> +		return -EINVAL;
> +
> +	return 0;
> +}
> +

-- 
With best wishes
Dmitry

  reply	other threads:[~2026-05-20 13:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-20  6:50 [PATCH v11 0/4] misc: fastrpc: Add polling mode support Ekansh Gupta
2026-05-20  6:50 ` [PATCH v11 1/4] misc: fastrpc: Move fdlist to invoke context structure Ekansh Gupta
2026-05-25 12:12   ` Claude review: " Claude Code Review Bot
2026-05-20  6:50 ` [PATCH v11 2/4] misc: fastrpc: Replace hardcoded ctxid mask with GENMASK Ekansh Gupta
2026-05-25 12:12   ` Claude review: " Claude Code Review Bot
2026-05-20  6:50 ` [PATCH v11 3/4] misc: fastrpc: Expand context ID mask for DSP polling mode support Ekansh Gupta
2026-05-25 12:12   ` Claude review: " Claude Code Review Bot
2026-05-20  6:50 ` [PATCH v11 4/4] misc: fastrpc: Add polling mode support for fastRPC driver Ekansh Gupta
2026-05-20 13:36   ` Dmitry Baryshkov [this message]
2026-05-21  4:06     ` Ekansh Gupta
2026-05-25 12:12   ` Claude review: " Claude Code Review Bot
2026-05-25 12:12 ` Claude review: misc: fastrpc: Add polling mode support Claude Code Review Bot

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=jtqfnly2ma56gbdstyk7exk4lhw5nild57uyokkkgrtnnqqscv@xik2phrs4v6t \
    --to=dmitry.baryshkov@oss.qualcomm.com \
    --cc=arnd@arndb.de \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=ekansh.gupta@oss.qualcomm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quic_bkumar@quicinc.com \
    --cc=quic_chennak@quicinc.com \
    --cc=srini@kernel.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