From: kernel test robot <lkp@intel.com>
To: Meng Li <li.meng@amd.com>,
"Rafael J . Wysocki" <rafael.j.wysocki@intel.com>,
Huang Rui <ray.huang@amd.com>
Cc: llvm@lists.linux.dev, oe-kbuild-all@lists.linux.dev,
linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org,
x86@kernel.org, linux-acpi@vger.kernel.org,
Shuah Khan <skhan@linuxfoundation.org>,
linux-kselftest@vger.kernel.org,
Nathan Fontenot <nathan.fontenot@amd.com>,
Deepak Sharma <deepak.sharma@amd.com>,
Alex Deucher <alexander.deucher@amd.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Shimmer Huang <shimmer.huang@amd.com>,
Perry Yuan <Perry.Yuan@amd.com>,
Xiaojian Du <Xiaojian.Du@amd.com>,
Viresh Kumar <viresh.kumar@linaro.org>,
Borislav Petkov <bp@alien8.de>, Meng Li <li.meng@amd.com>
Subject: Re: [PATCH V4 4/7] cpufreq: Add a notification message that the highest perf has changed
Date: Wed, 30 Aug 2023 00:27:13 +0800 [thread overview]
Message-ID: <202308300057.ASUJQpsV-lkp@intel.com> (raw)
In-Reply-To: <20230829064340.1136448-5-li.meng@amd.com>
Hi Meng,
kernel test robot noticed the following build errors:
[auto build test ERROR on rafael-pm/linux-next]
[also build test ERROR on linus/master v6.5 next-20230829]
[cannot apply to tip/x86/core]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we suggest to use '--base' as documented in
https://git-scm.com/docs/git-format-patch#_base_tree_information]
url: https://github.com/intel-lab-lkp/linux/commits/Meng-Li/x86-Drop-CPU_SUP_INTEL-from-SCHED_MC_PRIO-for-the-expansion/20230829-144723
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git linux-next
patch link: https://lore.kernel.org/r/20230829064340.1136448-5-li.meng%40amd.com
patch subject: [PATCH V4 4/7] cpufreq: Add a notification message that the highest perf has changed
config: i386-randconfig-r031-20230829 (https://download.01.org/0day-ci/archive/20230830/202308300057.ASUJQpsV-lkp@intel.com/config)
compiler: clang version 16.0.4 (https://github.com/llvm/llvm-project.git ae42196bc493ffe877a7e3dff8be32035dea4d07)
reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20230830/202308300057.ASUJQpsV-lkp@intel.com/reproduce)
If you fix the issue in a separate patch/commit (i.e. not just a new version of
the same patch/commit), kindly add following tags
| Reported-by: kernel test robot <lkp@intel.com>
| Closes: https://lore.kernel.org/oe-kbuild-all/202308300057.ASUJQpsV-lkp@intel.com/
All errors (new ones prefixed by >>):
>> drivers/acpi/processor_driver.c:88:3: error: call to undeclared function 'cpufreq_update_highest_perf'; ISO C99 and later do not support implicit function declarations [-Wimplicit-function-declaration]
cpufreq_update_highest_perf(pr->id);
^
1 error generated.
vim +/cpufreq_update_highest_perf +88 drivers/acpi/processor_driver.c
53
54 static void acpi_processor_notify(acpi_handle handle, u32 event, void *data)
55 {
56 struct acpi_device *device = data;
57 struct acpi_processor *pr;
58 int saved;
59
60 if (device->handle != handle)
61 return;
62
63 pr = acpi_driver_data(device);
64 if (!pr)
65 return;
66
67 switch (event) {
68 case ACPI_PROCESSOR_NOTIFY_PERFORMANCE:
69 saved = pr->performance_platform_limit;
70 acpi_processor_ppc_has_changed(pr, 1);
71 if (saved == pr->performance_platform_limit)
72 break;
73 acpi_bus_generate_netlink_event(device->pnp.device_class,
74 dev_name(&device->dev), event,
75 pr->performance_platform_limit);
76 break;
77 case ACPI_PROCESSOR_NOTIFY_POWER:
78 acpi_processor_power_state_has_changed(pr);
79 acpi_bus_generate_netlink_event(device->pnp.device_class,
80 dev_name(&device->dev), event, 0);
81 break;
82 case ACPI_PROCESSOR_NOTIFY_THROTTLING:
83 acpi_processor_tstate_has_changed(pr);
84 acpi_bus_generate_netlink_event(device->pnp.device_class,
85 dev_name(&device->dev), event, 0);
86 break;
87 case ACPI_PROCESSOR_NOTIFY_HIGEST_PERF_CHANGED:
> 88 cpufreq_update_highest_perf(pr->id);
89 acpi_bus_generate_netlink_event(device->pnp.device_class,
90 dev_name(&device->dev), event, 0);
91 break;
92 default:
93 acpi_handle_debug(handle, "Unsupported event [0x%x]\n", event);
94 break;
95 }
96
97 return;
98 }
99
--
0-DAY CI Kernel Test Service
https://github.com/intel/lkp-tests/wiki
next prev parent reply other threads:[~2023-08-29 16:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 6:43 [PATCH V4 0/7] AMD Pstate Preferred Core Meng Li
2023-08-29 6:43 ` [PATCH V4 1/7] x86: Drop CPU_SUP_INTEL from SCHED_MC_PRIO for the expansion Meng Li
2023-08-29 6:43 ` [PATCH V4 2/7] acpi: cppc: Add get the highest performance cppc control Meng Li
2023-08-29 6:43 ` [PATCH V4 3/7] cpufreq: amd-pstate: Enable AMD Pstate Preferred Core Supporting Meng Li
2023-08-29 8:01 ` Huang Rui
2023-08-31 1:42 ` Meng, Li (Jassmine)
2023-08-29 14:52 ` kernel test robot
2023-08-29 6:43 ` [PATCH V4 4/7] cpufreq: Add a notification message that the highest perf has changed Meng Li
2023-08-29 16:27 ` kernel test robot [this message]
2023-08-29 6:43 ` [PATCH V4 5/7] cpufreq: amd-pstate: Update AMD Pstate Preferred Core ranking dynamically Meng Li
2023-08-29 6:43 ` [PATCH V4 6/7] Documentation: amd-pstate: introduce AMD Pstate Preferred Core Meng Li
2023-08-29 8:07 ` Huang Rui
2023-08-29 6:43 ` [PATCH V4 7/7] Documentation: introduce AMD Pstate Preferrd Core mode kernel command line options Meng Li
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=202308300057.ASUJQpsV-lkp@intel.com \
--to=lkp@intel.com \
--cc=Perry.Yuan@amd.com \
--cc=Xiaojian.Du@amd.com \
--cc=alexander.deucher@amd.com \
--cc=bp@alien8.de \
--cc=deepak.sharma@amd.com \
--cc=li.meng@amd.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=llvm@lists.linux.dev \
--cc=mario.limonciello@amd.com \
--cc=nathan.fontenot@amd.com \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=rafael.j.wysocki@intel.com \
--cc=ray.huang@amd.com \
--cc=shimmer.huang@amd.com \
--cc=skhan@linuxfoundation.org \
--cc=viresh.kumar@linaro.org \
--cc=x86@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;
as well as URLs for NNTP newsgroup(s).