2005-04-16 22:20:36 +00:00
|
|
|
#include <linux/init.h>
|
|
|
|
#include <linux/mm.h>
|
2009-07-04 02:20:44 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#include <asm/mtrr.h>
|
|
|
|
#include <asm/msr.h>
|
2009-07-04 02:20:44 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
#include "mtrr.h"
|
|
|
|
|
|
|
|
static struct {
|
|
|
|
unsigned long high;
|
|
|
|
unsigned long low;
|
|
|
|
} centaur_mcr[8];
|
|
|
|
|
|
|
|
static u8 centaur_mcr_reserved;
|
|
|
|
static u8 centaur_mcr_type; /* 0 for winchip, 1 for winchip2 */
|
|
|
|
|
2009-07-04 02:20:44 +00:00
|
|
|
/**
|
|
|
|
* centaur_get_free_region - Get a free MTRR.
|
|
|
|
*
|
|
|
|
* @base: The starting (base) address of the region.
|
|
|
|
* @size: The size (in bytes) of the region.
|
|
|
|
*
|
|
|
|
* Returns: the index of the region on success, else -1 on error.
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
|
|
|
static int
|
[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-07 01:14:09 +00:00
|
|
|
centaur_get_free_region(unsigned long base, unsigned long size, int replace_reg)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
[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-07 01:14:09 +00:00
|
|
|
unsigned long lbase, lsize;
|
2009-07-04 02:20:44 +00:00
|
|
|
mtrr_type ltype;
|
|
|
|
int i, max;
|
2005-04-16 22:20:36 +00:00
|
|
|
|
|
|
|
max = num_var_ranges;
|
[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-07 01:14:09 +00:00
|
|
|
if (replace_reg >= 0 && replace_reg < max)
|
|
|
|
return replace_reg;
|
2009-07-04 02:20:44 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
for (i = 0; i < max; ++i) {
|
|
|
|
if (centaur_mcr_reserved & (1 << i))
|
|
|
|
continue;
|
|
|
|
mtrr_if->get(i, &lbase, &lsize, <ype);
|
|
|
|
if (lsize == 0)
|
|
|
|
return i;
|
|
|
|
}
|
2009-07-04 02:20:44 +00:00
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
return -ENOSPC;
|
|
|
|
}
|
|
|
|
|
2009-07-04 02:20:44 +00:00
|
|
|
/*
|
|
|
|
* Report boot time MCR setups
|
|
|
|
*/
|
|
|
|
void mtrr_centaur_report_mcr(int mcr, u32 lo, u32 hi)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
centaur_mcr[mcr].low = lo;
|
|
|
|
centaur_mcr[mcr].high = hi;
|
|
|
|
}
|
|
|
|
|
|
|
|
static void
|
|
|
|
centaur_get_mcr(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-07 01:14:09 +00:00
|
|
|
unsigned long *size, mtrr_type * type)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
*base = centaur_mcr[reg].high >> PAGE_SHIFT;
|
|
|
|
*size = -(centaur_mcr[reg].low & 0xfffff000) >> PAGE_SHIFT;
|
2009-07-04 02:20:44 +00:00
|
|
|
*type = MTRR_TYPE_WRCOMB; /* write-combining */
|
|
|
|
|
2005-04-16 22:20:36 +00:00
|
|
|
if (centaur_mcr_type == 1 && ((centaur_mcr[reg].low & 31) & 2))
|
|
|
|
*type = MTRR_TYPE_UNCACHABLE;
|
|
|
|
if (centaur_mcr_type == 1 && (centaur_mcr[reg].low & 31) == 25)
|
|
|
|
*type = MTRR_TYPE_WRBACK;
|
|
|
|
if (centaur_mcr_type == 0 && (centaur_mcr[reg].low & 31) == 31)
|
|
|
|
*type = MTRR_TYPE_WRBACK;
|
|
|
|
}
|
|
|
|
|
2009-07-04 02:20:44 +00:00
|
|
|
static void
|
|
|
|
centaur_set_mcr(unsigned int reg, unsigned long base,
|
|
|
|
unsigned long size, mtrr_type type)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
unsigned long low, high;
|
|
|
|
|
|
|
|
if (size == 0) {
|
2009-07-04 02:20:44 +00:00
|
|
|
/* Disable */
|
2005-04-16 22:20:36 +00:00
|
|
|
high = low = 0;
|
|
|
|
} else {
|
|
|
|
high = base << PAGE_SHIFT;
|
2009-07-04 02:20:44 +00:00
|
|
|
if (centaur_mcr_type == 0) {
|
|
|
|
/* Only support write-combining... */
|
|
|
|
low = -size << PAGE_SHIFT | 0x1f;
|
|
|
|
} else {
|
2005-04-16 22:20:36 +00:00
|
|
|
if (type == MTRR_TYPE_UNCACHABLE)
|
2009-07-04 02:20:44 +00:00
|
|
|
low = -size << PAGE_SHIFT | 0x02; /* NC */
|
2005-04-16 22:20:36 +00:00
|
|
|
else
|
2009-07-04 02:20:44 +00:00
|
|
|
low = -size << PAGE_SHIFT | 0x09; /* WWO, WC */
|
2005-04-16 22:20:36 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
centaur_mcr[reg].high = high;
|
|
|
|
centaur_mcr[reg].low = low;
|
|
|
|
wrmsr(MSR_IDT_MCR0 + reg, low, high);
|
|
|
|
}
|
|
|
|
|
2009-07-04 02:20:44 +00:00
|
|
|
static int
|
|
|
|
centaur_validate_add_page(unsigned long base, unsigned long size, unsigned int type)
|
2005-04-16 22:20:36 +00:00
|
|
|
{
|
|
|
|
/*
|
2009-07-04 02:20:44 +00:00
|
|
|
* FIXME: Winchip2 supports uncached
|
2005-04-16 22:20:36 +00:00
|
|
|
*/
|
2009-07-04 02:20:44 +00:00
|
|
|
if (type != MTRR_TYPE_WRCOMB &&
|
2005-04-16 22:20:36 +00:00
|
|
|
(centaur_mcr_type == 0 || type != MTRR_TYPE_UNCACHABLE)) {
|
2009-07-04 02:20:44 +00:00
|
|
|
pr_warning("mtrr: only write-combining%s supported\n",
|
|
|
|
centaur_mcr_type ? " and uncacheable are" : " is");
|
2005-04-16 22:20:36 +00:00
|
|
|
return -EINVAL;
|
|
|
|
}
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
2010-01-31 19:16:34 +00:00
|
|
|
static const struct mtrr_ops centaur_mtrr_ops = {
|
2005-04-16 22:20:36 +00:00
|
|
|
.vendor = X86_VENDOR_CENTAUR,
|
|
|
|
.set = centaur_set_mcr,
|
|
|
|
.get = centaur_get_mcr,
|
|
|
|
.get_free_region = centaur_get_free_region,
|
|
|
|
.validate_add_page = centaur_validate_add_page,
|
|
|
|
.have_wrcomb = positive_have_wrcomb,
|
|
|
|
};
|
|
|
|
|
|
|
|
int __init centaur_init_mtrr(void)
|
|
|
|
{
|
|
|
|
set_mtrr_ops(¢aur_mtrr_ops);
|
|
|
|
return 0;
|
|
|
|
}
|