30 Aug, 2005
38 commits
-
This patch fixes a rare memory leak found by Coverity.
Signed-off-by: Joel Schopp
Signed-off-by: Paul Mackerras -
Coverity found more unused code.
Signed-off-by: Joel Schopp
Signed-off-by: Paul Mackerras -
While ppc64 has the CONFIG_HZ Kconfig option, it wasnt actually being
used. Connect it up and set all platforms to 250Hz.Signed-off-by: Anton Blanchard
Signed-off-by: Paul Mackerras -
Here's the 970MP's PVR (processor version register) entry for oprofile.
Signed-off-by: Jake Moilanen
Signed-off-by: Paul Mackerras -
Some RS64-based machines (p620, F80, others) have problems with firmware
returning 0xdeadbeef instead of failure to allocations that end at the
1GB mark.We have two options:
1. Detect the undocumented 0xdeadbeef return value and interpret it as
a failure.
2. Avoid allocating that high.(2) is really the cleaner solution here. 768MB is plenty of room so use
that as the max alloc_top instead of 1GB.Signed-off-by: Olof Johansson
Signed-off-by: Paul Mackerras -
They differed in either simple comments or in the protecting ifdefs.
Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
Move the identical files from include/asm-ppc{,64}/ to
include/asm-powerpc/. Remove hdreg.h completely as it is unused in
the tree.Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
The ppc and ppc64 trees are hopefully going to merge over time, so this
patch begins the process by creating a place for the merging of the
header files.Create include/asm-powerpc (and move linkage.h into it from
asm-{ppc,ppc64} since we don't like empty directories). Modify the
ppc and ppc64 Makefiles to cope.Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
Make MODULE_DEVICE_TABLE work for vio devices.
Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
Create vio_bus_ops so that we just pass a structure to vio_bus_init
instead of three separate function pointers.Rearrange vio.h to avoid forward references. vio.h only needs
struct device_node from prom.h so remove the include and just
declare it.Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
Take some assignments out of vio_register_device_common and
rename it to vio_register_device.Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
Formatting changes to vio.c to bring it closer to the
kernel coding standard.Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
gcc 3.4 (at least the build we are using) puts the gcc generated .ident
string into a .note section at the end of the files it compiles (gcc
3.3.3-hammer and gcc 4.0.2 Debian puts it in the .text section). This
means that the lparmap.s file we produce in the iSeries build may end with
a .note section. When we include it into head.S, the assembler can no
longer resolve some of the conditional branches since the target label
ends up too far away. This patch just forces us back to the .text section
after including lparmap.s.The breakage was caused by my patch "iSeries build with newer assemblers
and compilers" (sha1-id: 2ad56496627630ebc99f06af5f81ca23e17e014e).Signed-off-by: Stephen Rothwell
Signed-off-by: Paul Mackerras -
A mistake rebasing the series of ppc64 head.S cleanup patches meant
the #include of lparmap.s, needed for iSeries was lost. This patch
puts it back again.Signed-off-by: David Gibson
Signed-off-by: Paul Mackerras -
With CONFIG_HUGETLB_PAGE=n:
In file included from kernel/sysctl.c:37:
include/linux/hugetlb.h:104:1: warning: "hugetlb_free_pgd_range" redefined
In file included from include/linux/mm.h:36,
from kernel/sysctl.c:23:
include/asm/pgtable.h:492:1: warning: this is the location of the previous definitionSigned-off-by: Andrew Morton
Signed-off-by: David Gibson
Signed-off-by: Paul Mackerras -
It appears that a memory barrier soon after a mispredicted
branch, not just in the delay slot, can cause the hang
condition of this cpu errata.So move them out-of-line, and explicitly put them into
a "branch always, predict taken" delay slot which should
fully kill this problem.Signed-off-by: David S. Miller
-
When the spinlock routines were moved out of line into
kernel/spinlock.c this made it so that the debugging
spinlocks record lock acquisition program counts in the
kernel/spinlock.c functions not in their callers.
This makes the debugging info kind of useless.So record the correct caller's program counter and
now this feature is useful once more.Signed-off-by: David S. Miller
-
Removed sparc architecture specific users of asm/segment.h and
asm-sparc/segment.h itselfSigned-off-by: Kumar Gala
Signed-off-by: David S. Miller -
Removed sparc64 architecture specific users of asm/segment.h and
asm-sparc64/segment.h itselfSigned-off-by: Kumar Gala
Signed-off-by: David S. Miller -
Current uncorrectable error handling was poor enough
that the processor could just loop taking the same
trap over and over again. Fix things up so that we
at least get a log message and perhaps even some register
state.In the process, much consolidation became possible,
particularly with the correctable error handler.Prefix assembler and C function names with "spitfire"
to indicate that these are for Ultra-I/II/IIi/IIe only.More work is needed to make these routines robust and
featureful to the level of the Ultra-III error handlers.Signed-off-by: David S. Miller
-
Verify we really are taking a data access exception trap, at TL1, from
one of the window spill/fill handlers.Else call a new function, data_access_exception_tl1, to log the error.
Signed-off-by: David S. Miller
-
1) Read ASI_IMMU SFSR not ASI_DMMU.
2) IMMU has no SFAR, read TPC instead
3) Delete old and incorrect comment about the DTLB protection
trap having a dependency on the SFSR contents in order to
function correctlySigned-off-by: David S. Miller
-
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
* ieee1394_device_id has kernel_ulong_t field after an odd number of
__u32 ones. Since mod_devicetable.h is included both from kernel and
from host build helper, we may be in trouble if we are building on
32bit host for 64bit target - userland sees unsigned long long,
kernel sees unsigned long and while their sizes match, alignments
might not. Fixed by forcing alignment. Fortunately, almost nobody
else needs that - the rest of such fields is naturally aligned as it
is.* of_device_id has void * in it. Host userland helpers need
kernel_ulong_t instead, since their void * might have nothing to do
with the kernel one. Fixed in the same way it's done for similar
problems in pcmcia_device_id (ifdef __KERNEL__).* pcmcia_device_id has the same problem as ieee1394_device_id. Fixed
the same way.Signed-off-by: Al Viro
Signed-off-by: Linus Torvalds -
We've had Woozy Numbat for a while now. Here's an updated name care of
Jeff Garzik and myself.Signed-off-by: Benjamin LaHaise
Signed-off-by: Linus Torvalds -
It has been reported that the way Linux handles NODEFER for signals is
not consistent with the way other Unix boxes handle it. I've written a
program to test the behavior of how this flag affects signals and had
several reports from people who ran this on various Unix boxes,
confirming that Linux seems to be unique on the way this is handled.The way NODEFER affects signals on other Unix boxes is as follows:
1) If NODEFER is set, other signals in sa_mask are still blocked.
2) If NODEFER is set and the signal is in sa_mask, then the signal is
still blocked. (Note: this is the behavior of all tested but Linux _and_
NetBSD 2.0 *).The way NODEFER affects signals on Linux:
1) If NODEFER is set, other signals are _not_ blocked regardless of
sa_mask (Even NetBSD doesn't do this).2) If NODEFER is set and the signal is in sa_mask, then the signal being
handled is not blocked.The patch converts signal handling in all current Linux architectures to
the way most Unix boxes work.Unix boxes that were tested: DU4, AIX 5.2, Irix 6.5, NetBSD 2.0, SFU
3.5 on WinXP, AIX 5.3, Mac OSX, and of course Linux 2.6.13-rcX.* NetBSD was the only other Unix to behave like Linux on point #2. The
main concern was brought up by point #1 which even NetBSD isn't like
Linux. So with this patch, we leave NetBSD as the lonely one that
behaves differently here with #2.Signed-off-by: Linus Torvalds
29 Aug, 2005
2 commits
-
Paulus, I think this is now a reasonable candidate for the post-2.6.13
queue.Relax address restrictions for hugepages on ppc64
Presently, 64-bit applications on ppc64 may only use hugepages in the
address region from 1-1.5T. Furthermore, if hugepages are enabled in
the kernel config, they may only use hugepages and never normal pages
in this area. This patch relaxes this restriction, allowing any
address to be used with hugepages, but with a 1TB granularity. That
is if you map a hugepage anywhere in the region 1TB-2TB, that entire
area will be reserved exclusively for hugepages for the remainder of
the process's lifetime. This works analagously to hugepages in 32-bit
applications, where hugepages can be mapped anywhere, but with 256MB
(mmu segment) granularity.This patch applies on top of the four level pagetable patch
(http://patchwork.ozlabs.org/linuxppc64/patch?id=1936).Signed-off-by: David Gibson
Signed-off-by: Paul Mackerras -
You can't call get_property() on a NULL node, so check if of_chosen is set
in check_for_initrd().Signed-off-by: Michael Ellerman
arch/ppc64/kernel/setup.c | 20 ++++++++++++--------
1 files changed, 12 insertions(+), 8 deletions(-)
Signed-off-by: Paul Mackerras
