Loading Documentation/RCU/checklist.txt +12 −0 Original line number Original line Diff line number Diff line Loading @@ -298,3 +298,15 @@ over a rather long period of time, but improvements are always welcome! Note that, rcu_assign_pointer() and rcu_dereference() relate to Note that, rcu_assign_pointer() and rcu_dereference() relate to SRCU just as they do to other forms of RCU. SRCU just as they do to other forms of RCU. 15. The whole point of call_rcu(), synchronize_rcu(), and friends is to wait until all pre-existing readers have finished before carrying out some otherwise-destructive operation. It is therefore critically important to -first- remove any path that readers can follow that could be affected by the destructive operation, and -only- -then- invoke call_rcu(), synchronize_rcu(), or friends. Because these primitives only wait for pre-existing readers, it is the caller's responsibility to guarantee safety to any subsequent readers. Documentation/feature-removal-schedule.txt +9 −0 Original line number Original line Diff line number Diff line Loading @@ -335,3 +335,12 @@ Why: In 2.6.18 the Secmark concept was introduced to replace the "compat_net" Secmark, it is time to deprecate the older mechanism and start the Secmark, it is time to deprecate the older mechanism and start the process of removing the old code. process of removing the old code. Who: Paul Moore <paul.moore@hp.com> Who: Paul Moore <paul.moore@hp.com> --------------------------- What: sysfs ui for changing p4-clockmod parameters When: September 2009 Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and e088e4c9cdb618675874becb91b2fd581ee707e6. Removal is subject to fixing any remaining bugs in ACPI which may cause the thermal throttling not to happen at the right time. Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com> Documentation/filesystems/squashfs.txt +1 −1 Original line number Original line Diff line number Diff line Loading @@ -22,7 +22,7 @@ Squashfs filesystem features versus Cramfs: Squashfs Cramfs Squashfs Cramfs Max filesystem size: 2^64 16 MiB Max filesystem size: 2^64 256 MiB Max file size: ~ 2 TiB 16 MiB Max file size: ~ 2 TiB 16 MiB Max files: unlimited unlimited Max files: unlimited unlimited Max directories: unlimited unlimited Max directories: unlimited unlimited Loading Documentation/networking/ipv6.txt 0 → 100644 +35 −0 Original line number Original line Diff line number Diff line Options for the ipv6 module are supplied as parameters at load time. Module options may be given as command line arguments to the insmod or modprobe command, but are usually specified in either the /etc/modules.conf or /etc/modprobe.conf configuration file, or in a distro-specific configuration file. The available ipv6 module parameters are listed below. If a parameter is not specified the default value is used. The parameters are as follows: disable Specifies whether to load the IPv6 module, but disable all its functionality. This might be used when another module has a dependency on the IPv6 module being loaded, but no IPv6 addresses or operations are desired. The possible values and their effects are: 0 IPv6 is enabled. This is the default value. 1 IPv6 is disabled. No IPv6 addresses will be added to interfaces, and it will not be possible to open an IPv6 socket. A reboot is required to enable IPv6. Documentation/x86/earlyprintk.txt 0 → 100644 +101 −0 Original line number Original line Diff line number Diff line Mini-HOWTO for using the earlyprintk=dbgp boot option with a USB2 Debug port key and a debug cable, on x86 systems. You need two computers, the 'USB debug key' special gadget and and two USB cables, connected like this: [host/target] <-------> [USB debug key] <-------> [client/console] 1. There are three specific hardware requirements: a.) Host/target system needs to have USB debug port capability. You can check this capability by looking at a 'Debug port' bit in the lspci -vvv output: # lspci -vvv ... 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (prog-if 20 [EHCI]) Subsystem: Lenovo ThinkPad T61 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin D routed to IRQ 19 Region 0: Memory at fe227000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME+ Capabilities: [58] Debug port: BAR=1 offset=00a0 ^^^^^^^^^^^ <==================== [ HERE ] Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd ... ( If your system does not list a debug port capability then you probably wont be able to use the USB debug key. ) b.) You also need a Netchip USB debug cable/key: http://www.plxtech.com/products/NET2000/NET20DC/default.asp This is a small blue plastic connector with two USB connections, it draws power from its USB connections. c.) Thirdly, you need a second client/console system with a regular USB port. 2. Software requirements: a.) On the host/target system: You need to enable the following kernel config option: CONFIG_EARLY_PRINTK_DBGP=y And you need to add the boot command line: "earlyprintk=dbgp". (If you are using Grub, append it to the 'kernel' line in /etc/grub.conf) NOTE: normally earlyprintk console gets turned off once the regular console is alive - use "earlyprintk=dbgp,keep" to keep this channel open beyond early bootup. This can be useful for debugging crashes under Xorg, etc. b.) On the client/console system: You should enable the following kernel config option: CONFIG_USB_SERIAL_DEBUG=y On the next bootup with the modified kernel you should get a /dev/ttyUSBx device(s). Now this channel of kernel messages is ready to be used: start your favorite terminal emulator (minicom, etc.) and set it up to use /dev/ttyUSB0 - or use a raw 'cat /dev/ttyUSBx' to see the raw output. c.) On Nvidia Southbridge based systems: the kernel will try to probe and find out which port has debug device connected. 3. Testing that it works fine: You can test the output by using earlyprintk=dbgp,keep and provoking kernel messages on the host/target system. You can provoke a harmless kernel message by for example doing: echo h > /proc/sysrq-trigger On the host/target system you should see this help line in "dmesg" output: SysRq : HELP : loglevel(0-9) reBoot Crashdump terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W) dump-ftrace-buffer(Z) On the client/console system do: cat /dev/ttyUSB0 And you should see the help line above displayed shortly after you've provoked it on the host system. If it does not work then please ask about it on the linux-kernel@vger.kernel.org mailing list or contact the x86 maintainers. Loading
Documentation/RCU/checklist.txt +12 −0 Original line number Original line Diff line number Diff line Loading @@ -298,3 +298,15 @@ over a rather long period of time, but improvements are always welcome! Note that, rcu_assign_pointer() and rcu_dereference() relate to Note that, rcu_assign_pointer() and rcu_dereference() relate to SRCU just as they do to other forms of RCU. SRCU just as they do to other forms of RCU. 15. The whole point of call_rcu(), synchronize_rcu(), and friends is to wait until all pre-existing readers have finished before carrying out some otherwise-destructive operation. It is therefore critically important to -first- remove any path that readers can follow that could be affected by the destructive operation, and -only- -then- invoke call_rcu(), synchronize_rcu(), or friends. Because these primitives only wait for pre-existing readers, it is the caller's responsibility to guarantee safety to any subsequent readers.
Documentation/feature-removal-schedule.txt +9 −0 Original line number Original line Diff line number Diff line Loading @@ -335,3 +335,12 @@ Why: In 2.6.18 the Secmark concept was introduced to replace the "compat_net" Secmark, it is time to deprecate the older mechanism and start the Secmark, it is time to deprecate the older mechanism and start the process of removing the old code. process of removing the old code. Who: Paul Moore <paul.moore@hp.com> Who: Paul Moore <paul.moore@hp.com> --------------------------- What: sysfs ui for changing p4-clockmod parameters When: September 2009 Why: See commits 129f8ae9b1b5be94517da76009ea956e89104ce8 and e088e4c9cdb618675874becb91b2fd581ee707e6. Removal is subject to fixing any remaining bugs in ACPI which may cause the thermal throttling not to happen at the right time. Who: Dave Jones <davej@redhat.com>, Matthew Garrett <mjg@redhat.com>
Documentation/filesystems/squashfs.txt +1 −1 Original line number Original line Diff line number Diff line Loading @@ -22,7 +22,7 @@ Squashfs filesystem features versus Cramfs: Squashfs Cramfs Squashfs Cramfs Max filesystem size: 2^64 16 MiB Max filesystem size: 2^64 256 MiB Max file size: ~ 2 TiB 16 MiB Max file size: ~ 2 TiB 16 MiB Max files: unlimited unlimited Max files: unlimited unlimited Max directories: unlimited unlimited Max directories: unlimited unlimited Loading
Documentation/networking/ipv6.txt 0 → 100644 +35 −0 Original line number Original line Diff line number Diff line Options for the ipv6 module are supplied as parameters at load time. Module options may be given as command line arguments to the insmod or modprobe command, but are usually specified in either the /etc/modules.conf or /etc/modprobe.conf configuration file, or in a distro-specific configuration file. The available ipv6 module parameters are listed below. If a parameter is not specified the default value is used. The parameters are as follows: disable Specifies whether to load the IPv6 module, but disable all its functionality. This might be used when another module has a dependency on the IPv6 module being loaded, but no IPv6 addresses or operations are desired. The possible values and their effects are: 0 IPv6 is enabled. This is the default value. 1 IPv6 is disabled. No IPv6 addresses will be added to interfaces, and it will not be possible to open an IPv6 socket. A reboot is required to enable IPv6.
Documentation/x86/earlyprintk.txt 0 → 100644 +101 −0 Original line number Original line Diff line number Diff line Mini-HOWTO for using the earlyprintk=dbgp boot option with a USB2 Debug port key and a debug cable, on x86 systems. You need two computers, the 'USB debug key' special gadget and and two USB cables, connected like this: [host/target] <-------> [USB debug key] <-------> [client/console] 1. There are three specific hardware requirements: a.) Host/target system needs to have USB debug port capability. You can check this capability by looking at a 'Debug port' bit in the lspci -vvv output: # lspci -vvv ... 00:1d.7 USB Controller: Intel Corporation 82801H (ICH8 Family) USB2 EHCI Controller #1 (rev 03) (prog-if 20 [EHCI]) Subsystem: Lenovo ThinkPad T61 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR+ FastB2B- DisINTx- Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 0 Interrupt: pin D routed to IRQ 19 Region 0: Memory at fe227000 (32-bit, non-prefetchable) [size=1K] Capabilities: [50] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=375mA PME(D0+,D1-,D2-,D3hot+,D3cold+) Status: D0 PME-Enable- DSel=0 DScale=0 PME+ Capabilities: [58] Debug port: BAR=1 offset=00a0 ^^^^^^^^^^^ <==================== [ HERE ] Kernel driver in use: ehci_hcd Kernel modules: ehci-hcd ... ( If your system does not list a debug port capability then you probably wont be able to use the USB debug key. ) b.) You also need a Netchip USB debug cable/key: http://www.plxtech.com/products/NET2000/NET20DC/default.asp This is a small blue plastic connector with two USB connections, it draws power from its USB connections. c.) Thirdly, you need a second client/console system with a regular USB port. 2. Software requirements: a.) On the host/target system: You need to enable the following kernel config option: CONFIG_EARLY_PRINTK_DBGP=y And you need to add the boot command line: "earlyprintk=dbgp". (If you are using Grub, append it to the 'kernel' line in /etc/grub.conf) NOTE: normally earlyprintk console gets turned off once the regular console is alive - use "earlyprintk=dbgp,keep" to keep this channel open beyond early bootup. This can be useful for debugging crashes under Xorg, etc. b.) On the client/console system: You should enable the following kernel config option: CONFIG_USB_SERIAL_DEBUG=y On the next bootup with the modified kernel you should get a /dev/ttyUSBx device(s). Now this channel of kernel messages is ready to be used: start your favorite terminal emulator (minicom, etc.) and set it up to use /dev/ttyUSB0 - or use a raw 'cat /dev/ttyUSBx' to see the raw output. c.) On Nvidia Southbridge based systems: the kernel will try to probe and find out which port has debug device connected. 3. Testing that it works fine: You can test the output by using earlyprintk=dbgp,keep and provoking kernel messages on the host/target system. You can provoke a harmless kernel message by for example doing: echo h > /proc/sysrq-trigger On the host/target system you should see this help line in "dmesg" output: SysRq : HELP : loglevel(0-9) reBoot Crashdump terminate-all-tasks(E) memory-full-oom-kill(F) kill-all-tasks(I) saK show-backtrace-all-active-cpus(L) show-memory-usage(M) nice-all-RT-tasks(N) powerOff show-registers(P) show-all-timers(Q) unRaw Sync show-task-states(T) Unmount show-blocked-tasks(W) dump-ftrace-buffer(Z) On the client/console system do: cat /dev/ttyUSB0 And you should see the help line above displayed shortly after you've provoked it on the host system. If it does not work then please ask about it on the linux-kernel@vger.kernel.org mailing list or contact the x86 maintainers.
