mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Dmitry Baryshkov' <dmitry.baryshkov@linaro.org>,
	Qing Wang <wangqing@vivo.com>,
	Stanimir Varbanov <stanimir.varbanov@linaro.org>,
	"Andy Gross" <agross@kernel.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	"linux-media@vger.kernel.org" <linux-media@vger.kernel.org>,
	"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH] media: qcom: use div64_u64() instead of do_div()
Date: Fri, 11 Feb 2022 12:21:14 +0000	[thread overview]
Message-ID: <11c926109b394ae9bfc3230b68cdaf14@AcuMS.aculab.com> (raw)
In-Reply-To: <19b96972-cee7-937f-21ce-c78982ed2048@linaro.org>

From: Dmitry Baryshkov
> Sent: 10 February 2022 10:17
> 
> On 09/02/2022 11:38, Qing Wang wrote:
> > From: Wang Qing <wangqing@vivo.com>
> >
> > do_div() does a 64-by-32 division.
> > When the divisor is u64, do_div() truncates it to 32 bits, this means it
> > can test non-zero and be truncated to zero for division.
> >
> > fix do_div.cocci warning:
> > do_div() does a 64-by-32 division, please consider using div64_u64 instead.
> 
> 
> NAK
> 
> The div64_u64 is not equivalent to do_div. It returns the quotient
> rather than modifying the first arg. Moreover it is unoptimal on 32-bit
> arches.
> 
> >
> > Signed-off-by: Wang Qing <wangqing@vivo.com>
> > ---
> >   drivers/media/platform/qcom/venus/vdec.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/media/platform/qcom/venus/vdec.c b/drivers/media/platform/qcom/venus/vdec.c
> > index 91da3f5..941a904
> > --- a/drivers/media/platform/qcom/venus/vdec.c
> > +++ b/drivers/media/platform/qcom/venus/vdec.c
> > @@ -435,7 +435,7 @@ static int vdec_s_parm(struct file *file, void *fh, struct v4l2_streamparm *a)
> >   		return -EINVAL;
> >
> >   	fps = (u64)USEC_PER_SEC;
> > -	do_div(fps, us_per_frame);
> > +	div64_u64(fps, us_per_frame);

That one is particularly insane to begin with.
Why was it even do_div()?
I guess because:
	fps = USEC_PER_SEC / us_per_frame;
caused the compiler to call the 64bit divide function because the 'us_per_frame'
is 64bit - even though the code only makes sense if it is small.

The correct fix here is probably to change the type of us_per_frame to 32bit
or just do:
	fps = USEC_PER_FRAM / (unsigned int)us_per_frame.

Oh, and fps definitely doesn't need to be 64bit either.

IMHO all (and I mean ALL) of these patches to change do_div() to div64_u64()
need dropping.
Maybe one or two are real problems, but the surrounding code needs
correctly examining.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)

      reply	other threads:[~2022-02-11 12:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  8:38 Qing Wang
2022-02-10 10:16 ` Dmitry Baryshkov
2022-02-11 12:21   ` David Laight [this message]

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=11c926109b394ae9bfc3230b68cdaf14@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=agross@kernel.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=stanimir.varbanov@linaro.org \
    --cc=wangqing@vivo.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

all inboxes | Powered by JetHome®