- 08 Sep, 2004 40 commits
-
-
Andries E. Brouwer authored
Signed-off-by:
Andrew Morton <akpm@osdl.org> Signed-off-by:
Linus Torvalds <torvalds@osdl.org>
-
Andries E. Brouwer authored
The routine afs_rxvl_probe() is unused and could be removed. (I only put #if 0 around it.) Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Ingo Molnar authored
Clean up the TSC-synchronization code: get rid of div64 and calm down the printks. Signed-off-by:
Ingo Molnar <mingo@elte.hu> Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Andries E. Brouwer authored
Signed-off-by:
-
Paul Fulghum authored
Uses msecs_to_jiffies() instead of the custom jiffies_from_ms(). Signed-off-by:
Nishanth Aravamudan <nacc@us.ibm.com> Signed-off-by:
-
Adrian Bunk authored
drivers/cdrom/cdu31a.c: In function `do_sony_cd_cmd': drivers/cdrom/cdu31a.c:962: parse error before `:' Signed-off-by:
Adrian Bunk <bunk@fs.tum.de> Signed-off-by:
-
Anton Blanchard authored
I noticed a large machine was doing about 400,000 context switches per second when oprofile was enabled. Upon closer inspection it looks like we were rearming the buffer sync timer without modifying the expire time. Now that we have schedule_delayed_work_on I believe we can remove the timer completely. Each cpu should be offset by 1 jiffy so they dont all fire at the same time. I bumped DEFAULT_TIMER_EXPIRE from 2 to 10 times a second to be sure we reap cpu buffers. With the following patch the same large machine gets about 4000 context switches per second. Signed-off-by:
Anton Blanchard <anton@samba.org> Signed-off-by:
-
Anton Blanchard authored
On error we can call __free_cpu_buffers with only some buffers allocated. I was getting a bunch of vfree warnings when I hit it, we should check before calling vfree. Signed-off-by:
-
Anton Blanchard authored
Replace open coded versions with for_each_cpu()/for_each_online_cpu(). Signed-off-by:
-
Adrian Bunk authored
drivers/char/riscom8.c:1178: macro `min_t' used with only 2 args Signed-off-by:
-
Badari Pulavarty authored
The problem here is, finished_one_bio() shouldn't call aio_complete() since no work has been done. I have a fix for this - can you verify this ? I am not really comfortable with this "tweaking". (I am not really sure about IO errors like EIO etc. - if they can lead to calling aio_complete() twice) Fix is to call aio_complete() ONLY if there is something to report. Note the we don't update dio->result with any error codes from get_user_pages(), they just passed as "ret" value from do_direct_IO(). Signed-off-by:
-
Thor Kooda authored
xtea_encrypt() should use XTEA_DELTA instead of TEA_DELTA. Signed-off-by:
Thor Kooda <tkooda-patch-kernel@devsec.org> Signed-off-by:
-
Dave Jones authored
This pointer is used prior to a test for NULL. But Bart says it can never be NULL. Signed-off-by:
Dave Jones <davej@redhat.com> Signed-off-by:
-
Dave Jones authored
Not that this driver compiles, but coverity picked up this nonsense. If the pci_alloc_consistent fails, we go boom. Amusingly, after the ==NULL check, is an identical memset. Signed-off-by:
-
Antonino Daplas authored
This adds module_init(xxxfb_init) in all drivers. For drivers with xxxfb_setup(), this patch also adds a 'xxxfb_setup(fb_get_options("xxxfb"))' prior to initialization. Signed-off-by:Antonino Daplas <adaplas@pol.net> Signed-off-by:
-
Antonino Daplas authored
This patch probably deserves discussion among developers. Currently, the framebuffer system is initialized in a roundabout manner. First, drivers/char/mem.c calls fbmem_init(). fbmem_init() will then iterate over an array of individual drivers' xxxfb_init(), then each driver registers its presence back to fbmem. During console_init(), drivers/char/vt.c will call fb_console_init(). fbcon will check for registered drivers, and if any are present, will call take_over_console() in drivers/char/vt.c. This patch changes the initialization sequence so it proceeds in this manner: Each driver has its own module_init(). Each driver calls register_framebuffer() in fbmem.c. fbmem.c will then notify fbcon of the driver registration. Upon notification, fbcon calls take_over_console() in vt.c. The following are the changes brought about by this patch: - Each subsystem (fbcon, fbmem, xxxfb) will have their own module_init. Thus, explicit calls to each subsystem's init functions are eliminated. - The struct fb_drivers array in fbmem.c can be removed. This slashes around 400 lines in fbmem.c - Parsing of kernel boot options were done by fbmem.c calling each driver's xxxfb_setup() function. Because this is not possible with this patch, drivers can choose to either: - have their own __setup() routine - call fb_get_options("xxxfb") and pass the return value to xxxfb_setup(). This is to maintain compatibility with the 'video=xxxfb:<options>' semantics. - Getting a framebuffer console will occur a bit late during the boot process since the initialization sequence will depend upon the link order. So, 'video/' is moved up in drivers/Makefile, shortly after 'pci/' - Because driver initialization will be dependent on the link order, hardware that depends on other subsystems (agpgart, usb, serial, etc) may choose to initialize after the subsystems they depend on. Signed-off-by: -
Antonino Daplas authored
- This fixes another regression from 2.4. If fbcon is compiled statically, and the framebuffer driver is compiled as a module, doing a 'modprobe xxxfb' does nothing to the console. This has generated numerous bug reports from users. With this patch, fbmem will notify fbcon upon driver registration allowing fbcon to take over the console. - This also fixes con2fbmap not working if fbcon is compiled as a module using the same mechanism as described above. Signed-off-by:
-
Antonino Daplas authored
- Fixed rivafb crashing in PPC. rivafb in PPC requires full, instead of partial, hardware initialization in rivafb_set_par(). - Added untested support for NV_ARCH_30 chipsets. - From Guido Guenther <agx@sigxcpu.org> here's another short patch fixing the cursor colors on big endian. - From Guido Guenther <agx@sigxcpu.org> trivial: strictmode is a MODULE_PARAM, even if CONFIG_MTRR is not set: Signed-off-by:Guido Guenther <agx@sigxcpu.org> Signed-off-by:
-
Antonino Daplas authored
This patch speeds up scrolling of tdfxfb by maximizing var->yres_virtual so tdfxfb uses SCROLL_PAN_MOVE instead of SCROLL_REDRAW. This is true whether CONFIG_FB_3DFX_ACCEL is set or not. This problem was reported by Paolo Ornati <ornati@fastwebnet.it> who also made substantial contributions to solve this problem. This patch also fixes compile errors when CONFIG_FB_3DFX_ACCEL is false. Signed-off-by:
-
Dave Jones authored
This looks awry. Move the dereference to after we have checked sb is non-NULL. Signed-off-by:
-
Tom Rini authored
The following patch switches arch/ppc/boot over from using its own version of zlib to the code found under lib/zlib_inflate. In conjunction with the previous two patches, the size of the resulting images isn't noticably different. But this does have the advantage of removing another copy of zlib from the kernel, and I believe this allows for lib/inflate.c to go away (as that's basically what ppc used to use). Signed-off-by:
Tom Rini <trini@kernel.crashing.org> Signed-off-by:
-
Tom Rini authored
The following changes zlib_inflate_trees_fixed(...) from using a statically defined table, to generating this table. This cuts out 4-8kB from inftrees.o (4kB on IBM 440GP, 8kB on PPC 74xx). Signed-off-by:
-
Tom Rini authored
The following patch moves zlib_inflateSync and friends, which are used by PPP and not a 'normal' gzip, into inflate_sync.c. Signed-off-by:
-
Martin Schwidefsky authored
From: Thomas Spatzier <tspat@de.ibm.com> lcs network driver changes: - Fix deadlock on card->ipm_lock. Signed-off-by:
Martin Schwidefsky <schwidefsky@de.ibm.com> Signed-off-by:
-
Martin Schwidefsky authored
The different stack frame layout for packed stacks broke cpu hotplug. Recreate the initial stack frame of the idle thread for offline cpus coming back online. Reenable interrupts after loading the initial registers. In addition this patch contains two more bug fixes: a typo for 64 bit (__SMALL_STACK_SIZE vs. __SMALL_STACK) and show_trace didn't show a trace if for task == NULL. Signed-off-by:
-
Martin Schwidefsky authored
Removes unnecessary min/max macros and changes calls to use kernel.h macros instead. Signed-off-by:
Michael Veeck <michael.veeck@gmx.net> Signed-off-by:
Maximilian Attems <janitor@sternwelten.at> Signed-off-by:
-
Bastian Blank authored
The attached patch exports __copy_in_user_asm for s390. It is used in xfs. Signed-off-by:
-
Andrew Morton authored
It has no callers. Signed-off-by:
-
Brian Gerst authored
This patch removes the default stubs for init_module and cleanup_module, and checks for NULL instead. It changes modpost to only create references to those functions if they actually exist. Signed-off-by:
-
Neil Brown authored
No need to set fl_owner and fl_pid to 0, since that's already been done by locks_init_lock. Signed-off-by:
Andy Adamson <andros@umich.edu> Signed-off-by:
J. Bruce Fields <bfields@citi.umich.edu> Signed-off-by:
Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by:
-
Neil Brown authored
The file_lock.fl_pid is no longer used in posix_same_owner() tests. So just set it to current->tgid for informational purposes. Signed-off-by:
-
Neil Brown authored
Postpone the release of a stateowner on CLOSE for lease time to enable the CLOSE replay cache. Place stateowner on the close_lru list to be reaped by the laundromat service. Signed-off-by:
-
Neil Brown authored
nfsd4 could leak a stateid in a case of kmalloc failure; fix. Signed-off-by:
-
Neil Brown authored
Whitespace cleanup, fix one dprintk, remove superfluous casts of NULL. Signed-off-by:
-
Neil Brown authored
The nfs4 attributes supported_attrs and aclsupport should not be static; they need to depend on the exported filesystem's acl support. Test the latter by attempting to get an acl, and adjust the returned attributes apropriately. Signed-off-by:
-
Neil Brown authored
fix incorrect indentation in fh_verify Signed-off-by:
-
Neil Brown authored
As 'nfs_acceptable' uses the authnetication user in it's checks, the filehandle might not be truely "stale" - EACCES is safer. Thanks Olaf Kirch <okir@suse.de> and others. Signed-off-by:
-
Neil Brown authored
If we would block, we return "err-jukebox" for nfsv3, or just drop the request for v2. Signed-off-by:
-
