2005-04-16 16:20:36 -06:00
|
|
|
/*
|
|
|
|
|
* local mtrr defines.
|
|
|
|
|
*/
|
|
|
|
|
|
2008-01-30 05:30:31 -07:00
|
|
|
#include <linux/types.h>
|
|
|
|
|
#include <linux/stddef.h>
|
2005-04-16 16:20:36 -06:00
|
|
|
|
|
|
|
|
#define MTRRcap_MSR 0x0fe
|
|
|
|
|
#define MTRRdefType_MSR 0x2ff
|
|
|
|
|
|
|
|
|
|
#define MTRRphysBase_MSR(reg) (0x200 + 2 * (reg))
|
|
|
|
|
#define MTRRphysMask_MSR(reg) (0x200 + 2 * (reg) + 1)
|
|
|
|
|
|
|
|
|
|
#define NUM_FIXED_RANGES 88
|
x86, 32-bit: trim memory not covered by wb mtrrs
On some machines, buggy BIOSes don't properly setup WB MTRRs to cover all
available RAM, meaning the last few megs (or even gigs) of memory will be
marked uncached. Since Linux tends to allocate from high memory addresses
first, this causes the machine to be unusably slow as soon as the kernel
starts really using memory (i.e. right around init time).
This patch works around the problem by scanning the MTRRs at boot and
figuring out whether the current end_pfn value (setup by early e820 code)
goes beyond the highest WB MTRR range, and if so, trimming it to match. A
fairly obnoxious KERN_WARNING is printed too, letting the user know that
not all of their memory is available due to a likely BIOS bug.
Something similar could be done on i386 if needed, but the boot ordering
would be slightly different, since the MTRR code on i386 depends on the
boot_cpu_data structure being setup.
This patch fixes a bug in the last patch that caused the code to run on
non-Intel machines (AMD machines apparently don't need it and it's untested
on other non-Intel machines, so best keep it off).
Further enhancements and fixes from:
Yinghai Lu <Yinghai.Lu@Sun.COM>
Andi Kleen <ak@suse.de>
Signed-off-by: Jesse Barnes <jesse.barnes@intel.com>
Tested-by: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Andi Kleen <andi@firstfloor.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 05:33:18 -07:00
|
|
|
#define MAX_VAR_RANGES 256
|
2005-04-16 16:20:36 -06:00
|
|
|
#define MTRRfix64K_00000_MSR 0x250
|
|
|
|
|
#define MTRRfix16K_80000_MSR 0x258
|
|
|
|
|
#define MTRRfix16K_A0000_MSR 0x259
|
|
|
|
|
#define MTRRfix4K_C0000_MSR 0x268
|
|
|
|
|
#define MTRRfix4K_C8000_MSR 0x269
|
|
|
|
|
#define MTRRfix4K_D0000_MSR 0x26a
|
|
|
|
|
#define MTRRfix4K_D8000_MSR 0x26b
|
|
|
|
|
#define MTRRfix4K_E0000_MSR 0x26c
|
|
|
|
|
#define MTRRfix4K_E8000_MSR 0x26d
|
|
|
|
|
#define MTRRfix4K_F0000_MSR 0x26e
|
|
|
|
|
#define MTRRfix4K_F8000_MSR 0x26f
|
|
|
|
|
|
|
|
|
|
#define MTRR_CHANGE_MASK_FIXED 0x01
|
|
|
|
|
#define MTRR_CHANGE_MASK_VARIABLE 0x02
|
|
|
|
|
#define MTRR_CHANGE_MASK_DEFTYPE 0x04
|
|
|
|
|
|
|
|
|
|
/* In the Intel processor's MTRR interface, the MTRR type is always held in
|
|
|
|
|
an 8 bit field: */
|
|
|
|
|
typedef u8 mtrr_type;
|
|
|
|
|
|
x86, 32-bit: trim memory not covered by wb mtrrs
On some machines, buggy BIOSes don't properly setup WB MTRRs to cover all
available RAM, meaning the last few megs (or even gigs) of memory will be
marked uncached. Since Linux tends to allocate from high memory addresses
first, this causes the machine to be unusably slow as soon as the kernel
starts really using memory (i.e. right around init time).
This patch works around the problem by scanning the MTRRs at boot and
figuring out whether the current end_pfn value (setup by early e820 code)
goes beyond the highest WB MTRR range, and if so, trimming it to match. A
fairly obnoxious KERN_WARNING is printed too, letting the user know that
not all of their memory is available due to a likely BIOS bug.
Something similar could be done on i386 if needed, but the boot ordering
would be slightly different, since the MTRR code on i386 depends on the
boot_cpu_data structure being setup.
This patch fixes a bug in the last patch that caused the code to run on
non-Intel machines (AMD machines apparently don't need it and it's untested
on other non-Intel machines, so best keep it off).
Further enhancements and fixes from:
Yinghai Lu <Yinghai.Lu@Sun.COM>
Andi Kleen <ak@suse.de>
Signed-off-by: Jesse Barnes <jesse.barnes@intel.com>
Tested-by: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Andi Kleen <andi@firstfloor.org>
Cc: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 05:33:18 -07:00
|
|
|
extern unsigned int mtrr_usage_table[MAX_VAR_RANGES];
|
|
|
|
|
|
2005-04-16 16:20:36 -06:00
|
|
|
struct mtrr_ops {
|
|
|
|
|
u32 vendor;
|
|
|
|
|
u32 use_intel_if;
|
|
|
|
|
// void (*init)(void);
|
|
|
|
|
void (*set)(unsigned int reg, unsigned long base,
|
|
|
|
|
unsigned long size, mtrr_type type);
|
|
|
|
|
void (*set_all)(void);
|
|
|
|
|
|
|
|
|
|
void (*get)(unsigned int reg, unsigned long *base,
|
[PATCH] i386: fix MTRR code
Until not so long ago, there were system log messages pointing to
inconsistent MTRR setup of the video frame buffer caused by the way vesafb
and X worked. While vesafb was fixed meanwhile, I believe fixing it there
only hides a shortcoming in the MTRR code itself, in that that code is not
symmetric with respect to the ordering of attempts to set up two (or more)
regions where one contains the other. In the current shape, it permits
only setting up sub-regions of pre-exisiting ones. The patch below makes
this symmetric.
While working on that I noticed a few more inconsistencies in that code,
namely
- use of 'unsigned int' for sizes in many, but not all places (the patch
is converting this to use 'unsigned long' everywhere, which specifically
might be necessary for x86-64 once a processor supporting more than 44
physical address bits would become available)
- the code to correct inconsistent settings during secondary processor
startup tried (if necessary) to correct, among other things, the value
in IA32_MTRR_DEF_TYPE, however the newly computed value would never get
used (i.e. stored in the respective MSR)
- the generic range validation code checked that the end of the
to-be-added range would be above 1MB; the value checked should have been
the start of the range
- when contained regions are detected, previously this was allowed only
when the old region was uncacheable; this can be symmetric (i.e. the new
region can also be uncacheable) and even further as per Intel's
documentation write-trough and write-back for either region is also
compatible with the respective opposite in the other
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andi Kleen <ak@suse.de>
2006-12-06 18:14:09 -07:00
|
|
|
unsigned long *size, mtrr_type * type);
|
|
|
|
|
int (*get_free_region)(unsigned long base, unsigned long size,
|
|
|
|
|
int replace_reg);
|
2005-04-16 16:20:36 -06:00
|
|
|
int (*validate_add_page)(unsigned long base, unsigned long size,
|
|
|
|
|
unsigned int type);
|
|
|
|
|
int (*have_wrcomb)(void);
|
|
|
|
|
};
|
|
|
|
|
|
[PATCH] i386: fix MTRR code
Until not so long ago, there were system log messages pointing to
inconsistent MTRR setup of the video frame buffer caused by the way vesafb
and X worked. While vesafb was fixed meanwhile, I believe fixing it there
only hides a shortcoming in the MTRR code itself, in that that code is not
symmetric with respect to the ordering of attempts to set up two (or more)
regions where one contains the other. In the current shape, it permits
only setting up sub-regions of pre-exisiting ones. The patch below makes
this symmetric.
While working on that I noticed a few more inconsistencies in that code,
namely
- use of 'unsigned int' for sizes in many, but not all places (the patch
is converting this to use 'unsigned long' everywhere, which specifically
might be necessary for x86-64 once a processor supporting more than 44
physical address bits would become available)
- the code to correct inconsistent settings during secondary processor
startup tried (if necessary) to correct, among other things, the value
in IA32_MTRR_DEF_TYPE, however the newly computed value would never get
used (i.e. stored in the respective MSR)
- the generic range validation code checked that the end of the
to-be-added range would be above 1MB; the value checked should have been
the start of the range
- when contained regions are detected, previously this was allowed only
when the old region was uncacheable; this can be symmetric (i.e. the new
region can also be uncacheable) and even further as per Intel's
documentation write-trough and write-back for either region is also
compatible with the respective opposite in the other
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andi Kleen <ak@suse.de>
2006-12-06 18:14:09 -07:00
|
|
|
extern int generic_get_free_region(unsigned long base, unsigned long size,
|
|
|
|
|
int replace_reg);
|
2005-04-16 16:20:36 -06:00
|
|
|
extern int generic_validate_add_page(unsigned long base, unsigned long size,
|
|
|
|
|
unsigned int type);
|
|
|
|
|
|
|
|
|
|
extern struct mtrr_ops generic_mtrr_ops;
|
|
|
|
|
|
|
|
|
|
extern int positive_have_wrcomb(void);
|
|
|
|
|
|
|
|
|
|
/* library functions for processor-specific routines */
|
|
|
|
|
struct set_mtrr_context {
|
|
|
|
|
unsigned long flags;
|
|
|
|
|
unsigned long cr4val;
|
[PATCH] i386: fix MTRR code
Until not so long ago, there were system log messages pointing to
inconsistent MTRR setup of the video frame buffer caused by the way vesafb
and X worked. While vesafb was fixed meanwhile, I believe fixing it there
only hides a shortcoming in the MTRR code itself, in that that code is not
symmetric with respect to the ordering of attempts to set up two (or more)
regions where one contains the other. In the current shape, it permits
only setting up sub-regions of pre-exisiting ones. The patch below makes
this symmetric.
While working on that I noticed a few more inconsistencies in that code,
namely
- use of 'unsigned int' for sizes in many, but not all places (the patch
is converting this to use 'unsigned long' everywhere, which specifically
might be necessary for x86-64 once a processor supporting more than 44
physical address bits would become available)
- the code to correct inconsistent settings during secondary processor
startup tried (if necessary) to correct, among other things, the value
in IA32_MTRR_DEF_TYPE, however the newly computed value would never get
used (i.e. stored in the respective MSR)
- the generic range validation code checked that the end of the
to-be-added range would be above 1MB; the value checked should have been
the start of the range
- when contained regions are detected, previously this was allowed only
when the old region was uncacheable; this can be symmetric (i.e. the new
region can also be uncacheable) and even further as per Intel's
documentation write-trough and write-back for either region is also
compatible with the respective opposite in the other
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andi Kleen <ak@suse.de>
2006-12-06 18:14:09 -07:00
|
|
|
u32 deftype_lo;
|
|
|
|
|
u32 deftype_hi;
|
|
|
|
|
u32 ccr3;
|
2005-04-16 16:20:36 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
struct mtrr_var_range {
|
[PATCH] i386: fix MTRR code
Until not so long ago, there were system log messages pointing to
inconsistent MTRR setup of the video frame buffer caused by the way vesafb
and X worked. While vesafb was fixed meanwhile, I believe fixing it there
only hides a shortcoming in the MTRR code itself, in that that code is not
symmetric with respect to the ordering of attempts to set up two (or more)
regions where one contains the other. In the current shape, it permits
only setting up sub-regions of pre-exisiting ones. The patch below makes
this symmetric.
While working on that I noticed a few more inconsistencies in that code,
namely
- use of 'unsigned int' for sizes in many, but not all places (the patch
is converting this to use 'unsigned long' everywhere, which specifically
might be necessary for x86-64 once a processor supporting more than 44
physical address bits would become available)
- the code to correct inconsistent settings during secondary processor
startup tried (if necessary) to correct, among other things, the value
in IA32_MTRR_DEF_TYPE, however the newly computed value would never get
used (i.e. stored in the respective MSR)
- the generic range validation code checked that the end of the
to-be-added range would be above 1MB; the value checked should have been
the start of the range
- when contained regions are detected, previously this was allowed only
when the old region was uncacheable; this can be symmetric (i.e. the new
region can also be uncacheable) and even further as per Intel's
documentation write-trough and write-back for either region is also
compatible with the respective opposite in the other
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andi Kleen <ak@suse.de>
2006-12-06 18:14:09 -07:00
|
|
|
u32 base_lo;
|
|
|
|
|
u32 base_hi;
|
|
|
|
|
u32 mask_lo;
|
|
|
|
|
u32 mask_hi;
|
2005-04-16 16:20:36 -06:00
|
|
|
};
|
|
|
|
|
|
|
|
|
|
void set_mtrr_done(struct set_mtrr_context *ctxt);
|
|
|
|
|
void set_mtrr_cache_disable(struct set_mtrr_context *ctxt);
|
|
|
|
|
void set_mtrr_prepare_save(struct set_mtrr_context *ctxt);
|
|
|
|
|
|
|
|
|
|
void get_mtrr_state(void);
|
|
|
|
|
|
|
|
|
|
extern void set_mtrr_ops(struct mtrr_ops * ops);
|
|
|
|
|
|
2007-02-13 05:26:23 -07:00
|
|
|
extern u64 size_or_mask, size_and_mask;
|
2005-04-16 16:20:36 -06:00
|
|
|
extern struct mtrr_ops * mtrr_if;
|
|
|
|
|
|
|
|
|
|
#define is_cpu(vnd) (mtrr_if && mtrr_if->vendor == X86_VENDOR_##vnd)
|
|
|
|
|
#define use_intel() (mtrr_if && mtrr_if->use_intel_if == 1)
|
|
|
|
|
|
|
|
|
|
extern unsigned int num_var_ranges;
|
|
|
|
|
|
|
|
|
|
void mtrr_state_warn(void);
|
[PATCH] i386: fix MTRR code
Until not so long ago, there were system log messages pointing to
inconsistent MTRR setup of the video frame buffer caused by the way vesafb
and X worked. While vesafb was fixed meanwhile, I believe fixing it there
only hides a shortcoming in the MTRR code itself, in that that code is not
symmetric with respect to the ordering of attempts to set up two (or more)
regions where one contains the other. In the current shape, it permits
only setting up sub-regions of pre-exisiting ones. The patch below makes
this symmetric.
While working on that I noticed a few more inconsistencies in that code,
namely
- use of 'unsigned int' for sizes in many, but not all places (the patch
is converting this to use 'unsigned long' everywhere, which specifically
might be necessary for x86-64 once a processor supporting more than 44
physical address bits would become available)
- the code to correct inconsistent settings during secondary processor
startup tried (if necessary) to correct, among other things, the value
in IA32_MTRR_DEF_TYPE, however the newly computed value would never get
used (i.e. stored in the respective MSR)
- the generic range validation code checked that the end of the
to-be-added range would be above 1MB; the value checked should have been
the start of the range
- when contained regions are detected, previously this was allowed only
when the old region was uncacheable; this can be symmetric (i.e. the new
region can also be uncacheable) and even further as per Intel's
documentation write-trough and write-back for either region is also
compatible with the respective opposite in the other
Signed-off-by: Jan Beulich <jbeulich@novell.com>
Signed-off-by: Andi Kleen <ak@suse.de>
2006-12-06 18:14:09 -07:00
|
|
|
const char *mtrr_attrib_to_str(int x);
|
2005-04-16 16:20:36 -06:00
|
|
|
void mtrr_wrmsr(unsigned, unsigned, unsigned);
|
|
|
|
|
|
