linux.git/Documentation/kernel-parameters.txt, branch v2.6.17

Doc/kernel-parameters.txt: slightly reword sentence about restrictions

2006-03-31T23:44:30+00:00

The previous patch somewhat diverted the train of thought.
Here I am trying to bring the valued reader back on track.

Signed-off-by: Stefan Richter 
Signed-off-by: Adrian Bunk

Doc/kernel-parameters.txt: mention modinfo and sysfs

2006-03-31T23:43:18+00:00

Doc/kernel-parameters.txt: mention modinfo and sysfs

Signed-off-by: Stefan Richter 
Signed-off-by: Adrian Bunk

Doc/kernel-parameters.txt: delete false version information and history

2006-03-31T23:42:29+00:00

Doc/kernel-parameters.txt: delete false version information and history

Signed-off-by: Stefan Richter 
Signed-off-by: Adrian Bunk

Documentation: Reorder documentation of nomca and nomce

2006-03-31T23:36:09+00:00

My patch to add brief documentation of the nomca boot parameter
added it out of alphabetical order.

Signed-Off-By: Horms 
Signed-off-by: Adrian Bunk

[PATCH] doc: more serial-console info

2006-03-25T16:23:00+00:00

Add info on flow control for serial consoles.  Refer to netconsole option
also.

Signed-off-by: Randy Dunlap 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] PCI: Provide a boot parameter to disable MSI

2006-03-23T22:35:16+00:00

Several drivers are starting to grow options to disable MSI.  However,
it's often a host chipset issue, not something which individual drivers
should handle.  So we add the pci=nomsi kernel parameter to allow the user
to disable MSI modes for systems we haven't added to the quirk list yet.

Signed-off-by: Matthew Wilcox 
Signed-off-by: Randy Dunlap 
Acked-by: Jeff Garzik 
Signed-off-by: Greg Kroah-Hartman

[PATCH] pause_on_oops command line option

2006-03-23T15:38:16+00:00

Attempt to fix the problem wherein people's oops reports scroll off the screen
due to repeated oopsing or to oopses on other CPUs.

If this happens the user can reboot with the `pause_on_oops=' option.
It will allow the first oopsing CPU to print an oops record just a single
time.  Second oopsing attempts, or oopses on other CPUs will cause those CPUs
to enter a tight loop until the specified number of seconds have elapsed.

The patch implements the infrastructure generically in the expectation that
architectures other than x86 will find it useful.

Cc: Dave Jones 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] i386: allow disabling X86_FEATURE_SEP at boot

2006-03-23T15:38:04+00:00

Allow the x86 "sep" feature to be disabled at bootup.  This forces use of the
int80 vsyscall.  Mainly for testing or benchmarking the int80 vsyscall code.

Signed-off-by: Chuck Ebbert <76306.1226@compuserve.com>
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] i386: port ATI timer fix from x86_64 to i386 II

2006-03-09T02:10:31+00:00

ATI chipsets tend to generate double timer interrupts for the local APIC
timer when both the 8254 and the IO-APIC timer pins are enabled.  This is
because they route it to both and the result is anded together and the CPU
ends up processing it twice.

This patch changes check_timer to disable the 8254 routing for interrupt 0.

I think it would be safe on all chipsets actually (i tested it on a couple
and it worked everywhere) and Windows seems to do it in a similar way, but
to be conservative this patch only enables this mode on ATI (and adds
options to enable/disable too)

Ported over from a similar x86-64 change.

I reused the ACPI earlyquirk infrastructure for the ATI bridge check, but
tweaked it a bit to work even without ACPI.

Inspired by a patch from Chuck Ebbert, but redone.

Cc: Chuck Ebbert <76306.1226@compuserve.com>
Cc: "Brown, Len" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

[PATCH] rcu batch tuning

2006-03-08T22:14:01+00:00

This patch adds new tunables for RCU queue and finished batches.  There are
two types of controls - number of completed RCU updates invoked in a batch
(blimit) and monitoring for high rate of incoming RCUs on a cpu (qhimark,
qlowmark).

By default, the per-cpu batch limit is set to a small value.  If the input
RCU rate exceeds the high watermark, we do two things - force quiescent
state on all cpus and set the batch limit of the CPU to INTMAX.  Setting
batch limit to INTMAX forces all finished RCUs to be processed in one shot.
 If we have more than INTMAX RCUs queued up, then we have bigger problems
anyway.  Once the incoming queued RCUs fall below the low watermark, the
batch limit is set to the default.

Signed-off-by: Dipankar Sarma 
Cc: "Paul E. McKenney" 
Cc: "David S. Miller" 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds