[SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Mantic |
Won't Fix
|
Undecided
|
Unassigned | ||
Noble |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
[Impact]
Ubuntu currently sets CONFIG_
However, unlike plug and play devices, there is no way to load uncore module when user tries to use uncore event.
Also, a primary motivation to add module support in uncore driver was to ease development (https:/
Its not immediately apparent from perf tool output that the "amd-uncore" module is not loaded when opening "amd_df" or "amd_l3" events fail or when they do not show up in "perf list" despite using a compatible kernel. Since the primary motivation of the commit [1] that made it possible for this to be loaded as a module was to make development easier, CONFIG_
[1] https:/
[2] https:/
[Fix]
Change kernel config to CONFIG_
[Test case]
(How can this change be tested/verified?)
[Where problems may occur]
(What side effects or regressions could this change create?)
summary: |
- change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y + [SRU] change CONFIG_PERF_EVENTS_AMD_UNCORE from m to y |
Changed in linux (Ubuntu Mantic): | |
status: | New → Confirmed |
description: | updated |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 2033416
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.