This allows arbitrary firmware files to be included in the static kernel where the firmware loader can find them without requiring userspace to be alive. (Updated and CONFIG_BUILTIN_FIRMWARE_DIR added with lots of help from Johannes Berg). Signed-off-by: David Woodhouse <dwmw2@infradead.org> Signed-off-by: Johannes Berg <johannes@sipsolutions.net> --- Makefile | 2 +- drivers/base/Kconfig | 33 +++++++++++++++++++ firmware/Makefile | 88 ++++++++++++++++++++++...

There is no point to consider FreeBSD et al. in the linux kernel source code. Signed-off-by: Carlos R. Mafra <crmafra@gmail.com> --- drivers/char/drm/drm.h | 17 ----------------- 1 files changed, 0 insertions(+), 17 deletions(-) diff --git a/drivers/char/drm/drm.h b/drivers/char/drm/drm.h index 3a05c6d..140f461 100644 --- a/drivers/char/drm/drm.h +++ b/drivers/char/drm/drm.h @@ -36,7 +36,6 @@ #ifndef _DRM_H_ #define _DRM_H_ -#if defined(__linux__) #if defined(__KERNEL__) ...

From: Rik van Riel <riel@redhat.com> During an AIM7 run on a 16GB system, fork started failing around 32000 threads, despite the system having plenty of free swap and 15GB of pageable memory. If normal pageout does not result in contiguous free pages for kernel stacks, fall back to lumpy reclaim instead of failing fork or doing excessive pageout IO. I do not know whether this change is needed due to the extreme stress test or because the inactive list is a smaller fraction of system mem...

