2005-04-17 05:20:36 +07:00
|
|
|
/*
|
|
|
|
|
* Copyright 2001-2002 Pavel Machek <pavel@suse.cz>
|
|
|
|
|
* Based on code
|
|
|
|
|
* Copyright 2001 Patrick Mochel <mochel@osdl.org>
|
|
|
|
|
*/
|
2008-10-23 12:26:29 +07:00
|
|
|
#ifndef _ASM_X86_SUSPEND_32_H
|
|
|
|
|
#define _ASM_X86_SUSPEND_32_H
|
2008-06-11 04:45:45 +07:00
|
|
|
|
2005-04-17 05:20:36 +07:00
|
|
|
#include <asm/desc.h>
|
2015-04-24 07:46:00 +07:00
|
|
|
#include <asm/fpu/api.h>
|
2005-04-17 05:20:36 +07:00
|
|
|
|
|
|
|
|
/* image of the saved processor state */
|
|
|
|
|
struct saved_context {
|
2008-03-23 15:03:35 +07:00
|
|
|
u16 es, fs, gs, ss;
|
2005-04-17 05:20:36 +07:00
|
|
|
unsigned long cr0, cr2, cr3, cr4;
|
2010-06-08 05:32:49 +07:00
|
|
|
u64 misc_enable;
|
|
|
|
|
bool misc_enable_saved;
|
x86/pm: Introduce quirk framework to save/restore extra MSR registers around suspend/resume
A bug was reported that on certain Broadwell platforms, after
resuming from S3, the CPU is running at an anomalously low
speed.
It turns out that the BIOS has modified the value of the
THERM_CONTROL register during S3, and changed it from 0 to 0x10,
thus enabled clock modulation(bit4), but with undefined CPU Duty
Cycle(bit1:3) - which causes the problem.
Here is a simple scenario to reproduce the issue:
1. Boot up the system
2. Get MSR 0x19a, it should be 0
3. Put the system into sleep, then wake it up
4. Get MSR 0x19a, it shows 0x10, while it should be 0
Although some BIOSen want to change the CPU Duty Cycle during
S3, in our case we don't want the BIOS to do any modification.
Fix this issue by introducing a more generic x86 framework to
save/restore specified MSR registers(THERM_CONTROL in this case)
for suspend/resume. This allows us to fix similar bugs in a much
simpler way in the future.
When the kernel wants to protect certain MSRs during suspending,
we simply add a quirk entry in msr_save_dmi_table, and customize
the MSR registers inside the quirk callback, for example:
u32 msr_id_need_to_save[] = {MSR_ID0, MSR_ID1, MSR_ID2...};
and the quirk mechanism ensures that, once resumed from suspend,
the MSRs indicated by these IDs will be restored to their
original, pre-suspend values.
Since both 64-bit and 32-bit kernels are affected, this patch
covers the common 64/32-bit suspend/resume code path. And
because the MSRs specified by the user might not be available or
readable in any situation, we use rdmsrl_safe() to safely save
these MSRs.
Reported-and-tested-by: Marcin Kaszewski <marcin.kaszewski@intel.com>
Signed-off-by: Chen Yu <yu.c.chen@intel.com>
Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
Acked-by: Pavel Machek <pavel@ucw.cz>
Cc: Andy Lutomirski <luto@amacapital.net>
Cc: Borislav Petkov <bp@alien8.de>
Cc: Brian Gerst <brgerst@gmail.com>
Cc: Denys Vlasenko <dvlasenk@redhat.com>
Cc: H. Peter Anvin <hpa@zytor.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: bp@suse.de
Cc: len.brown@intel.com
Cc: linux@horizon.com
Cc: luto@kernel.org
Cc: rjw@rjwysocki.net
Link: http://lkml.kernel.org/r/c9abdcbc173dd2f57e8990e304376f19287e92ba.1448382971.git.yu.c.chen@intel.com
[ More edits to the naming of data structures. ]
Signed-off-by: Ingo Molnar <mingo@kernel.org>
2015-11-25 00:03:41 +07:00
|
|
|
struct saved_msrs saved_msrs;
|
2013-05-02 08:53:30 +07:00
|
|
|
struct desc_ptr gdt_desc;
|
2008-01-30 19:31:12 +07:00
|
|
|
struct desc_ptr idt;
|
2005-04-17 05:20:36 +07:00
|
|
|
u16 ldt;
|
|
|
|
|
u16 tss;
|
|
|
|
|
unsigned long tr;
|
|
|
|
|
unsigned long safety;
|
|
|
|
|
unsigned long return_address;
|
|
|
|
|
} __attribute__((packed));
|
|
|
|
|
|
2008-10-23 12:26:29 +07:00
|
|
|
#endif /* _ASM_X86_SUSPEND_32_H */
|