- 07 Jul, 2003 12 commits
-
-
Pavel Machek authored
This allows suspend to work on UP machines, even if the kernel is compiled for SMP.
-
Ian Molton authored
-
Bruno Ducrot authored
Due to a typo in powernow-k7.c, the value which correspond to the CPU core multiplicator and the VID value are swapped when we go down to up in frequency step.
-
Paul Mackerras authored
This adds a declaration that the macserial driver needs in order to compile correctly, and removes some old SERIAL_DO_RESTART junk which isn't used (SERIAL_DO_RESTART is never defined in this driver) and which I think is incorrect anyway, since it looks to me like it would potentially return an ERESTARTSYS error without a signal pending.
-
Rusty Russell authored
switch_mm and enter_lazy_tlb take a CPU arg, which is always smp_processor_id(). This is misleading, and pointless if they use per-cpu variables or other optimizations. gcc will eliminate redundant smp_processor_id() (in inline functions) anyway. This removes that arg from all the architectures.
-
Rusty Russell authored
kstat_this_cpu() is defined in terms of per_cpu instead of __get_cpu_var. This patch changes that, and uses it everywhere appropriate. The sched.c change puts it in a local variable, which helps gcc generate better code.
-
Greg Ungerer authored
No longer need the 68360 specific trap init call. The generic interrupt/trap code is now setup to do this itself.
-
Greg Ungerer authored
Define the raw read and write access macros for m68knommu. These rae use by MTD drivers in particular.
-
Greg Ungerer authored
Clean up show_process_blocks() loop for non-mmu targets.
-
Greg Ungerer authored
This patch includes the last peices of the flat laoder shared library support. Define the shared lib limit and implement a flag for doing kernel level tracing.
-
Greg Ungerer authored
A couple of minor fixes for the 68328 interrupt setup code. - don't define the .romvec section for DragonEngine build - print newline at end of spurious interrupt count in show_interrupts()
-
Ingo Molnar authored
doh - double unlock in the acct-is-on path. Noticed by Aneesh Kumar K.V <aneesh.kumar@digital.com>
-
- 06 Jul, 2003 28 commits
-
-
bk://cifs.bkbits.net/linux-2.5cifsLinus Torvalds authored
into home.osdl.org:/home/torvalds/v2.5/linux
-
Steve French authored
-
Greg Ungerer authored
Conditionally copy the ROMfs filesystem on the Cleopatra/5307 target board only if using a ROMfs.
-
Andrew Morton authored
From: Ingo Molnar <mingo@elte.hu> Most distributions turn on process accounting - but even the common 'accounting is off' case is horrible SMP-scalability-wise: it accesses a global spinlock during every sys_exit() call, which bounces like mad on SMP (and NUMA) systems. (i also got rid of the unused return code.)
-
Andrew Morton authored
From: "lode leroy" <lode_leroy@hotmail.com> I would like to submit a trivial enhancement to display the ip address of the bootserver in /proc/net/pnp This aids me in developing a diskless linux root image to know where it comes from...
-
Andrew Morton authored
From: Jan Kara <jack@suse.cz> This implements autoloading of quota modules.
-
Andrew Morton authored
From: Andreas Gruenbacher <agruen@suse.de> This patch removes the dependency on i_sem in the getxattr and listxattr iops of ext2 and ext3. In addition, the global ext[23]_xattr semaphores go away. Instead of i_sem and the global semaphore, mutual exclusion is now ensured by per-inode xattr semaphores, and by locking the buffers before modifying them. The detailed locking strategy is described in comments in fs/ext[23]/xattr.c. Due to this change it is no longer necessary to take i_sem in ext[23]_permission() for retrieving acls, so the ext[23]_permission_locked() functions go away. Additionally, the patch fixes a race condition in ext[23]_permission: Accessing inode->i_acl was protected by the BKL in 2.4; in 2.5 there no longer is such protection. Instead, inode->i_acl (and inode->i_default_acl) are now accessed under inode->i_lock. (This could be replaced by RCU in the future.) In the ext3 extended attribute code, an new uglines results from locking at the buffer head level: The buffer lock must be held between testing if an xattr block can be modified and the actual modification to prevent races from happening. Before a block can be modified, ext3_journal_get_write_access() must be called. But this requies an unlocked buffer, so I call ext3_journal_get_write_access() before locking the buffer. If it turns out that the buffer cannot be modified, journal_release_buffer() is called. Calling ext3_journal_get_write_access after the test but while the buffer is still locked would be much better.
-
Andrew Morton authored
From: Andreas Gruenbacher <agruen@suse.de> Andrew Morton found that there is lock contention between extended attribute operations (like reading ACLs, which `ls -l' needs to do) and other operations on the same files. This is due to the fact that all extended attribute syscalls take inode->i_sem before calling into the filesystem code. To fix this problem, this patch no longer takes inode->i_sem in the getxattr and listxattr syscalls, and moves the lock taking code into the file systems. (Another patch improves the locking strategy in ext2 and ext3.)
-
Andrew Morton authored
From: Andreas Gruenbacher <agruen@suse.de> It is common to update extended attributes without changing the value's length. This patch optimizes this case. In addition to that, the current code tries to recognize early when extended attribute blocks become empty. This optimization is not of significant value, so this patch removes it, and moves the empty block test further down.
-
Andrew Morton authored
From: Andreas Gruenbacher <agruen@suse.de> The inode->i_bdev field is not the same as inode->i_sb->s_bdev or bh->b_bdev. We must compare inode->i_sb->s_bdev with bh->b_bdev, or else equal extended attribute block will not be found.
-
Andrew Morton authored
From: From: Andreas Gruenbacher <agruen@suse.de> * Various minor cleanups and simplifications in the extended attributes and acl code. * Use a smarter shortcut rule in ext[23]_permission(): If the mask contains permissions that are not also contained in the group file mode permission bits, those permissions can never be granted by an acl. (The previous shortcut rule was more coarse.)
-
Andrew Morton authored
From: Daniele Belluci <bellucda@tiscali.it> proc_attr_lookup() was missed out in Trond's conversion. (It is behind CONFIG_SECURITY).
-
Andrew Morton authored
- use ll_rw_block(). - use READA - export it to modules.
-
Andrew Morton authored
- xfs printk warning fix (dev_t is ulong on ppc64) - unused var in serial_remove() (Daniele Bellucci <bellucda@tiscali.it>)
-
Andrew Morton authored
From: Mikael Pettersson <mikpe@csd.uu.se> This patch fixes two p->thread_info->cpu occurrences in kernel/sched.c to use the task_cpu(p) macro instead, which is optimised on UP. Although one of the occurrences is under #ifdef CONFIG_SMP, it's bad style to use the raw non-optimisable form in non-arch code.
-
Linus Torvalds authored
in the networking code. From YOSHIFUJI Hideaki <yoshfuji@linux-ipv6.org>
-
Greg Ungerer authored
Architecture specific flat loader code for v850 moved into its own v850 flat.h header. This patch also adds supporti for a number of relocation cases that need to be handled at laod time. Most of this code is originally from Miles Bader <miles@gnu.org>.
-
Greg Ungerer authored
Architecture specific flat loader code for m68knommu moved into its own m68knommu flat.h header. Part of the shared library flat loader update.
-
Greg Ungerer authored
Architecture specific flat loader code for H8/300 moved into its own H8/300 flat.h header.
-
Greg Ungerer authored
This patch adds shared library support to the MMU application loader, binfmt_flat. This is not new, it is a forward port from the same support in 2.4.x kernels with MMUless support, and has been running for well over a year now. The code support is conditionally compiled on CONFIG_BINFMT_FLAT_SHARED. This change also abstracts a bit more architecture dependent code into the separate flat.h includes. Basically relocations within an application also carry a tag to identify what they refer too (this code or which shared library). This is patched as before at load/run-time with an appropriate address.
-
Steve French authored
-
Greg Ungerer authored
Unify access_ok for all m68knommu targets. All targets use the common linker script and have common end symbols. So now we can just use a simple check.
-
Greg Ungerer authored
Remove "%d0" register from clobber list of down_trylock() for m68knommu. It is not used by the asm code here at all.
-
Greg Ungerer authored
Force PAGE_SIZE for the m68knommu architecture to be an unsigned long. This makes it consistent with all other architectures and cleans up a load of compiler warnings.
-
Greg Ungerer authored
Conditionally copy the ROMfs filesystem on the Motorola M5307C3 target board only if using a ROMfs.
-
Greg Ungerer authored
Allow setting boot time parameters at configuration for Motorola 5282 targets.
-
Linus Torvalds authored
This improves cold-cache program startup noticeably for me, and simplifies the read-ahead logic at the same time. The rules for read-ahead are: - if the vma is marked random, we just do the regular one-page case. Obvious. - if the vma is marked "linear access", we use the regular readahead code. No change in behaviour there (well, we also only consider it a _miss_ if it was marked linear access - the "readahead" and "readaround" things are now totally independent of each other) - otherwise, we look at how many hits/misses we've had for this particular file open for mmap, and if we've had noticeably more misses than hits, we don't bother with read-around. In particular, this means that the "real" read-ahead logic literally only needs to worry about finding sequential accesses, and does not have to worry about the common executable mmap access patthers that have very different behaviour. Some constant tweaking may be a good idea.
-
Ingo Molnar authored
in add_timer_internal() we simply leave the timer pending forever if the expiry is in more than 0xffffffff jiffies. This means more than 48 days on eg. ia64 - which is not an unrealistic timeout. IIRC crond is happy to use extremely large timeouts. It's better to time out early (if you can call 48 days "early") than to not time out at all.
-