From: Lee Schermerhorn <Lee.Schermerhorn@hp.com> Christoph Lameter pointed out that ram disk pages also clutter the LRU lists. When vmscan finds them dirty and tries to clean them, the ram disk writeback function just redirties the page so that it goes back onto the active list. Round and round she goes... Define new address_space flag [shares address_space flags member with mapping's gfp mask] to indicate that the address space contains all non-reclaimable pages. This will provide for e...

From: Lee Schermerhorn <Lee.Schermerhorn@hp.com> Report non-reclaimable pages per zone and system wide. Note: may want to track/report some specific reasons for nonreclaimability for deciding when to splice the noreclaim lists back to the normal lru. That will be tricky, especially in shrink_active_list(), where we'd need someplace to save the per page reason for non-reclaimability until the pages are dumped back onto the noreclaim list from the pagevec. Note: my tests indicate that ...

From: Rik van Riel <riel@redhat.com> We avoid evicting and scanning anonymous pages for the most part, but under some workloads we can end up with most of memory filled with anonymous pages. At that point, we suddenly need to clear the referenced bits on all of memory, which can take ages on very large memory systems. We can reduce the maximum number of pages that need to be scanned by not taking the referenced state into account when deactivating an anonymous page. After all, every anony...

From: Rik van Riel <riel@redhat.com> Swapin_readahead can read in a lot of data that the processes in memory never need. Adding swap cache pages to the inactive list prevents them from putting too much pressure on the working set. This has the potential to help the programs that are already in memory, but it could also be a disadvantage to processes that are trying to get swapped in. In short, this patch needs testing. Signed-off-by: Rik van Riel <riel@redhat.com> --- mm/sw...

From: Lee Schermerhorn <Lee.Schermerhorn@hp.com> While working with Nick Piggin's mlock patches, I noticed that shmem segments locked via shmctl(SHM_LOCKED) were not being handled. SHM_LOCKed pages work like ramdisk pages--the writeback function just redirties the page so that it can't be reclaimed. Deal with these using the same approach as for ram disk pages. Use the AS_NORECLAIM flag to mark address_space of SHM_LOCKed shared memory regions as non-reclaimable. Then these pages will be...

From: Rik van Riel <riel@redhat.com> Split the LRU lists in two, one set for pages that are backed by real file systems ("file") and one for pages that are backed by memory and swap ("anon"). The latter includes tmpfs. Eventually mlocked pages will be taken off the LRUs alltogether. A patch for that already exists and just needs to be integrated into this series. This patch mostly has the infrastructure and a basic policy to balance how much we scan the anon lists and how much we scan ...

Signed-off-by: Kristian Høgsberg <krh@redhat.com> --- arch/x86/boot/compressed/misc.c | 26 +++++++++++--------------- 1 files changed, 11 insertions(+), 15 deletions(-) diff --git a/arch/x86/boot/compressed/misc.c b/arch/x86/boot/compressed/misc.c index 90456ce..0d03579 100644 --- a/arch/x86/boot/compressed/misc.c +++ b/arch/x86/boot/compressed/misc.c @@ -30,6 +30,7 @@ #include <asm/io.h> #include <asm/page.h> #include <asm/boot.h> +#include <asm/bootparam.h&...

Hi, Isn't that a bit much code to potentially suppress three lines of output? Hannes --

Currently it is possible for some errors to be detected at write-back time but not reported to the program as shown by the following script using the included make_file.c. Undetected ENOSPC or EIO can obviously lead to data corruption. ---------8<---------8<---------8<---------8<---------8<---------8<--------- #!/bin/bash # We binary search the size of a file in a 40M filesystem that can cause # the missed error. MIN=5000000 MAX=50000000 rm fs.40M dd if=/dev/zero of=fs.40M...

From: Nick Piggin <npiggin@suse.de> isolate_lru_page logically belongs to be in vmscan.c than migrate.c. It is tough, because we don't need that function without memory migration so there is a valid argument to have it in migrate.c. However a subsequent patch needs to make use of it in the core mm, so we can happily move it to vmscan.c. Also, make the function a little more generic by not requiring that it adds an isolated page to a given list. Callers can do that. Note that we now ha...

Current IRQ affinity interface does not provide a way to set affinity for the IRQs that will be allocated/activated in the future. This patch creates /proc/irq/default_smp_affinity that lets users set default affinity mask for the newly allocated IRQs. Changing default does not affect affinity masks for the currently active IRQs, they have to be changed explicitly. Signed-off-by: Max Krasnyansky <maxk@qualcomm.com> --- arch/alpha/kernel/irq.c | 5 +-- include/linux/irq.h | 14 ++++...

Oops, my bad. Did it again. Will fix. Max --

<posted & mailed> This fixed the problem for me (it was horribly intermittant but I've done 10+ consecutive reboots without seeing an oopos). I changed the patch to printk everytime the condition was hit and it seems to happen twice per PATA device - once after each scsi?: pata_via message and then again after each scsi 0:0:0:0: Direct-Accesss ATA DISKID etc : 0 ANSI: 5 . The thing I don't understand about your explanation is that it sounds like the device struct is being round-trippe...

From: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> Signed-off-by: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com> --- scripts/.gitignore | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/scripts/.gitignore b/scripts/.gitignore index b939fbd..bb1dd86 100644 --- a/scripts/.gitignore +++ b/scripts/.gitignore @@ -7,3 +7,4 @@ pnmtologo bin2c unifdef binoffset +testlpp -- 1.5.4.1 --

Hi, since my upgrade to openSUSE 11.0, which comes with 2.6.25.4, soon after I start using my DVD player, I get the following in the log: May 23 21:34:04 stein klogd: ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen May 23 21:34:04 stein klogd: ata1.00: cmd a0/01:00:00:00:08/00:00:00:00:00/a0 tag 0 dma 2048 in May 23 21:34:04 stein klogd: cdb 28 00 00 00 01 b3 00 00 01 0...

That wouldn't be a problem if it would not block the drive completely Not yet, I will try them (but as I said it worked fine before, without any such kernel options). Andras -- Quanta Plus developer - http://quanta.kdewebdev.org K Desktop Environment - http://www.kde.org --

The former. Why? Because the latter case has unbalanced indentation: to an editor, and to the human eye, it looks like the if in the #else clause is a child to the "else if". *However*, the best would really be if we changed Kconfig to emit configuration constants what were 0/1 instead of undefined/defined. That way we could do: if (CONFIG_SOMETHING && foo) { /* ... something ... */ } else if ((mode & S_IWUGO) == 0) { /* ... */ ... in many cases. -hpa --

I would consider the first one much harder to read since you can _very_ easily miss that the "if" is in an "else" clause and completely misread cu Adrian -- "Is there not promise of rain?" Ling Tan asked suddenly out of the darkness. There had been need of rain for many days. "Only a promise," Lao Er said. Pearl S. Buck - Dragon Seed --

dock.c remove trailing printk whitespace Signed-off-by: Tim Pepper <lnxninja@linux.vnet.ibm.com> --- I was looking at how docking events are handled these days as I was hoping to have an event handler automatically run an xrandr script for me to set up and remove my docking station attached monitor on dock/undock (which I still haven't figured out how to do or if it's even supported with my hardware :) and noticed the printk from the dock driver left trailing whitespace in syslog. Given...

This patch depends on the Grant Likely's SPI patches, so this is for RFC only. Also, later we'll able to remove OF_GPIO dependency. Signed-off-by: Anton Vorontsov <avorontsov@ru.mvista.com> --- Documentation/powerpc/booting-without-of.txt | 24 ++++ drivers/mmc/host/Kconfig | 7 ++ drivers/mmc/host/Makefile | 2 +- drivers/mmc/host/of_mmc_spi.c | 151 ++++++++++++++++++++++++++ 4 files changed, 183 insertions(+), 1 deletions(...

thinkpad z60m, Intel(R) Pentium(R) M processor 2.00GHz. kernel from git fro= m=20 1-2 days ago.=20 Unfortunately it seems that suspend to ram/resume causes frequency to be limited to 800MHz only. I can't set it to 2GHz again :-/ scaling_max_freq is then 800000 and cannot be changed. reboot and the problem disappears until new suspend/resume cycle. cpufreq stuff is driven by acpi-cpufreq $ cpufreq-info cpufrequtils 002: cpufreq-info (C) Dominik Brodowski 2004-2006 Report errors and bugs...

Hi folks, It's time to start kicking off the 2008 Kernel Summit planning process. This year, the Kernel Summit will be held in Portland, Oregon, on September 15-16, just before the Plumber's conference. As in previous years, I've set up a e-mail discussion list for people who are interested in making suggestions for this year's kernel summit. In the probably hopeless attempt to avoid the list address getting instantly harvested by spammers from all of the LKML archives, the list submi...