[PATCH] x86-64: Calgary IOMMU: Fix off by one when calculating register space location
Jon Mason authored

The purpose of the code being modified is to determine the location
of the calgary chip address space.  This is done by a magical formula
of FE0MB-8MB*OneBasedChassisNumber+1MB*(RioNodeId-ChassisBase) to
find the offset where BIOS puts it.  In this formula,
OneBasedChassisNumber corresponds to the NUMA node, and rionodeid is
always 2 or 3 depending on which chip in the system it is.  The
problem was that we had an off by one error that caused us to account
some busses to the wrong chip and thus give them the wrong address
space.

Fixes RH bugzilla #203971.
Signed-off-by: default avatarJon Mason <jdmason@kudzu.us>
Signed-off-bu: Muli Ben-Yehuda <muli@il.ibm.com>
Signed-off-by: default avatarAndi Kleen <ak@suse.de>
76fd2317
Name Last commit Last update
..
alpha Remove all inclusions of <linux/config.h>
arm [PATCH] atmel_serial: Pass fixed register mappings through platform_data
arm26 Remove all inclusions of <linux/config.h>
avr32 [PATCH] AVR32: Allow renumbering of serial devices
cris more misc typo fixes
frv Remove all inclusions of <linux/config.h>
h8300 Remove all inclusions of <linux/config.h>
i386 [PATCH] i386: Update defconfig
ia64 [PATCH] msi: move the ia64 code into arch/ia64
m32r Remove all inclusions of <linux/config.h>
m68k Remove all inclusions of <linux/config.h>
m68knommu Remove all inclusions of <linux/config.h>
mips [MIPS] PNX8550 fixups
parisc [PA-RISC] Fix time.c for new do_timer() calling convention
powerpc [POWERPC] cell: fix bugs found by sparse
ppc Remove all inclusions of <linux/config.h>
s390 [S390] Remove open-coded mem_map usage.
sh fix file specification in comments
sh64 fix file specification in comments
sparc Remove all inclusions of <linux/config.h>
sparc64 Remove all inclusions of <linux/config.h>
um Remove all inclusions of <linux/config.h>
v850 Remove all inclusions of <linux/config.h>
x86_64 [PATCH] x86-64: Calgary IOMMU: Fix off by one when calculating register space location
xtensa fix file specification in comments