- 01 Jun, 2004 40 commits
-
-
bk://bk.arm.linux.org.uk/linux-2.6-rmkLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Russell King authored
-
Nicolas Pitre authored
Patch from Nicolas Pitre [patch rediffed] On PXA27x the memory and LCd clocks are different. Also clean the PXA27x clock code a bit.
-
Russell King authored
-
Russell King authored
Remove 26-bit ARM region reserves. All region reserves start at PHYS_OFFSET, and we only ever have one, so set res_size and reserve the region from PHYS_OFFSET size res_size. Don't free the .init sections on Integrator/CP - they sit in the SSRAM obscured region so we are unable to use them for DMA purposes.
-
Linus Torvalds authored
Ingo explains: The condition is 'impossible', but the whole balancing code is (intentionally) a bit racy: cpus_and(tmp, group->cpumask, cpu_online_map); if (!cpus_weight(tmp)) goto next_group; for_each_cpu_mask(i, tmp) { if (!idle_cpu(i)) goto next_group; push_cpu = i; } rq = cpu_rq(push_cpu); double_lock_balance(busiest, rq); move_tasks(rq, push_cpu, busiest, 1, sd, IDLE); in the for_each_cpu_mask() loop we specifically check for each CPU in the target group to be idle - so push_cpu's runqueue == busiest [== current runqueue] cannot be true because the current CPU is not idle, we are running in the migration thread ... But this is not a real problem, load-balancing we do in a racy way to reduce overhead [and it's all statistics anyway so absolute accuracy is impossible], and active balancing itself is somewhat racy due to the migration-thread wakeup (and the active_balance flag) going outside the runqueue locks [for similar reasons]. so it all looks quite plausible - the normal SMP boxes dont trigger it, but Bjorn's 128-CPU setup with a non-trivial domain hiearachy triggers it. Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Bjorn Helgaas authored
active_load_balance() looks susceptible to deadlock when busiest==rq. Without the following patch, my 128-way box deadlocks consistently during boot-time driver init.
-
http://linux-watchdog.bkbits.net/linux-2.6-watchdogLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Pádraig Brady authored
Add w83627hf_select_wd_register and w83627hf_unselect_wd_register. Add w83627hf_init to fix initialization problem on certain motherboards. Make ping and disable code return 0 (int) on success. Extract set_heartbeat code to seperate function.
-
Linus Torvalds authored
We already have over 200 sign-off lines in the kernel, so let's document the thing, even if discussion may still be on-going.
-
bk://linux-dj.bkbits.net/agpgartLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Dave Jones authored
into delerium.codemonkey.org.uk:/mnt/nfs/neologic/bar/src/kernel/2.6/trees/agpgart
-
Dave Jones authored
From: Matt Domsch. The E7205 doesn't have an AGP header, so printing this message is pretty much useless. Also make it KERN_WARNING as well, as it's not really worthy of a KERN_ERR
-
Dave Jones authored
-
Dave Jones authored
(the bios might not have done that). From: Arjan van de Ven
-
Dave Jones authored
This option only worked for the amd64 driver. On every other driver, the only thing it did was make it not printk the banner on startup.
-
Dave Jones authored
This is horribly broken due to a jiffy wrap bug, we never get out of the while loop, preventing booting on a kernel with this driver compiled in. (See https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=124495) The warning message there has never been reported in any bug report that google can find, so I'm of the opinion that this driver is trying to be too clever for its own good. Rip out the jiffies logic completely, it should be totally unnecessary.
-
bk://linux-dj.bkbits.net/cpufreqLinus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Dave Jones authored
Arjan noted that in some cases, the build fails. This should fix it up.
-
Andrew Morton authored
From: <fxkuehl@gmx.de> When I switch the computer to standby with echo -n standby > /sys/power/state the radeonfb driver tells me its suspending to state 1 but the display does not get turned off. It turns out to be a small typo in drivers/video/aty/radeon_pm.c. (from http://bugme.osdl.org/show_bug.cgi?id=2758) Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: "Mikael Starvik" <mikael.starvik@axis.com> - Lots of fixes from 2.4. - Updated for 2.6.6. - Added IDE driver Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> Split off from suparna's patches: Correct use_mm()/unuse_mm() to use task_lock() to protect task->mm. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: William Lee Irwin III <wli@holomorphy.com> Minor aio correction split off from suparna's patches: Use the dedicated aio workqueue, not keventd, in order to isolate the rest of the system from aio's demands. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: George France <france@handhelds.org> Teach cpqarray.c to do the add_disk_randomness() thing. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Ingo Molnar <mingo@elte.hu> Now the x86_64 bitop memory clobber problem has been fixed we can remove this. Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Andi Kleen <ak@muc.de> Add missing memory clobbers to find_first_bit() and find_first_zero_bit(). Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: NeilBrown <neilb@cse.unsw.edu.au> The read-ahead structures were not being initialised properly, and were not having the use-count decremented after use, making them fairly useless (since Apr 2002!). From: Colin Gibbs <colin@gibbsonline.net> Signed-off-by: Neil Brown <neilb@cse.unsw.edu.au> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Christoph Hellwig <hch@lst.de> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Christoph Hellwig <hch@lst.de> timer.h is using NULL and thus needs stddef.h, without it some drivers break on alpha. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: bert hubert <ahu@ds9a.nl> Documentation is in fact for tgkill and not for tkill Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Marc-Christian Petersen <m.c.p@kernel.linux-systeme.com> Give the vesafb `vram' boot option the same (silly) syntax as 2.4 and document it. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Diego Calleja =?ISO-8859-15?Q?Garc=EDa?= <diegocg@teleline.es> It'll be much better if the world can know about the existence of checkstacks. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Christoph Hellwig <hch@lst.de> Extracted from the Debian kernel package Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Adrian Bunk <bunk@fs.tum.de> LD .tmp_vmlinux1 security/built-in.o(.text+0x97e4): In function `selnl_notify': : undefined reference to `alloc_skb' security/built-in.o(.text+0x988a): In function `selnl_notify': : undefined reference to `netlink_broadcast' Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Adrian Bunk <bunk@fs.tum.de> POSIX_MQUEUE requires netlink. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Ingo Molnar <mingo@elte.hu> the patch below gets rid of a message that gets printed during FC2's quiet bootup. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: <gniibe@m17n.org> There is a missing pop-off after call of acpi_enter_sleep_state. On success, acpi_enter_sleep_state never returns, but on failure, it will cause kernel OOPS. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: David Goodenough <david.goodenough@btconnect.com> Add PCI device supoprt for the Geode SC1100-based Microtik Routerboard 230. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Brian Gerst <bgerst@didntduck.org> We don't need to keep the pointer array around after the caches are initialized. This doesn't affect the actual strings. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Andrew Morton authored
From: Jakub Jelinek <jakub@redhat.com> FUTEX_REQUEUE operation has been added to the kernel mainly to improve pthread_cond_broadcast which previously used FUTEX_WAKE INT_MAX op. pthread_cond_broadcast releases internal condvar mutex before FUTEX_REQUEUE operation, as otherwise the woken up thread most likely immediately sleeps again on the internal condvar mutex until the broadcasting thread releases it. Unfortunately this is racy and causes e.g. http://sources.redhat.com/cgi-bin/cvsweb.cgi/libc/nptl/tst-cond16.c?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=glibc to hang on SMP. http://listman.redhat.com/archives/phil-list/2004-May/msg00023.html contains analysis how the hang happens, the problem is if any thread does pthread_cond_*wait in between releasing of the internal condvar mutex and FUTEX_REQUEUE operation, a wrong thread might be awaken (and immediately go to sleep again because it doesn't satisfy conditions for returning from pthread_cond_*wait) while the right thread requeued on the associated mutex and there would be nobody to wake that thread up. The patch below extends FUTEX_REQUEUE operation with something FUTEX_WAIT already uses: FUTEX_CMP_REQUEUE is passed an additional argument which is the expected value of *futex. Kernel then while holding the futex locks checks if *futex != expected and returns -EAGAIN in that case, while if it is equal, continues with a normal FUTEX_REQUEUE operation. If the syscall returns -EAGAIN, NPTL can fall back to FUTEX_WAKE INT_MAX operation which doesn't have this problem, but is less efficient, while in the likely case that nobody hit the (small) window the efficient FUTEX_REQUEUE operation is used. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-