- 02 Jul, 2004 24 commits
-
-
Martin Schwidefsky authored
From: Utz Bacher <utz.bacher@de.ibm.com> From: Cornelia Huck <cohuck@de.ibm.com> Common i/o layer changes: - Consolidate store channel subsystem characteristics from its three users (css, cmf and qdio) to a single location. - Always use new stipd format and move creation of global path group to channel subsystem init function. Add dummy init_IRQ to setup.c and remove requestirq.c. - Remove bogus CHPID_LONGS define. - Add more magic to catch chpids coming online again without generating machine checks. - Fix check for unsolicited interrupts. Deferred cc=1 indicates a solicited interrupt. - Fix progress indication in qdio summary bytes to avoid loosing interrupts. - Rename console_device to console_devno to avoid naming conflict. Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Martin Schwidefsky authored
From: Arnd Bergmann <arndb@de.ibm.com> From: Christian Bornträger <cborntra@de.ibm.com> From: Michael Holzheu <holzheu@de.ibm.com> From: Martin Schwidefsky <schwidefsky@de.ibm.com> s390 core changes: - Fix cpu_idle loop if /proc/sys/kernel/hz_timer is set. - Store correct trap indication on 64 bit for call to do_debugger_trap in the single stepped svc code. - Avoid the use of alloca in the debug feature. - Remove extraneous includes of linux/version.h. - Regenerate default configuration. - Mention eServer z890 in Kconfig help text. - Prevent gcc 3.4 from removing statically defined per cpu variables. Signed-off-by:
-
Martin Schwidefsky authored
The radix tree functions __lookup and __lookup_tag uses (1 << shift) in their index calculations. On 64 bit systems the shift can be bigger than 32. The shift of an integer by more than 32 bits evaluates to zero which causes the lookup to fail. Signed-off-by:
-
Eric Lammerts authored
The init function is writing somewhere using a physical address instead of a virtual address. Signed-off-by:
-
Natalie Protasevich authored
This is ES7000 sub arch update. The tiny patch below fixes a bug that results in boot problem on all ES7000 partitions with numbers higher than 0. Currently, target_cpus() returns incorrect cpumask value since it indexes bits by the logical APIC ID, not by CPU number. The patch affects only ES7000 sub arch. It was tested extensively on the system with multiple partitions. Signed-off-by:
-
Bjorn Helgaas authored
Include <asm/io.h> for ioremap() declaration. Signed-off-by:
Bjorn Helgaas <bjorn.helgaas@hp.com> Signed-off-by:
-
Antonino Daplas authored
- Update display->vrows when fbset changes certain fields in var (such as color depth) but without changing the display resolution. This might produce concommitant changes in other fields such as and especially var->yres_virtual. - Clear the FBINFO_MISC_MODECHANGEUSER flag _before_ issuing a notifier_call_chain(). Clearing it after the notifier_call_chain() will cause fbcon to go into an infinite loop. - Sanitized failure path of set_con2fb_map(). Signed-off-by:
Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
As we've discussed in another thread, below is a diff that will do a set_par() as late as possible when there is KD_TEXT<->KD_GRAPHICS switch. The set_par() will be forced in fbcon_resize() instead. Not sure if this has repercussions with the other drivers, but this patch fixed the X nv driver hanging when switching to the console. (I believe the crash is actually caused by an early set_par() -- while in fbcon_blank. Removing the set_par in fbcon_blank fixed the hang but caused cursor sprite and display corruption). Signed-off-by:
-
Antonino Daplas authored
The patch below fixes the following to rivafb: 1 Seems that nVidia hardware has a limit on clipping coordinates that is also dependent on the color depth of the framebuffer. 2.From Pawel Goleniowski <pawelg@dabrowa.pl>: Fix for wrong colors at 16bpp (RGB565). The fix has been submitted several times in lkml and this list but was never applied. 3 Search all I2C/DDC busses for the EDID block instead of just the first bus. 4 Updated request_mem_region/release_mem_region to pci_request_regions/pci_release_regions. Signed-off-by:
-
Randy Dunlap authored
Convert private ABS() defines and callers to use abs() from linux/kernel.h. Builds successfully. stv0299, riva, & sstfb modules load. Signed-off-by:
Randy Dunlap <rddunlap@osdl.org> Signed-off-by:
-
Mika Kukkonen authored
CHECK drivers/pnp/pnpbios/core.c include/linux/pnpbios.h:144:5: warning: undefined preprocessor identifier 'needed' CC drivers/pnp/pnpbios/core.o CHECK drivers/pnp/pnpbios/bioscalls.c include/linux/pnpbios.h:144:5: warning: undefined preprocessor identifier 'needed' drivers/pnp/pnpbios/bioscalls.c:346:5: warning: undefined preprocessor identifier 'needed' drivers/pnp/pnpbios/bioscalls.c:361:5: warning: undefined preprocessor identifier 'needed' drivers/pnp/pnpbios/bioscalls.c:388:5: warning: undefined preprocessor identifier 'needed' drivers/pnp/pnpbios/bioscalls.c:427:5: warning: undefined preprocessor identifier 'needed' drivers/pnp/pnpbios/bioscalls.c:509:5: warning: undefined preprocessor identifier 'needed' CC drivers/pnp/pnpbios/bioscalls.o CHECK drivers/pnp/pnpbios/rsparser.c include/linux/pnpbios.h:144:5: warning: undefined preprocessor identifier 'needed' CC drivers/pnp/pnpbios/rsparser.o CHECK drivers/pnp/pnpbios/proc.c include/linux/pnpbios.h:144:5: warning: undefined preprocessor identifier 'needed' The fix is trivial, sparse wants the preprocessor symbol to be defined before use. There was a similar fix accepted by Linus couple weeks ago. Patch attached. Signed-off-by:
-
Mika Kukkonen authored
CHECK kernel/power/swsusp.c kernel/power/swsusp.c:320:15: warning: expected lvalue for member dereference kernel/power/swsusp.c:337:15: warning: expected lvalue for member dereference kernel/power/swsusp.c:359:14: warning: expected lvalue for member dereference kernel/power/swsusp.c:925:12: warning: assignment expression in conditional [...] CHECK kernel/power/pmdisk.c kernel/power/pmdisk.c:795:12: warning: assignment expression in conditional Trivial sparse fixes for two files under kernel/power. Patch attached. Signed-off-by:
-
Mika Kukkonen authored
CHECK kernel/kallsyms.c kernel/kallsyms.c:136:7: warning: bad constant expression kernel/kallsyms.c:136:7: warning: bad constant expression kernel/kallsyms.c:136:7: warning: bad constant expression kernel/kallsyms.c:143:22: warning: bad constant expression kernel/kallsyms.c:143:22: warning: bad constant expression kernel/kallsyms.c:143:22: warning: bad constant expression Now the cause of sparse warnings is that it does not handle runtime array dimensioning (which I take it is a sparse problem), but in this particular case it _might_ make sense to change the runtime allocation to compile time, as the upper size of the array is known, because the code in kernel/kallsyms.c clearly uses 127 (or 128) as "magic constant" for kernel symbol (array) length, and in the other hand in include/linux/module.h there is: #define MODULE_NAME_LEN (64 - sizeof(unsigned long)) The only concern is that the array become quite big (the original comment of it being "pretty small" no longer applies ...). One way to help that would be to use buffer[] also in place of namebuf[], but that would be little tricky as the format string should be before the symbol name ... Signed-off-by:
-
George Anzinger authored
As required by the standard, this patch adds to POSIX ABSOLUTE timers the functionality of adjusting the timer when the clock is set so that it still expires at the specified time (provided that time has not passed, in which case the timer expires immeadiatly). The standard is, IMNSOHO, a bit vague on just how repeating timers are to be handled so I made some choices: 1) If an absolute timer is to expire every N intervals, we assume that the expiries should happen at those specified times after clock setting. I.e. we adjust the repeat timer as well as the initial timer. (The other option would be to treat the repeating timers as relative and not to adjust them.) 2) If a clock set moves the the clock prior to the initial expiry time AND that time has already passed and been signaled, the current repeat timer is adjusted, i.e. we DO NOT go back to the initial time and repeat that. (The other option is to treat this case as a new request with the initial timer parameters (which by this time we have lost).) 3) If time is advanced such that it appears that several expiries have been missed, the overrun count will reflect the misses. (The other option is to not reflect this in the overrun.) At the same time, nothing is done to acknowledge, to the user, that we are repeating expiries when the clock is retarded. Signed-off-by:George Anzinger <george@mvista.com> Signed-off-by:
-
Arjan van de Ven authored
The patch below uses the new-in-gcc-3.4 option to generate a warning on unchecked results of marked functions, and applies this to the inode_setattr function (which based on recent bk commits HAS to be checked for it's return value for correct operation). A warning looks like this: fs/ext2/inode.c:1279: warning: ignoring return value of 'inode_setattr', declared with attribute warn_unused_result Signed-off-by:
-
Pavel Machek authored
It fixes levels for calling driver model, puts devices into sleep before powering down (so that emergency parking does not happen), and actually introduces SMP support, but its disabled for now. Plus noone should try to freeze_processes() when thats not implemented, we now BUG()s -- we do not want Heisenbugs. Signed-off-by:
-
Matt Porter authored
Fixes a case where we were not correctly acking the base cascade controller on PPC4xx. Patch from Pavel Bartusek <pba@sysgo.com> Signed-off-by:
Matt Porter <mporter@kernel.crashing.org> Signed-off-by:
-
Matt Porter authored
PPC4xx preempt fixes. Based on previous Classic PPC patch. Signed-off-by:
Tom Rini <trini@kernel.crashing.org> Signed-off-by:
-
Matt Porter authored
Update PPC44x defconfigs and some fixes. Signed-off-by:
-
Tom Rini authored
Attached is the latest version of Adrian Cox's OCP patch for MPC107/8240/8245. This unifies some openpic setup code, and ensures that the OCP devices are only added to the bus on chip variants which have them. All interested parties seem happy, and this patch is necessary to provide a unified I2C driver for 85xx and 107/824x. Signed-off-by:
Adrian Cox <adrian@humboldt.co.uk> Signed-off-by:
-
Paul Mackerras authored
Recently I changed the return value of rtas_call() from an unsigned long to an int. That patch missed a few places where we declare a variable to store the result from rtas_call(). This new patch changes those places to use an int variable instead of a long or unsigned long variable. Linas Vepstas pointed this out. Signed-off-by:
Paul Mackerras <paulus@samba.org> Signed-off-by:
-
Paul Mackerras authored
This patch from Linas Vepstas (rediffed by me) fixes the confusing argument aliasing of the log_rtas_error() subroutine. This patch makes no functional changes, it just cleans up some strange usage. The rtas_args used to communicate with firmware are always taken from the paca struct, so as to keep the args at a fixed, low-memory location. But the log_rtas_error() routine also took an rtas_args pointer, which it assumed was aliased to the paca struct. This aliasing is both un-neccessary, and confusing; this patch eliminates this confusion. Signed-off-by:
Linas Vepstas <linas@linas.org> Signed-off-by:
-
David Gibson authored
Cleanup the PPC64 PACA structure. It was previously a big mess of unecessary fields, overengineered cache layout and uninformative comments. This is essentially a rewrite of include/asm-pp64/paca.h with associated changes elsewhere. The patch: - Removes unused PACA fields - Removes uneeded #includes - Uses gcc attributes instead of explicit padding to get the desired cacheline layout, also rethinks the layout and comments accordingly. - Better comments where asm or firmware dependencies apply non-obvious layout constraints. - Splits up the pointless STAB structure, letting us move its elements independently. - Uses offsetof instead of hardcoded offset in spinlocks. - Eradicates xStudlyCaps identifiers - Replaces PACA guard page with an explicitly defined emergency stack (removing more than NR_CPUS pages from the initialized data segment). Cc: Paul Mackerras <paulus@samba.org> Signed-off-by:
-
David Gibson authored
This patch removes the RTAS arguments structure on ppc64 from the PACA. The args have to be in the RMO, but since we have a global spinlock for RTAS anyway, there's no reason to have a separate copy of the args per-CPU. This patch replaces the PACA field with a single instance in the global rtas structure. The one exception is for the rtas_stop_self() call, which can't take the lock, because it never returns. But it has a fixed set of arguments, so we can use another global instance which is initialized at boot. This lets us remove rtas.h from paca.h, which substantially reduces overall #include hairiness (because paca.h is now, as it wants to be, a nice low-level structure-defining header which relies on very little and can safely be included almost anywhere). Although it does add some noise to the patch, because a bunch of places relied on the indirect inclusion of rtas.h, or even more indirect inclusions (see the hunks applying to eeh.h and current.h!). Cc: Paul Mackerras <paulus@samba.org> Signed-off-by:
-
- 01 Jul, 2004 12 commits
-
-
Matt Domsch authored
On Wed, Jun 30, 2004 at 01:22:21AM -0400, Jeff Garzik wrote: > CC arch/x86_64/kernel/setup.o > arch/x86_64/kernel/setup.c: In function `copy_edd': > arch/x86_64/kernel/setup.c:415: error: `EDD_MBR_SIGNATURE' undeclared=20 > (first use in this function) > arch/x86_64/kernel/setup.c:415: error: (Each undeclared identifier is=20 > reported only once > arch/x86_64/kernel/setup.c:415: error: for each function it appears in.) > arch/x86_64/kernel/setup.c:417: error: `EDD_MBR_SIG_NR' undeclared=20 > (first use in this function) > make[1]: *** [arch/x86_64/kernel/setup.o] Error 1 > make: *** [arch/x86_64/kernel] Error 2 Arrgh. On i386 it's in include/asm-i386/setup.h On x86_64 it belongs in include/asm-x86_64/bootsetup.h. Patch below defines EDD_MBR_SIG_NR and EDD_MBR_SIGNATURE on x86_64. Signed-off-by:Matt_Domsch <Matt_Domsch@dell.com>
-
David S. Miller authored
into kernel.bkbits.net:/home/davem/net-2.6
-
Stephen Hemminger authored
Current 2.6.7 tree acts as if it is alway under memory pressure because a recent change did a s/tcp_memory_pressure/tcp_prot.memory_pressure/. The problem is tcp_prot.memory_pressure is a pointer, so it is always non-zero! Rather than using *tcp_prot.memory_pressure, just go back to looking at tcp_memory_pressure. Signed-off-by:
Stephen Hemminger <shemminger@osdl.org> Signed-off-by:
David S. Miller <davem@redhat.com>
-
Kevin Corry authored
Remove the limitation of 1024 DM devices. Signed-off-by:
Kevin Corry <kevcorry@us.ibm.com> Signed-off-by:
-
Kevin Corry authored
dm-raid1.c: Declare fixed-sized (instead of variable-sized) arrays on the stack in recover() and do_write(). Signed-off-by:
-
Kevin Corry authored
dm-raid1.c: Since kcopyd can currently only handle 1 source and up to 8 destinations, enforce a max of 9 mirrors when creating a dm-mirror device. Signed-off-by:
-
Kevin Corry authored
kcopyd.c: client_add() can return void instead of an int, which will eliminate an unnecessary error path in kcopyd_client_create(). Signed-off-by:
-
Kevin Corry authored
kcopyd.c: Remove unused #include. Signed-off-by:
-
Mika Kukkonen authored
-
Andrea Arcangeli authored
'strace' shows a problem with a missing release_task for self-reaping clones that have been traced. We need to defer releasing them until the tracer is done with them, but if the tracer dies, we need to handle that case gracefully too. We do that by having 'forget_original_parent()' generate a list of tasks to release when this case happens. Patch based on discussions on linux-kernel, and suggestions from Roland McGrath <roland@redhat.com>.
-
Peter Osterlund authored
Opening a CDROM device for writing no longer works, because cdrom_open() returns -EROFS even if cdrom_open_write() succeeds. This fixes it. Signed-off-by:
Peter Osterlund <petero2@telia.com> Signed-off-by:
-
Ingo Molnar authored
This fixes a corner-case NX bug: the x86 SMP kernel doesnt boot on SMP Opterons if NX is enabled [and mem=nopentium is specified], due to kernel-space NX protection preventing the SMP trampoline from being executable. Since the SMP trampoline is a rare case of 'dynamic code' executed by the kernel (it has to be below 640K so it cannot be part of the kernel text itself), i've added the necessary infrastructure to enable/disable executability of specific kernel pages. We cannot simply disable NX via the MSR because we've got the NX bits in the kernel pagetables, which are set up before we do the SMP bootup. The NX bit in the pagetables is undefined if EFER.NXE is 0, so we cannot count on NX-capable CPUs not faulting when they encounter them. I've tested the x86 kernel on a non-NX SMP x86 box and on an NX UP box, on which i've also tested a simulated SMP trampoline, it all works fine. - add infrastructure to enable/disable executability of kernel pages - make the SMP trampoline page executable. Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
- 30 Jun, 2004 4 commits
-
-
bk://gkernel.bkbits.net/net-drivers-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Jeff Garzik authored
-
Stephen Hemminger authored
Cleanup the SK Fddi driver a little more. Mark some functions as static, and eliminate (or comment out) some that are defined but never used. Signed-off-by: -
Stephen Hemminger authored
The conversion to ANSI, caused a warning because the mulitcast code needs a cast. dmi->dmi_addr is a u8 array, and fddi_addr is just a wrapper around a u8 array. Signed-off-by:
-
