dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Dan Carpenter <dan.carpenter@linaro.org>
To: Lizhi Hou <lizhi.hou@amd.com>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [bug report] accel/amdxdna: Enhance power management settings
Date: Wed, 8 Jan 2025 21:19:41 +0300	[thread overview]
Message-ID: <2709d6f4-ece7-4def-b5e7-e99f4f01bd8b@stanley.mountain> (raw)
In-Reply-To: <47966a55-0272-b4c7-3717-fabf85cc0f3d@amd.com>

On Wed, Jan 08, 2025 at 10:14:47AM -0800, Lizhi Hou wrote:
> 
> On 1/8/25 00:40, Dan Carpenter wrote:
> > Hello Lizhi Hou,
> > 
> > Commit f4d7b8a6bc8c ("accel/amdxdna: Enhance power management
> > settings") from Dec 13, 2024 (linux-next), leads to the following
> > Smatch static checker warning:
> > 
> > 	drivers/accel/amdxdna/aie2_smu.c:68 npu1_set_dpm()
> > 	error: uninitialized symbol 'freq'.
> > 
> > drivers/accel/amdxdna/aie2_smu.c
> 
> Thanks for pointing this out. I will fix it.
> 
> I actually did run smatch_scripts/kchecker and it is clean.
> 
> Maybe I did not use the correct command. Could you share the instruction to
> reproduce this?
> 

This requires the cross function database which is simple to build but
takes hours. ~/smatch/smatch_scripts/build_kernel_data.sh.  Each time you
build the cross function database it adds a level to the call tree.
Having a one level call tree is slightly annoying because it give Smatch
a false sense of confidence.  I rebuild my database every day.  Probably
seven times is where it stops adding data.

regards,
dan carpenter


      reply	other threads:[~2025-01-08 18:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-08  8:40 [bug report] accel/amdxdna: Enhance power management settings Dan Carpenter
2025-01-08 18:14 ` Lizhi Hou
2025-01-08 18:19   ` Dan Carpenter [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=2709d6f4-ece7-4def-b5e7-e99f4f01bd8b@stanley.mountain \
    --to=dan.carpenter@linaro.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=lizhi.hou@amd.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