[Intel-gfx] [PATCH v2] Core-for-CI:ICL_only Disable ACPI idle driver
Rafael J. Wysocki
rafael.j.wysocki at intel.com
Tue Apr 9 15:49:23 UTC 2019
On 4/9/2019 8:29 AM, Anshuman Gupta wrote:
> There were few system hung observed while running i915_pm_rpm igt test.
> FDO https://bugs.freedesktop.org/show_bug.cgi?id=108840
> Root cause is believed to due to page fault in ACPI idle driver.
> (FDO comment 18).
> It has been suggested by Daniel Vetter to disable ACPI idle
> driver for Core-for-CI, only for ICL.
>
> This hacky patch is only for ICL processor and for Core-for-CI branch.
>
> v2: Fixed compilation errors raised by lkp.
> commit message improvement.
>
> Cc: martin.peres at intel.com
> Cc: daniel.vetter at intel.com
>
> Signed-off-by: Anshuman Gupta <anshuman.gupta at intel.com>
This is fine only as long as it doesn't anywhere close to the mainline.
If ACPI idle crashes on new Intel HW, it needs to be fixed to work with
it instead of refusing to work on it.
> ---
> drivers/acpi/processor_driver.c | 18 +++++++++++++++++-
> 1 file changed, 17 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/acpi/processor_driver.c b/drivers/acpi/processor_driver.c
> index 9d6aff2..ee842a2f 100644
> --- a/drivers/acpi/processor_driver.c
> +++ b/drivers/acpi/processor_driver.c
> @@ -35,6 +35,12 @@
>
> #include <acpi/processor.h>
>
> +/* Only for Core-for-CI so don't want ia64 to fail compilation.*/
> +#ifdef CONFIG_X86
> +#include <asm/cpu_device_id.h>
> +#include <asm/intel-family.h>
> +#endif
> +
> #include "internal.h"
>
> #define ACPI_PROCESSOR_NOTIFY_PERFORMANCE 0x80
> @@ -58,6 +64,13 @@ static const struct acpi_device_id processor_device_ids[] = {
> };
> MODULE_DEVICE_TABLE(acpi, processor_device_ids);
>
> +#define ICPU(model) { X86_VENDOR_INTEL, 6, model, X86_FEATURE_ANY, }
> +static const struct x86_cpu_id intel_cpu_ids[] = {
> + ICPU(INTEL_FAM6_ICELAKE_MOBILE), /* ICL */
> + {}
> +};
> +MODULE_DEVICE_TABLE(x86cpu, intel_cpu_ids);
> +
> static struct device_driver acpi_processor_driver = {
> .name = "processor",
> .bus = &cpu_subsys,
> @@ -226,6 +239,7 @@ static inline void acpi_pss_perf_exit(struct acpi_processor *pr,
> static int __acpi_processor_start(struct acpi_device *device)
> {
> struct acpi_processor *pr = acpi_driver_data(device);
> + const struct x86_cpu_id *id;
> acpi_status status;
> int result = 0;
>
> @@ -239,7 +253,9 @@ static int __acpi_processor_start(struct acpi_device *device)
> if (result && !IS_ENABLED(CONFIG_ACPI_CPU_FREQ_PSS))
> dev_dbg(&device->dev, "CPPC data invalid or not present\n");
>
> - if (!cpuidle_get_driver() || cpuidle_get_driver() == &acpi_idle_driver)
> + id = x86_match_cpu(intel_cpu_ids);
> + if (!id && (!cpuidle_get_driver() || cpuidle_get_driver() ==
> + &acpi_idle_driver))
> acpi_processor_power_init(pr);
>
> result = acpi_pss_perf_init(pr, device);
More information about the Intel-gfx
mailing list