Loading Documentation/cgroups/cgroups.txt +9 −2 Original line number Original line Diff line number Diff line Loading @@ -227,7 +227,14 @@ as the path relative to the root of the cgroup file system. Each cgroup is represented by a directory in the cgroup file system Each cgroup is represented by a directory in the cgroup file system containing the following files describing that cgroup: containing the following files describing that cgroup: - tasks: list of tasks (by pid) attached to that cgroup - tasks: list of tasks (by pid) attached to that cgroup. This list is not guaranteed to be sorted. Writing a thread id into this file moves the thread into this cgroup. - cgroup.procs: list of tgids in the cgroup. This list is not guaranteed to be sorted or free of duplicate tgids, and userspace should sort/uniquify the list if this property is required. Writing a tgid into this file moves all threads with that tgid into this cgroup. - notify_on_release flag: run the release agent on exit? - notify_on_release flag: run the release agent on exit? - release_agent: the path to use for release notifications (this file - release_agent: the path to use for release notifications (this file exists in the top cgroup only) exists in the top cgroup only) Loading Loading @@ -374,7 +381,7 @@ Now you want to do something with this cgroup. In this directory you can find several files: In this directory you can find several files: # ls # ls notify_on_release tasks cgroup.procs notify_on_release tasks (plus whatever files added by the attached subsystems) (plus whatever files added by the attached subsystems) Now attach your shell to this cgroup: Now attach your shell to this cgroup: Loading Documentation/infiniband/user_mad.txt +2 −2 Original line number Original line Diff line number Diff line Loading @@ -128,8 +128,8 @@ Setting IsSM Capability Bit To create the appropriate character device files automatically with To create the appropriate character device files automatically with udev, a rule like udev, a rule like KERNEL="umad*", NAME="infiniband/%k" KERNEL=="umad*", NAME="infiniband/%k" KERNEL="issm*", NAME="infiniband/%k" KERNEL=="issm*", NAME="infiniband/%k" can be used. This will create device nodes named can be used. This will create device nodes named Loading Documentation/infiniband/user_verbs.txt +1 −1 Original line number Original line Diff line number Diff line Loading @@ -58,7 +58,7 @@ Memory pinning To create the appropriate character device files automatically with To create the appropriate character device files automatically with udev, a rule like udev, a rule like KERNEL="uverbs*", NAME="infiniband/%k" KERNEL=="uverbs*", NAME="infiniband/%k" can be used. This will create device nodes named can be used. This will create device nodes named Loading Documentation/isdn/INTERFACE.CAPI +67 −16 Original line number Original line Diff line number Diff line Loading @@ -60,10 +60,9 @@ open() operation on regular files or character devices. After a successful return from register_appl(), CAPI messages from the After a successful return from register_appl(), CAPI messages from the application may be passed to the driver for the device via calls to the application may be passed to the driver for the device via calls to the send_message() callback function. The CAPI message to send is stored in the send_message() callback function. Conversely, the driver may call Kernel data portion of an skb. Conversely, the driver may call Kernel CAPI's CAPI's capi_ctr_handle_message() function to pass a received CAPI message to capi_ctr_handle_message() function to pass a received CAPI message to Kernel Kernel CAPI for forwarding to an application, specifying its ApplID. CAPI for forwarding to an application, specifying its ApplID. Deregistration requests (CAPI operation CAPI_RELEASE) from applications are Deregistration requests (CAPI operation CAPI_RELEASE) from applications are forwarded as calls to the release_appl() callback function, passing the same forwarded as calls to the release_appl() callback function, passing the same Loading Loading @@ -142,6 +141,7 @@ u16 (*send_message)(struct capi_ctr *ctrlr, struct sk_buff *skb) to accepting or queueing the message. Errors occurring during the to accepting or queueing the message. Errors occurring during the actual processing of the message should be signaled with an actual processing of the message should be signaled with an appropriate reply message. appropriate reply message. May be called in process or interrupt context. Calls to this function are not serialized by Kernel CAPI, ie. it must Calls to this function are not serialized by Kernel CAPI, ie. it must be prepared to be re-entered. be prepared to be re-entered. Loading @@ -154,7 +154,8 @@ read_proc_t *ctr_read_proc system entry, /proc/capi/controllers/<n>; will be called with a system entry, /proc/capi/controllers/<n>; will be called with a pointer to the device's capi_ctr structure as the last (data) argument pointer to the device's capi_ctr structure as the last (data) argument Note: Callback functions are never called in interrupt context. Note: Callback functions except send_message() are never called in interrupt context. - to be filled in before calling capi_ctr_ready(): - to be filled in before calling capi_ctr_ready(): Loading @@ -171,14 +172,40 @@ u8 serial[CAPI_SERIAL_LEN] value to return for CAPI_GET_SERIAL value to return for CAPI_GET_SERIAL 4.3 The _cmsg Structure 4.3 SKBs CAPI messages are passed between Kernel CAPI and the driver via send_message() and capi_ctr_handle_message(), stored in the data portion of a socket buffer (skb). Each skb contains a single CAPI message coded according to the CAPI 2.0 standard. For the data transfer messages, DATA_B3_REQ and DATA_B3_IND, the actual payload data immediately follows the CAPI message itself within the same skb. The Data and Data64 parameters are not used for processing. The Data64 parameter may be omitted by setting the length field of the CAPI message to 22 instead of 30. 4.4 The _cmsg Structure (declared in <linux/isdn/capiutil.h>) (declared in <linux/isdn/capiutil.h>) The _cmsg structure stores the contents of a CAPI 2.0 message in an easily The _cmsg structure stores the contents of a CAPI 2.0 message in an easily accessible form. It contains members for all possible CAPI 2.0 parameters, of accessible form. It contains members for all possible CAPI 2.0 parameters, which only those appearing in the message type currently being processed are including subparameters of the Additional Info and B Protocol structured actually used. Unused members should be set to zero. parameters, with the following exceptions: * second Calling party number (CONNECT_IND) * Data64 (DATA_B3_REQ and DATA_B3_IND) * Sending complete (subparameter of Additional Info, CONNECT_REQ and INFO_REQ) * Global Configuration (subparameter of B Protocol, CONNECT_REQ, CONNECT_RESP and SELECT_B_PROTOCOL_REQ) Only those parameters appearing in the message type currently being processed are actually used. Unused members should be set to zero. Members are named after the CAPI 2.0 standard names of the parameters they Members are named after the CAPI 2.0 standard names of the parameters they represent. See <linux/isdn/capiutil.h> for the exact spelling. Member data represent. See <linux/isdn/capiutil.h> for the exact spelling. Member data Loading @@ -190,18 +217,19 @@ u16 for CAPI parameters of type 'word' u32 for CAPI parameters of type 'dword' u32 for CAPI parameters of type 'dword' _cstruct for CAPI parameters of type 'struct' not containing any _cstruct for CAPI parameters of type 'struct' variably-sized (struct) subparameters (eg. 'Called Party Number') The member is a pointer to a buffer containing the parameter in The member is a pointer to a buffer containing the parameter in CAPI encoding (length + content). It may also be NULL, which will CAPI encoding (length + content). It may also be NULL, which will be taken to represent an empty (zero length) parameter. be taken to represent an empty (zero length) parameter. Subparameters are stored in encoded form within the content part. _cmstruct for CAPI parameters of type 'struct' containing 'struct' _cmstruct alternative representation for CAPI parameters of type 'struct' subparameters ('Additional Info' and 'B Protocol') (used only for the 'Additional Info' and 'B Protocol' parameters) The representation is a single byte containing one of the values: The representation is a single byte containing one of the values: CAPI_DEFAULT: the parameter is empty CAPI_DEFAULT: The parameter is empty/absent. CAPI_COMPOSE: the values of the subparameters are stored CAPI_COMPOSE: The parameter is present. individually in the corresponding _cmsg structure members Subparameter values are stored individually in the corresponding _cmsg structure members. Functions capi_cmsg2message() and capi_message2cmsg() are provided to convert Functions capi_cmsg2message() and capi_message2cmsg() are provided to convert messages between their transport encoding described in the CAPI 2.0 standard messages between their transport encoding described in the CAPI 2.0 standard Loading Loading @@ -297,3 +325,26 @@ char *capi_cmd2str(u8 Command, u8 Subcommand) be NULL if the command/subcommand is not one of those defined in the be NULL if the command/subcommand is not one of those defined in the CAPI 2.0 standard. CAPI 2.0 standard. 7. Debugging The module kernelcapi has a module parameter showcapimsgs controlling some debugging output produced by the module. It can only be set when the module is loaded, via a parameter "showcapimsgs=<n>" to the modprobe command, either on the command line or in the configuration file. If the lowest bit of showcapimsgs is set, kernelcapi logs controller and application up and down events. In addition, every registered CAPI controller has an associated traceflag parameter controlling how CAPI messages sent from and to tha controller are logged. The traceflag parameter is initialized with the value of the showcapimsgs parameter when the controller is registered, but can later be changed via the MANUFACTURER_REQ command KCAPI_CMD_TRACE. If the value of traceflag is non-zero, CAPI messages are logged. DATA_B3 messages are only logged if the value of traceflag is > 2. If the lowest bit of traceflag is set, only the command/subcommand and message length are logged. Otherwise, kernelcapi logs a readable representation of the entire message. Documentation/kernel-parameters.txt +1 −0 Original line number Original line Diff line number Diff line Loading @@ -671,6 +671,7 @@ and is between 256 and 4096 characters. It is defined in the file earlyprintk= [X86,SH,BLACKFIN] earlyprintk= [X86,SH,BLACKFIN] earlyprintk=vga earlyprintk=vga earlyprintk=serial[,ttySn[,baudrate]] earlyprintk=serial[,ttySn[,baudrate]] earlyprintk=ttySn[,baudrate] earlyprintk=dbgp[debugController#] earlyprintk=dbgp[debugController#] Append ",keep" to not disable it when the real console Append ",keep" to not disable it when the real console Loading Loading
Documentation/cgroups/cgroups.txt +9 −2 Original line number Original line Diff line number Diff line Loading @@ -227,7 +227,14 @@ as the path relative to the root of the cgroup file system. Each cgroup is represented by a directory in the cgroup file system Each cgroup is represented by a directory in the cgroup file system containing the following files describing that cgroup: containing the following files describing that cgroup: - tasks: list of tasks (by pid) attached to that cgroup - tasks: list of tasks (by pid) attached to that cgroup. This list is not guaranteed to be sorted. Writing a thread id into this file moves the thread into this cgroup. - cgroup.procs: list of tgids in the cgroup. This list is not guaranteed to be sorted or free of duplicate tgids, and userspace should sort/uniquify the list if this property is required. Writing a tgid into this file moves all threads with that tgid into this cgroup. - notify_on_release flag: run the release agent on exit? - notify_on_release flag: run the release agent on exit? - release_agent: the path to use for release notifications (this file - release_agent: the path to use for release notifications (this file exists in the top cgroup only) exists in the top cgroup only) Loading Loading @@ -374,7 +381,7 @@ Now you want to do something with this cgroup. In this directory you can find several files: In this directory you can find several files: # ls # ls notify_on_release tasks cgroup.procs notify_on_release tasks (plus whatever files added by the attached subsystems) (plus whatever files added by the attached subsystems) Now attach your shell to this cgroup: Now attach your shell to this cgroup: Loading
Documentation/infiniband/user_mad.txt +2 −2 Original line number Original line Diff line number Diff line Loading @@ -128,8 +128,8 @@ Setting IsSM Capability Bit To create the appropriate character device files automatically with To create the appropriate character device files automatically with udev, a rule like udev, a rule like KERNEL="umad*", NAME="infiniband/%k" KERNEL=="umad*", NAME="infiniband/%k" KERNEL="issm*", NAME="infiniband/%k" KERNEL=="issm*", NAME="infiniband/%k" can be used. This will create device nodes named can be used. This will create device nodes named Loading
Documentation/infiniband/user_verbs.txt +1 −1 Original line number Original line Diff line number Diff line Loading @@ -58,7 +58,7 @@ Memory pinning To create the appropriate character device files automatically with To create the appropriate character device files automatically with udev, a rule like udev, a rule like KERNEL="uverbs*", NAME="infiniband/%k" KERNEL=="uverbs*", NAME="infiniband/%k" can be used. This will create device nodes named can be used. This will create device nodes named Loading
Documentation/isdn/INTERFACE.CAPI +67 −16 Original line number Original line Diff line number Diff line Loading @@ -60,10 +60,9 @@ open() operation on regular files or character devices. After a successful return from register_appl(), CAPI messages from the After a successful return from register_appl(), CAPI messages from the application may be passed to the driver for the device via calls to the application may be passed to the driver for the device via calls to the send_message() callback function. The CAPI message to send is stored in the send_message() callback function. Conversely, the driver may call Kernel data portion of an skb. Conversely, the driver may call Kernel CAPI's CAPI's capi_ctr_handle_message() function to pass a received CAPI message to capi_ctr_handle_message() function to pass a received CAPI message to Kernel Kernel CAPI for forwarding to an application, specifying its ApplID. CAPI for forwarding to an application, specifying its ApplID. Deregistration requests (CAPI operation CAPI_RELEASE) from applications are Deregistration requests (CAPI operation CAPI_RELEASE) from applications are forwarded as calls to the release_appl() callback function, passing the same forwarded as calls to the release_appl() callback function, passing the same Loading Loading @@ -142,6 +141,7 @@ u16 (*send_message)(struct capi_ctr *ctrlr, struct sk_buff *skb) to accepting or queueing the message. Errors occurring during the to accepting or queueing the message. Errors occurring during the actual processing of the message should be signaled with an actual processing of the message should be signaled with an appropriate reply message. appropriate reply message. May be called in process or interrupt context. Calls to this function are not serialized by Kernel CAPI, ie. it must Calls to this function are not serialized by Kernel CAPI, ie. it must be prepared to be re-entered. be prepared to be re-entered. Loading @@ -154,7 +154,8 @@ read_proc_t *ctr_read_proc system entry, /proc/capi/controllers/<n>; will be called with a system entry, /proc/capi/controllers/<n>; will be called with a pointer to the device's capi_ctr structure as the last (data) argument pointer to the device's capi_ctr structure as the last (data) argument Note: Callback functions are never called in interrupt context. Note: Callback functions except send_message() are never called in interrupt context. - to be filled in before calling capi_ctr_ready(): - to be filled in before calling capi_ctr_ready(): Loading @@ -171,14 +172,40 @@ u8 serial[CAPI_SERIAL_LEN] value to return for CAPI_GET_SERIAL value to return for CAPI_GET_SERIAL 4.3 The _cmsg Structure 4.3 SKBs CAPI messages are passed between Kernel CAPI and the driver via send_message() and capi_ctr_handle_message(), stored in the data portion of a socket buffer (skb). Each skb contains a single CAPI message coded according to the CAPI 2.0 standard. For the data transfer messages, DATA_B3_REQ and DATA_B3_IND, the actual payload data immediately follows the CAPI message itself within the same skb. The Data and Data64 parameters are not used for processing. The Data64 parameter may be omitted by setting the length field of the CAPI message to 22 instead of 30. 4.4 The _cmsg Structure (declared in <linux/isdn/capiutil.h>) (declared in <linux/isdn/capiutil.h>) The _cmsg structure stores the contents of a CAPI 2.0 message in an easily The _cmsg structure stores the contents of a CAPI 2.0 message in an easily accessible form. It contains members for all possible CAPI 2.0 parameters, of accessible form. It contains members for all possible CAPI 2.0 parameters, which only those appearing in the message type currently being processed are including subparameters of the Additional Info and B Protocol structured actually used. Unused members should be set to zero. parameters, with the following exceptions: * second Calling party number (CONNECT_IND) * Data64 (DATA_B3_REQ and DATA_B3_IND) * Sending complete (subparameter of Additional Info, CONNECT_REQ and INFO_REQ) * Global Configuration (subparameter of B Protocol, CONNECT_REQ, CONNECT_RESP and SELECT_B_PROTOCOL_REQ) Only those parameters appearing in the message type currently being processed are actually used. Unused members should be set to zero. Members are named after the CAPI 2.0 standard names of the parameters they Members are named after the CAPI 2.0 standard names of the parameters they represent. See <linux/isdn/capiutil.h> for the exact spelling. Member data represent. See <linux/isdn/capiutil.h> for the exact spelling. Member data Loading @@ -190,18 +217,19 @@ u16 for CAPI parameters of type 'word' u32 for CAPI parameters of type 'dword' u32 for CAPI parameters of type 'dword' _cstruct for CAPI parameters of type 'struct' not containing any _cstruct for CAPI parameters of type 'struct' variably-sized (struct) subparameters (eg. 'Called Party Number') The member is a pointer to a buffer containing the parameter in The member is a pointer to a buffer containing the parameter in CAPI encoding (length + content). It may also be NULL, which will CAPI encoding (length + content). It may also be NULL, which will be taken to represent an empty (zero length) parameter. be taken to represent an empty (zero length) parameter. Subparameters are stored in encoded form within the content part. _cmstruct for CAPI parameters of type 'struct' containing 'struct' _cmstruct alternative representation for CAPI parameters of type 'struct' subparameters ('Additional Info' and 'B Protocol') (used only for the 'Additional Info' and 'B Protocol' parameters) The representation is a single byte containing one of the values: The representation is a single byte containing one of the values: CAPI_DEFAULT: the parameter is empty CAPI_DEFAULT: The parameter is empty/absent. CAPI_COMPOSE: the values of the subparameters are stored CAPI_COMPOSE: The parameter is present. individually in the corresponding _cmsg structure members Subparameter values are stored individually in the corresponding _cmsg structure members. Functions capi_cmsg2message() and capi_message2cmsg() are provided to convert Functions capi_cmsg2message() and capi_message2cmsg() are provided to convert messages between their transport encoding described in the CAPI 2.0 standard messages between their transport encoding described in the CAPI 2.0 standard Loading Loading @@ -297,3 +325,26 @@ char *capi_cmd2str(u8 Command, u8 Subcommand) be NULL if the command/subcommand is not one of those defined in the be NULL if the command/subcommand is not one of those defined in the CAPI 2.0 standard. CAPI 2.0 standard. 7. Debugging The module kernelcapi has a module parameter showcapimsgs controlling some debugging output produced by the module. It can only be set when the module is loaded, via a parameter "showcapimsgs=<n>" to the modprobe command, either on the command line or in the configuration file. If the lowest bit of showcapimsgs is set, kernelcapi logs controller and application up and down events. In addition, every registered CAPI controller has an associated traceflag parameter controlling how CAPI messages sent from and to tha controller are logged. The traceflag parameter is initialized with the value of the showcapimsgs parameter when the controller is registered, but can later be changed via the MANUFACTURER_REQ command KCAPI_CMD_TRACE. If the value of traceflag is non-zero, CAPI messages are logged. DATA_B3 messages are only logged if the value of traceflag is > 2. If the lowest bit of traceflag is set, only the command/subcommand and message length are logged. Otherwise, kernelcapi logs a readable representation of the entire message.
Documentation/kernel-parameters.txt +1 −0 Original line number Original line Diff line number Diff line Loading @@ -671,6 +671,7 @@ and is between 256 and 4096 characters. It is defined in the file earlyprintk= [X86,SH,BLACKFIN] earlyprintk= [X86,SH,BLACKFIN] earlyprintk=vga earlyprintk=vga earlyprintk=serial[,ttySn[,baudrate]] earlyprintk=serial[,ttySn[,baudrate]] earlyprintk=ttySn[,baudrate] earlyprintk=dbgp[debugController#] earlyprintk=dbgp[debugController#] Append ",keep" to not disable it when the real console Append ",keep" to not disable it when the real console Loading
