2007-10-24 06:49:47 -04:00
|
|
|
#ifndef _ASM_X8664_IOMMU_H
|
|
|
|
#define _ASM_X8664_IOMMU_H 1
|
|
|
|
|
2008-05-20 10:27:17 -04:00
|
|
|
#include <asm/e820.h>
|
|
|
|
|
2007-10-24 06:49:47 -04:00
|
|
|
extern void pci_iommu_shutdown(void);
|
|
|
|
extern void no_iommu_init(void);
|
|
|
|
extern int force_iommu, no_iommu;
|
|
|
|
extern int iommu_detected;
|
2008-04-08 04:49:03 -04:00
|
|
|
extern int agp_amd64_init(void);
|
2007-10-24 06:49:48 -04:00
|
|
|
#ifdef CONFIG_GART_IOMMU
|
2007-10-24 06:49:47 -04:00
|
|
|
extern void gart_iommu_init(void);
|
|
|
|
extern void gart_iommu_shutdown(void);
|
|
|
|
extern void __init gart_parse_options(char *);
|
x86: disable the GART early, 64-bit
For K8 system: 4G RAM with memory hole remapping enabled, or more than
4G RAM installed.
when try to use kexec second kernel, and the first doesn't include
gart_shutdown. the second kernel could have different aper position than
the first kernel. and second kernel could use that hole as RAM that is
still used by GART set by the first kernel. esp. when try to kexec
2.6.24 with sparse mem enable from previous kernel (from RHEL 5 or SLES
10). the new kernel will use aper by GART (set by first kernel) for
vmemmap. and after new kernel setting one new GART. the position will be
real RAM. the _mapcount set is lost.
Bad page state in process 'swapper'
page:ffffe2000e600020 flags:0x0000000000000000 mapping:0000000000000000 mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Pid: 0, comm: swapper Not tainted 2.6.24-rc7-smp-gcdf71a10-dirty #13
Call Trace:
[<ffffffff8026401f>] bad_page+0x63/0x8d
[<ffffffff80264169>] __free_pages_ok+0x7c/0x2a5
[<ffffffff80ba75d1>] free_all_bootmem_core+0xd0/0x198
[<ffffffff80ba3a42>] numa_free_all_bootmem+0x3b/0x76
[<ffffffff80ba3461>] mem_init+0x3b/0x152
[<ffffffff80b959d3>] start_kernel+0x236/0x2c2
[<ffffffff80b9511a>] _sinittext+0x11a/0x121
and
[ffffe2000e600000-ffffe2000e7fffff] PMD ->ffff81001c200000 on node 0
phys addr is : 0x1c200000
RHEL 5.1 kernel -53 said:
PCI-DMA: aperture base @ 1c000000 size 65536 KB
new kernel said:
Mapping aperture over 65536 KB of RAM @ 3c000000
So could try to disable that GART if possible.
According to Ingo
> hm, i'm wondering, instead of modifying the GART, why dont we simply
> _detect_ whatever GART settings we have inherited, and propagate that
> into our e820 maps? I.e. if there's inconsistency, then punch that out
> from the memory maps and just dont use that memory.
>
> that way it would not matter whether the GART settings came from a [old
> or crashing] Linux kernel that has not called gart_iommu_shutdown(), or
> whether it's a BIOS that has set up an aperture hole inconsistent with
> the memory map it passed. (or the memory map we _think_ i tried to pass
> us)
>
> it would also be more robust to only read and do a memory map quirk
> based on that, than actively trying to change the GART so early in the
> bootup. Later on we have to re-enable the GART _anyway_ and have to
> punch a hole for it.
>
> and as a bonus, we would have shored up our defenses against crappy
> BIOSes as well.
add e820 modification for gart inconsistent setting.
gart_fix_e820=off could be used to disable e820 fix.
Signed-off-by: Yinghai Lu <yinghai.lu@sun.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 07:33:09 -05:00
|
|
|
extern void early_gart_iommu_check(void);
|
2007-10-24 06:49:50 -04:00
|
|
|
extern void gart_iommu_hole_init(void);
|
2007-10-24 06:49:47 -04:00
|
|
|
extern int fallback_aper_order;
|
|
|
|
extern int fallback_aper_force;
|
2007-10-24 06:49:50 -04:00
|
|
|
extern int gart_iommu_aperture;
|
|
|
|
extern int gart_iommu_aperture_allowed;
|
|
|
|
extern int gart_iommu_aperture_disabled;
|
2007-10-24 06:49:47 -04:00
|
|
|
extern int fix_aperture;
|
|
|
|
#else
|
2007-10-24 06:49:50 -04:00
|
|
|
#define gart_iommu_aperture 0
|
|
|
|
#define gart_iommu_aperture_allowed 0
|
2007-10-24 06:49:47 -04:00
|
|
|
|
x86: disable the GART early, 64-bit
For K8 system: 4G RAM with memory hole remapping enabled, or more than
4G RAM installed.
when try to use kexec second kernel, and the first doesn't include
gart_shutdown. the second kernel could have different aper position than
the first kernel. and second kernel could use that hole as RAM that is
still used by GART set by the first kernel. esp. when try to kexec
2.6.24 with sparse mem enable from previous kernel (from RHEL 5 or SLES
10). the new kernel will use aper by GART (set by first kernel) for
vmemmap. and after new kernel setting one new GART. the position will be
real RAM. the _mapcount set is lost.
Bad page state in process 'swapper'
page:ffffe2000e600020 flags:0x0000000000000000 mapping:0000000000000000 mapcount:1 count:0
Trying to fix it up, but a reboot is needed
Backtrace:
Pid: 0, comm: swapper Not tainted 2.6.24-rc7-smp-gcdf71a10-dirty #13
Call Trace:
[<ffffffff8026401f>] bad_page+0x63/0x8d
[<ffffffff80264169>] __free_pages_ok+0x7c/0x2a5
[<ffffffff80ba75d1>] free_all_bootmem_core+0xd0/0x198
[<ffffffff80ba3a42>] numa_free_all_bootmem+0x3b/0x76
[<ffffffff80ba3461>] mem_init+0x3b/0x152
[<ffffffff80b959d3>] start_kernel+0x236/0x2c2
[<ffffffff80b9511a>] _sinittext+0x11a/0x121
and
[ffffe2000e600000-ffffe2000e7fffff] PMD ->ffff81001c200000 on node 0
phys addr is : 0x1c200000
RHEL 5.1 kernel -53 said:
PCI-DMA: aperture base @ 1c000000 size 65536 KB
new kernel said:
Mapping aperture over 65536 KB of RAM @ 3c000000
So could try to disable that GART if possible.
According to Ingo
> hm, i'm wondering, instead of modifying the GART, why dont we simply
> _detect_ whatever GART settings we have inherited, and propagate that
> into our e820 maps? I.e. if there's inconsistency, then punch that out
> from the memory maps and just dont use that memory.
>
> that way it would not matter whether the GART settings came from a [old
> or crashing] Linux kernel that has not called gart_iommu_shutdown(), or
> whether it's a BIOS that has set up an aperture hole inconsistent with
> the memory map it passed. (or the memory map we _think_ i tried to pass
> us)
>
> it would also be more robust to only read and do a memory map quirk
> based on that, than actively trying to change the GART so early in the
> bootup. Later on we have to re-enable the GART _anyway_ and have to
> punch a hole for it.
>
> and as a bonus, we would have shored up our defenses against crappy
> BIOSes as well.
add e820 modification for gart inconsistent setting.
gart_fix_e820=off could be used to disable e820 fix.
Signed-off-by: Yinghai Lu <yinghai.lu@sun.com>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
2008-01-30 07:33:09 -05:00
|
|
|
static inline void early_gart_iommu_check(void)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
2007-10-24 06:49:47 -04:00
|
|
|
static inline void gart_iommu_shutdown(void)
|
|
|
|
{
|
|
|
|
}
|
|
|
|
|
|
|
|
#endif
|
|
|
|
|
2008-04-08 04:49:03 -04:00
|
|
|
/* PTE bits. */
|
|
|
|
#define GPTE_VALID 1
|
|
|
|
#define GPTE_COHERENT 2
|
|
|
|
|
|
|
|
/* Aperture control register bits. */
|
|
|
|
#define GARTEN (1<<0)
|
|
|
|
#define DISGARTCPU (1<<4)
|
|
|
|
#define DISGARTIO (1<<5)
|
|
|
|
|
|
|
|
/* GART cache control register bits. */
|
|
|
|
#define INVGART (1<<0)
|
|
|
|
#define GARTPTEERR (1<<1)
|
|
|
|
|
|
|
|
/* K8 On-cpu GART registers */
|
|
|
|
#define AMD64_GARTAPERTURECTL 0x90
|
|
|
|
#define AMD64_GARTAPERTUREBASE 0x94
|
|
|
|
#define AMD64_GARTTABLEBASE 0x98
|
|
|
|
#define AMD64_GARTCACHECTL 0x9c
|
|
|
|
#define AMD64_GARTEN (1<<0)
|
|
|
|
|
2008-04-15 06:43:57 -04:00
|
|
|
static inline void enable_gart_translation(struct pci_dev *dev, u64 addr)
|
|
|
|
{
|
|
|
|
u32 tmp, ctl;
|
|
|
|
|
|
|
|
/* address of the mappings table */
|
|
|
|
addr >>= 12;
|
|
|
|
tmp = (u32) addr<<4;
|
|
|
|
tmp &= ~0xf;
|
|
|
|
pci_write_config_dword(dev, AMD64_GARTTABLEBASE, tmp);
|
|
|
|
|
|
|
|
/* Enable GART translation for this hammer. */
|
|
|
|
pci_read_config_dword(dev, AMD64_GARTAPERTURECTL, &ctl);
|
|
|
|
ctl |= GARTEN;
|
|
|
|
ctl &= ~(DISGARTCPU | DISGARTIO);
|
|
|
|
pci_write_config_dword(dev, AMD64_GARTAPERTURECTL, ctl);
|
|
|
|
}
|
|
|
|
|
2008-05-20 10:27:17 -04:00
|
|
|
static inline int aperture_valid(u64 aper_base, u32 aper_size, u32 min_size)
|
|
|
|
{
|
|
|
|
if (!aper_base)
|
|
|
|
return 0;
|
|
|
|
|
|
|
|
if (aper_base + aper_size > 0x100000000ULL) {
|
|
|
|
printk(KERN_ERR "Aperture beyond 4GB. Ignoring.\n");
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
if (e820_any_mapped(aper_base, aper_base + aper_size, E820_RAM)) {
|
|
|
|
printk(KERN_ERR "Aperture pointing to e820 RAM. Ignoring.\n");
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
if (aper_size < min_size) {
|
|
|
|
printk(KERN_ERR "Aperture too small (%d MB) than (%d MB)\n",
|
|
|
|
aper_size>>20, min_size>>20);
|
|
|
|
return 0;
|
|
|
|
}
|
|
|
|
|
|
|
|
return 1;
|
|
|
|
}
|
|
|
|
|
2007-10-24 06:49:47 -04:00
|
|
|
#endif
|