| /linux-4.4.14/Documentation/zh_CN/ |
| D | HOWTO | 116 "Linux kernel patch submission format"
140 Documentation/kernel-docs.txt
180 http://selenic.com/mailman/listinfo/kernel-mentors
205 kernel.org网站的pub/linux/kernel/v2.6/目录下找到它。它的开发遵循以下步
224 关于内核发布，值得一提的是Andrew Morton在linux-kernel邮件列表中如是说：
240 2.6.x.y版本由“稳定版”小组（邮件地址<stable@vger.kernel.org>）维护，一般隔周发
258 和补丁拼凑到一起，并且加入了大量从linux-kernel邮件列表中采集的补丁。这个
269 linux-kernel邮件列表中提供反馈，告诉大家你遇到了问题还是一切正常。
286 git.kernel.org:/pub/scm/linux/kernel/git/sam/kbuild.git
289 git.kernel.org:/pub/scm/linux/kernel/git/lenb/linux-acpi-2.6.git
[all …]
|
| D | oops-tracing.txt | 19 中文版校译者： 李阳 Li Yang <leo@zh-kernel.org>
36 如果你对于发送给谁一无所知， 发给linux-kernel@vger.kernel.org。感谢你帮助Linux
68 怎样跟踪Oops.. [原发到linux-kernel的一封邮件]
160 Aug 29 09:51:01 blizard kernel: Unable to handle kernel paging request at virtual address f15e97cc
161 Aug 29 09:51:01 blizard kernel: current->tss.cr3 = 0062d000, %cr3 = 0062d000
162 Aug 29 09:51:01 blizard kernel: *pde = 00000000
163 Aug 29 09:51:01 blizard kernel: Oops: 0002
164 Aug 29 09:51:01 blizard kernel: CPU: 0
165 Aug 29 09:51:01 blizard kernel: EIP: 0010:[oops:_oops+16/3868]
166 Aug 29 09:51:01 blizard kernel: EFLAGS: 00010212
[all …]
|
| D | SubmittingPatches | 9 Chinese maintainer: TripleX Chung <triplex@zh-kernel.org>
17 中文版维护者： 钟宇 TripleX Chung <triplex@zh-kernel.org>
18 中文版翻译者： 钟宇 TripleX Chung <triplex@zh-kernel.org>
19 中文版校译者： 李阳 Li Yang <leo@zh-kernel.org>
118 件列表 linux-kernel@vger.kernel.org。大部分的内核开发者都跟踪这个邮件列
129 linux-kernel邮件列表。只有当补丁被讨论得差不多了，才提交给Linus。
133 除非你有理由不这样做，否则CC linux-kernel@vger.kernel.org。
136 的改动并提供代码审查和建议。linux-kernel 是 Linux 内核开发者主邮件列表
142 <http://vger.kernel.org/vger-lists.html>
152 (Trivial Patch Monkey)trivial@kernel.org，那里专门收集琐碎的补丁。下面这样
[all …]
|
| D | stable_kernel_rules.txt | 9 Chinese maintainer: TripleX Chung <triplex@zh-kernel.org>
18 中文版维护者： 钟宇 TripleX Chung <triplex@zh-kernel.org>
19 中文版翻译者： 钟宇 TripleX Chung <triplex@zh-kernel.org>
20 中文版校译者： 李阳 Li Yang <leo@zh-kernel.org>
45 - 在确认了补丁符合以上的规则后，将补丁发送到stable@vger.kernel.org。
49 - 安全方面的补丁不要发到这个列表，应该发送到security@kernel.org。
55 到linux-kernel邮件列表。
57 - 如果委员会中有成员拒绝这个补丁，或者linux-kernel列表上有人反对这个
|
| D | SubmittingDrivers | 9 Chinese maintainer: Li Yang <leo@zh-kernel.org>
17 中文版维护者： 李阳 Li Yang <leo@zh-kernel.org>
18 中文版翻译者： 李阳 Li Yang <leo@zh-kernel.org>
62 除了遵循和 2.4 版内核同样的规则外，你还需要在 linux-kernel 邮件
136 ftp.??.kernel.org:/pub/linux/kernel/...
140 linux-kernel@vger.kernel.org
141 [可通过向majordomo@vger.kernel.org发邮件来订阅]
149 http://lwn.net/Articles/2.6-kernel-api/
|
| D | sparse.txt | 9 Chinese maintainer: Li Yang <leo@zh-kernel.org>
17 中文版维护者： 李阳 Li Yang <leo@zh-kernel.org>
18 中文版翻译者： 李阳 Li Yang <leo@zh-kernel.org>
70 http://www.kernel.org/pub/linux/kernel/people/josh/sparse/
74 git://git.kernel.org/pub/scm/linux/kernel/git/josh/sparse.git
|
| D | basic_profiling.txt | 35 http://www.kernel.org/pub/linux/utils/util-linux/ 下载
39 启用readprofile需要在kernel启动命令行增加”profile=2“
49 在kernel启动命令行增加“idle=poll”
51 配置CONFIG_PROFILING=y和CONFIG_OPROFILE=y然后重启进入新kernel
53 ./configure --with-kernel-support
68 如果只看kernel相关的报告结果，请运行命令 opreport -l /boot/vmlinux > output_file
|
| /linux-4.4.14/Documentation/kdump/ |
| D | kdump.txt | 11 Kdump uses kexec to quickly boot to a dump-capture kernel whenever a
12 dump of the system kernel's memory needs to be taken (for example, when
13 the system panics). The system kernel's memory image is preserved across
14 the reboot and is accessible to the dump-capture kernel.
23 When the system kernel boots, it reserves a small section of memory for
24 the dump-capture kernel. This ensures that ongoing Direct Memory Access
25 (DMA) from the system kernel does not corrupt the dump-capture kernel.
26 The kexec -p command loads the dump-capture kernel into this reserved
30 regardless of where the kernel loads. Therefore, kexec backs up this
31 region just before rebooting into the dump-capture kernel.
[all …]
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | .kernel-api.xml.cmd | 1 …entation/DocBook/kernel-api.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/kernel-a…
2 …kernel-api.xml: Documentation/DocBook/kernel-api.tmpl include/linux/list.h lib/vsprintf.c include/…
|
| D | .kernel-locking.xml.cmd | 1 …tion/DocBook/kernel-locking.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/kernel-l…
2 …cumentation/DocBook/kernel-locking.xml: Documentation/DocBook/kernel-locking.tmpl include/linux/mu…
|
| D | .genericirq.xml.cmd | 2 …kernel/irq/generic-chip.c include/linux/irq.h include/linux/interrupt.h kernel/irq/manage.c kernel…
|
| D | .kernel-hacking.xml.cmd | 1 …tion/DocBook/kernel-hacking.xml := SRCTREE=./ ./scripts/docproc doc Documentation/DocBook/kernel-h…
2 Documentation/DocBook/kernel-hacking.xml: Documentation/DocBook/kernel-hacking.tmpl
|
| D | .device-drivers.xml.cmd | 2 …kernel/sched/core.c kernel/sched/cpupri.c kernel/sched/fair.c include/linux/completion.h kernel/ti…
|
| /linux-4.4.14/Documentation/ABI/testing/ |
| D | sysfs-kernel-livepatch | 1 What: /sys/kernel/livepatch
4 Contact: live-patching@vger.kernel.org
6 Interface for kernel live patching
8 The /sys/kernel/livepatch directory contains subdirectories for
11 What: /sys/kernel/livepatch/<patch>
14 Contact: live-patching@vger.kernel.org
16 The patch directory contains subdirectories for each kernel
19 What: /sys/kernel/livepatch/<patch>/enabled
22 Contact: live-patching@vger.kernel.org
28 What: /sys/kernel/livepatch/<patch>/<object>
[all …]
|
| D | sysfs-kernel-mm-ksm | 1 What: /sys/kernel/mm/ksm
7 What: /sys/kernel/mm/ksm/full_scans
8 What: /sys/kernel/mm/ksm/pages_shared
9 What: /sys/kernel/mm/ksm/pages_sharing
10 What: /sys/kernel/mm/ksm/pages_to_scan
11 What: /sys/kernel/mm/ksm/pages_unshared
12 What: /sys/kernel/mm/ksm/pages_volatile
13 What: /sys/kernel/mm/ksm/run
14 What: /sys/kernel/mm/ksm/sleep_millisecs
45 What: /sys/kernel/mm/ksm/merge_across_nodes
|
| D | sysfs-bus-event_source-devices-events | 13 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
32 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
69 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
81 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
86 recieved from the kernel to match the unit specified in the
94 in the kernel.
|
| D | debugfs-driver-genwqe | 1 What: /sys/kernel/debug/genwqe/genwqe<n>_card/ddcb_info
6 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_regs
12 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid0
18 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid1
24 What: /sys/kernel/debug/genwqe/genwqe<n>_card/curr_dbg_uid2
30 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_regs
37 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid0
43 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid1
49 What: /sys/kernel/debug/genwqe/genwqe<n>_card/prev_dbg_uid2
55 What: /sys/kernel/debug/genwqe/genwqe<n>_card/info
[all …]
|
| D | sysfs-class-powercap | 4 Contact: linux-pm@vger.kernel.org
13 Contact: linux-pm@vger.kernel.org
22 Contact: linux-pm@vger.kernel.org
30 Contact: linux-pm@vger.kernel.org
40 Contact: linux-pm@vger.kernel.org
51 Contact: linux-pm@vger.kernel.org
58 Contact: linux-pm@vger.kernel.org
67 Contact: linux-pm@vger.kernel.org
75 Contact: linux-pm@vger.kernel.org
82 Contact: linux-pm@vger.kernel.org
[all …]
|
| D | sysfs-class-net-statistics | 4 Contact: netdev@vger.kernel.org
12 Contact: netdev@vger.kernel.org
20 Contact: netdev@vger.kernel.org
29 Contact: netdev@vger.kernel.org
38 Contact: netdev@vger.kernel.org
47 Contact: netdev@vger.kernel.org
57 Contact: netdev@vger.kernel.org
66 Contact: netdev@vger.kernel.org
76 Contact: netdev@vger.kernel.org
85 Contact: netdev@vger.kernel.org
[all …]
|
| D | sysfs-class-net | 4 Contact: netdev@vger.kernel.org
7 1: enumerated by the kernel, possibly in an unpredictable way
8 2: predictably named by the kernel
15 Contact: netdev@vger.kernel.org
26 Contact: netdev@vger.kernel.org
36 Contact: netdev@vger.kernel.org
45 Contact: netdev@vger.kernel.org
64 Contact: netdev@vger.kernel.org
73 Contact: netdev@vger.kernel.org
87 Contact: netdev@vger.kernel.org
[all …]
|
| D | sysfs-devices-system-cpu | 3 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
8 named by the kernel's logical CPU number, e.g.:
18 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
19 Description: CPU topology files that describe kernel limits related to
22 kernel_max: the maximum cpu index allowed by the kernel
27 kernel configuration (kernel_max above).
43 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
77 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
87 hardware platform's identifier (rather than the kernel's).
90 core_siblings: internal kernel map of cpu#'s hardware threads
[all …]
|
| D | sysfs-kernel-slab | 1 What: /sys/kernel/slab
7 The /sys/kernel/slab directory contains a snapshot of the
11 Users: kernel memory tuning tools
13 What: /sys/kernel/slab/cache/aliases
22 What: /sys/kernel/slab/cache/align
31 What: /sys/kernel/slab/cache/alloc_calls
37 The alloc_calls file is read-only and lists the kernel code
42 What: /sys/kernel/slab/cache/alloc_fastpath
53 What: /sys/kernel/slab/cache/alloc_from_partial
65 What: /sys/kernel/slab/cache/alloc_refill
[all …]
|
| D | sysfs-memory-page-offline | 8 physical address of the page. The kernel will then attempt
10 dropping it if possible. The kernel will then be placed
13 The offlining is done in kernel specific granuality.
14 Normally it's the base page size of the kernel, but
18 kernel will never kill anything for this, but rather
31 kernel will then attempt to hard-offline the page, by
34 any processes owning the page. The kernel will avoid
38 The offlining is done in kernel specific granuality.
39 Normally it's the base page size of the kernel, but
|
| D | sysfs-class-uwb_rc | 4 Contact: linux-usb@vger.kernel.org
24 Contact: linux-usb@vger.kernel.org
31 Contact: linux-usb@vger.kernel.org
49 Contact: linux-usb@vger.kernel.org
62 Contact: linux-usb@vger.kernel.org
78 Contact: linux-usb@vger.kernel.org
88 Contact: linux-usb@vger.kernel.org
96 Contact: linux-usb@vger.kernel.org
105 Contact: linux-usb@vger.kernel.org
114 Contact: linux-usb@vger.kernel.org
[all …]
|
| D | sysfs-class-net-queues | 4 Contact: netdev@vger.kernel.org
14 Contact: netdev@vger.kernel.org
22 Contact: netdev@vger.kernel.org
30 Contact: netdev@vger.kernel.org
38 Contact: netdev@vger.kernel.org
48 Contact: netdev@vger.kernel.org
57 Contact: netdev@vger.kernel.org
65 Contact: netdev@vger.kernel.org
74 Contact: netdev@vger.kernel.org
83 Contact: netdev@vger.kernel.org
|
| D | sysfs-platform-ts5500 | 4 Contact: "Savoir-faire Linux Inc." <kernel@savoirfairelinux.com>
12 Contact: "Savoir-faire Linux Inc." <kernel@savoirfairelinux.com>
20 Contact: "Savoir-faire Linux Inc." <kernel@savoirfairelinux.com>
27 Contact: "Savoir-faire Linux Inc." <kernel@savoirfairelinux.com>
36 Contact: "Savoir-faire Linux Inc." <kernel@savoirfairelinux.com>
43 Contact: "Savoir-faire Linux Inc." <kernel@savoirfairelinux.com>
51 Contact: "Savoir-faire Linux Inc." <kernel@savoirfairelinux.com>
|
| D | sysfs-devices-edac | 3 Contact: linux-edac@vger.kernel.org
9 at driver initialization time, no module/kernel parameter
14 Contact: linux-edac@vger.kernel.org
21 Contact: linux-edac@vger.kernel.org
27 Contact: linux-edac@vger.kernel.org
33 Contact: linux-edac@vger.kernel.org
41 Contact: linux-edac@vger.kernel.org
48 Contact: linux-edac@vger.kernel.org
58 Contact: linux-edac@vger.kernel.org
68 Contact: linux-edac@vger.kernel.org
[all …]
|
| D | sysfs-kernel-boot_params | 1 What: /sys/kernel/boot_params
4 Description: The /sys/kernel/boot_params directory contains two
6 It is used to export the kernel boot parameters of an x86
18 structure in boot_params. setup_data is maintained in kernel
27 /sys/kernel/boot_params
|
| D | sysfs-kernel-mm | 1 What: /sys/kernel/mm
5 /sys/kernel/mm/ should contain any and all VM
6 related information in /sys/kernel/.
|
| D | sysfs-driver-wacom | 4 Contact: linux-bluetooth@vger.kernel.org
14 Contact: linux-input@vger.kernel.org
25 Contact: linux-input@vger.kernel.org
34 Contact: linux-input@vger.kernel.org
42 Contact: linux-input@vger.kernel.org
51 Contact: linux-input@vger.kernel.org
59 Contact: linux-input@vger.kernel.org
66 Contact: linux-input@vger.kernel.org
83 Contact: linux-input@vger.kernel.org
92 Contact: linux-input@vger.kernel.org
|
| D | debugfs-pktcdvd | 1 What: /sys/kernel/debug/pktcdvd/pktcdvd[0-7]
13 /sys/kernel/debug/pktcdvd/pktcdvd[0-7]/
19 cat /sys/kernel/debug/pktcdvd/pktcdvd0/info
|
| /linux-4.4.14/Documentation/watchdog/ |
| D | watchdog-parameters.txt | 7 See Documentation/kernel-parameters.txt for information on
8 providing kernel parameters for builtin drivers versus loadable
17 (default=kernel config parameter)
24 (default=kernel config parameter)
29 (default=kernel config parameter)
36 (default=kernel config parameter)
41 (default=kernel config parameter)
46 (default=kernel config parameter)
51 (default=kernel config parameter)
56 (default=kernel config parameter)
[all …]
|
| /linux-4.4.14/Documentation/wimax/ |
| D | README.i2400m | 7 and a basic Linux kernel WiMAX stack.
11 * Linux installation with Linux kernel 2.6.22 or newer (if building
16 + Linux kernel development package for the target kernel; to
17 build against your currently running kernel, you need to have
18 the kernel development package corresponding to the running
19 image installed (usually if your kernel is named
26 2.1. Compilation of the drivers included in the kernel
28 Configure the kernel; to enable the WiMAX drivers select Drivers >
32 If USB or SDIO are not enabled in the kernel configuration, the options
36 Compile and install your kernel as usual.
[all …]
|
| D | README.wimax | 2 Linux kernel WiMAX stack
6 This provides a basic Linux kernel WiMAX stack to provide a common
7 control API for WiMAX devices, usable from kernel and user space.
39 files will appear in /sys/kernel/debug/wimax:wmxX can tweak for
59 # find /sys/kernel/debug/wimax\:wmx0 -name \*dl_\*
60 /sys/kernel/debug/wimax:wmx0/wimax_dl_stack
61 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_rfkill
62 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_reset
63 /sys/kernel/debug/wimax:wmx0/wimax_dl_op_msg
64 /sys/kernel/debug/wimax:wmx0/wimax_dl_id_table
[all …]
|
| /linux-4.4.14/ |
| D | README | 1 Linux kernel release 4.x <http://kernel.org/>
5 kernel, and what to do if something goes wrong.
34 Linux has also been ported to itself. You can now run the kernel as a
47 these typically contain kernel-specific installation notes for some
51 your kernel.
54 kernel developers and users. These guides can be rendered in a
59 INSTALLING the kernel source:
61 - If you install the full sources, put the kernel tarball in a
67 Replace "X" with the version number of the latest kernel.
70 incomplete) set of kernel headers that are used by the library header
[all …]
|
| D | MAINTAINERS | 3 List of maintainers and how to submit kernel changes
13 them onto the kernel channel and await results. This is especially
22 module and built into the kernel.
34 generalized kernel feature ready for next time.
64 please Cc: security@kernel.org, especially if the maintainer
129 L: netdev@vger.kernel.org
136 L: netdev@vger.kernel.org
142 L: linux-scsi@vger.kernel.org
149 L: linux-scsi@vger.kernel.org
156 L: linux-bluetooth@vger.kernel.org
[all …]
|
| D | REPORTING-BUGS | 4 The upstream Linux kernel maintainers only fix bugs for specific kernel
6 kernel, any "stable" kernel versions, and any "long term" kernels.
8 Please see https://www.kernel.org/ for a list of supported kernels. Any
9 kernel marked with [EOL] is "end of life" and will not have any fixes
12 If you've found a bug on a kernel version isn't listed on kernel.org,
16 to reproduce the bug on the latest -rc kernel.
19 How to report Linux kernel bugs
26 Identifying which part of the Linux kernel might be causing your issue
28 generic linux-kernel mailing list (LKML) may cause your bug report to be
31 Instead, try to figure out which kernel subsystem is causing the issue,
[all …]
|
| D | Kbuild | 2 # Kbuild for top-level directory of the kernel
40 targets := kernel/bounds.s
43 kernel/bounds.s: kernel/bounds.c FORCE
47 $(obj)/$(bounds-file): kernel/bounds.s FORCE
65 $(obj)/$(timeconst-file): kernel/time/timeconst.bc FORCE
75 targets += arch/$(SRCARCH)/kernel/asm-offsets.s
78 arch/$(SRCARCH)/kernel/asm-offsets.s: arch/$(SRCARCH)/kernel/asm-offsets.c \
83 $(obj)/$(offsets-file): arch/$(SRCARCH)/kernel/asm-offsets.s FORCE
|
| /linux-4.4.14/Documentation/fault-injection/ |
| D | fault-injection.txt | 31 debugfs entries under /sys/kernel/debug/mmc0/fail_mmc_request
38 fault-inject-debugfs kernel module provides some debugfs entries for runtime
41 - /sys/kernel/debug/fail*/probability:
48 /sys/kernel/debug/fail*/interval for such testcases.
50 - /sys/kernel/debug/fail*/interval:
58 - /sys/kernel/debug/fail*/times:
63 - /sys/kernel/debug/fail*/space:
69 - /sys/kernel/debug/fail*/verbose
77 - /sys/kernel/debug/fail*/task-filter:
84 - /sys/kernel/debug/fail*/require-start:
[all …]
|
| D | notifier-error-inject.txt | 6 notifier call chain failures which is rarely executed. There are kernel
21 /sys/kernel/debug/notifier-error-inject/cpu/actions/<notifier event>/error
32 # cd /sys/kernel/debug/notifier-error-inject/cpu
46 /sys/kernel/debug/notifier-error-inject/pm/actions/<notifier event>/error
56 # cd /sys/kernel/debug/notifier-error-inject/pm/
64 /sys/kernel/debug/notifier-error-inject/memory/actions/<notifier event>/error
73 # cd /sys/kernel/debug/notifier-error-inject/memory
81 /sys/kernel/debug/notifier-error-inject/pSeries-reconfig/actions/<notifier event>/error
|
| /linux-4.4.14/arch/arm64/ |
| D | Kconfig.debug | 6 bool "Export kernel pagetable layout to userspace via debugfs"
10 Say Y here if you want to show the kernel pagetable layout in a
11 debugfs file. This information is only useful for kernel developers
12 who are working in architecture specific areas of the kernel.
14 kernel.
22 of memory, including kernel and userspace memory. Accidental
24 be used by people debugging the kernel.
34 Enabling this option causes the kernel to write the current PID to
37 planning to use hardware trace tools with this kernel.
43 of the kernel to be randomized at build-time. When selected,
[all …]
|
| /linux-4.4.14/Documentation/ |
| D | HOWTO | 1 HOWTO do Linux kernel development
5 instructions on how to become a Linux kernel developer and how to learn
6 to work with the Linux kernel development community. It tries to not
7 contain anything related to the technical aspects of kernel programming,
18 So, you want to learn how to become a Linux kernel developer? Or you
25 The kernel is written mostly in C, with some architecture-dependent
27 kernel development. Assembly (any architecture) is not required unless
35 The kernel is written using GNU C and the GNU toolchain. While it
37 not featured in the standard. The kernel is a freestanding C
41 difficult to understand the assumptions the kernel has on the toolchain
[all …]
|
| D | lockup-watchdogs.txt | 5 The Linux kernel can act as a watchdog to detect both soft and hard
8 A 'softlockup' is defined as a bug that causes the kernel to loop in
9 kernel mode for more than 20 seconds (see "Implementation" below for
12 will stay locked up. Alternatively, the kernel can be configured to
13 panic; a sysctl, "kernel.softlockup_panic", a kernel parameter,
14 "softlockup_panic" (see "Documentation/kernel-parameters.txt" for
19 kernel mode for more than 10 seconds (see "Implementation" below for
25 and a kernel parameter, "nmi_watchdog"
26 (see "Documentation/kernel-parameters.txt" for details).
29 timeout is set through the confusingly named "kernel.panic" sysctl),
[all …]
|
| D | oops-tracing.txt | 9 Find the Oops and send it to the maintainer of the kernel area that seems to be
16 linux-kernel@vger.kernel.org. Thanks for your help in making Linux as
22 Normally the Oops text is read from the kernel buffers by klogd and
25 in which case you can run dmesg > file to read the data from the kernel
45 extract the kernel ring buffer from old memory with using dmesg
52 NOTE: the message from Linus below applies to 2.4 kernel. I have preserved it
58 How to track down an Oops.. [originally a mail to linux-kernel]
74 Oh, it helps if the report happens on a kernel that is compiled with the
130 programs to search for specific patterns in the kernel code segment, and
132 that really requires pretty good knowledge of the kernel just to be able
[all …]
|
| D | stable_api_nonsense.txt | 7 kernel interface, nor does it have a stable kernel interface. Please
9 kernel to userspace interfaces. The kernel to userspace interface is
12 programs that were built on a pre 0.9something kernel that still work
13 just fine on the latest 2.6 kernel release. That interface is the one
19 You think you want a stable kernel interface, but you really do not, and
21 you get that only if your driver is in the main kernel tree. You also
22 get lots of other good benefits if your driver is in the main kernel
31 It's only the odd person who wants to write a kernel driver that needs
32 to worry about the in-kernel interfaces changing. For the majority of
38 that describes kernel drivers that do not have their source code
[all …]
|
| D | gcov.txt | 1 Using gcov with the Linux kernel
18 gcov profiling kernel support enables the use of GCC's coverage testing
19 tool gcov [1] with the Linux kernel. Coverage data of a running kernel
21 To get coverage data for a specific file, change to the kernel build
25 # gcov -o /sys/kernel/debug/gcov/tmp/linux-out/kernel spinlock.c
30 for the entire kernel and provide coverage overviews in HTML format.
36 * minimizing kernel configurations (do I need this option if the
48 Configure the kernel with:
57 and to get coverage data for the entire kernel:
68 mount -t debugfs none /sys/kernel/debug
[all …]
|
| D | kernel-doc-nano-HOWTO.txt | 1 kernel-doc nano-HOWTO
4 How to format kernel-doc comments
9 data structures in the Linux kernel, the Linux kernel has adopted
13 The format for this documentation is called the kernel-doc format.
14 It is documented in this Documentation/kernel-doc-nano-HOWTO.txt file.
17 a few simple conventions. The scripts/kernel-doc perl script, some
22 In order to provide good documentation of kernel functions and data
24 kernel-doc comments in Linux kernel source.
26 We definitely need kernel-doc formatted documentation for functions
29 We also look to provide kernel-doc formatted documentation for
[all …]
|
| D | applying-patches.txt | 10 a patch to the kernel or, more specifically, what base kernel a patch for
15 description of the different kernel trees (and examples of how to apply
35 Patches for the Linux kernel are generated relative to the parent directory
36 holding the kernel source dir.
39 kernel source directories it was generated against (or some other directory
41 Since this is unlikely to match the name of the kernel source dir on your
43 unlabeled patch was generated against) you should change into your kernel
124 If you don't have any third-party patches applied to your kernel source, but
125 only patches from kernel.org and you apply the patches in the correct order,
131 to start with a fresh tree downloaded in full from kernel.org.
[all …]
|
| D | stable_kernel_rules.txt | 15 - Serious issues as reported by a user of a distribution kernel may also
18 regression they should only be submitted by a distribution kernel
43 Cc: stable@vger.kernel.org
51 stable@vger.kernel.org containing the subject of the patch, the commit ID,
52 why you think it should be applied, and what kernel version you wish it to
58 stable@vger.kernel.org. You must note the upstream commit ID in the
59 changelog of your submission, as well as the kernel version you wish
66 to apply to an older kernel (e.g., if API's have changed in the meantime).
81 Cc: <stable@vger.kernel.org> # 3.3.x: a1f84a3: sched: Check for idle
82 Cc: <stable@vger.kernel.org> # 3.3.x: 1b9508f: sched: Rate-limit newidle
[all …]
|
| D | module-signing.txt | 10 - Public keys in the kernel.
22 The kernel module signing facility cryptographically signs modules during
24 allows increased kernel security by disallowing the loading of unsigned modules
26 making it harder to load a malicious module into the kernel. The module
27 signature checking is done by the kernel so that it is not necessary to have
43 Support" section of the kernel configuration and turning on
51 This specifies how the kernel should deal with a module that has a
55 available and modules that are unsigned are permitted, but the kernel will
60 signature that can be verified by a public key in the kernel's possession
87 The algorithm selected here will also be built into the kernel (rather
[all …]
|
| D | SubmittingDrivers | 5 various kernel trees. Note that if you are interested in video card drivers
19 be submitted to the mainstream kernel.
30 No new drivers are accepted for this kernel tree.
33 No new drivers are accepted for this kernel tree.
37 the maintainer listed in MAINTAINERS in the kernel file. If the
42 The same rules apply as 2.4 except that you should follow linux-kernel
121 or you did. Nobody has any special access to the kernel
129 Linux kernel master tree:
130 ftp.??.kernel.org:/pub/linux/kernel/...
133 http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git
[all …]
|
| D | kernel-docs.txt | 10 * http://www.dit.upm.es/~jmseyas/linux/kernel/hackers-docs.html
14 linux-kernel mailing list as the same questions, asking for pointers
46 programming API and kernel hacking in general. Available under the
81 Description: Conceptual software architecture of the Linux kernel,
83 figures. Gives good overall kernel understanding.
90 Description: Concrete architecture of the Linux kernel,
92 figures. Gives good overall kernel understanding. This papers
107 URL: http://www.mjmwired.net/kernel/Documentation/filesystems/vfs.txt
122 Linux kernel, providing users with high performance and reliable,
133 a practical approach to writing Linux device drivers as kernel
[all …]
|
| D | 00-INDEX | 16 - info on kernel <-> userspace ABI and relative interface stability.
23 - how the maintainers expect the C code in the kernel to look.
33 - directory with DocBook templates etc. for kernel documentation.
37 - the process and procedures of how to do Linux kernel development.
51 - how to (attempt to) manage kernel hackers.
59 - procedure for reporting security bugs found in the kernel.
61 - Linux kernel patch submission checklist.
63 - procedure to get a new driver source included into the kernel tree.
65 - procedure to get a source patch included into the kernel tree.
71 - info on ACPI-specific hooks in the kernel.
[all …]
|
| D | Changes | 20 running a Linux kernel. Also, not all tools are necessary on all
62 You will need GNU make 3.80 or later to build the kernel.
69 your kernel. This change does, however, mean that you need a recent
76 File::Basename, and File::Find to build the kernel.
102 (http://www.kernel.org/pub/linux/utils/kernel/hotplug/)
126 If the unthinkable happens and your kernel oopses, you may need the
128 It is generally preferred to build the kernel with CONFIG_KALLSYMS so
130 produces better output than ksymoops). If for some reason your kernel
138 A new module loader is now in the kernel that requires module-init-tools
177 work correctly with this version of the XFS kernel code (2.6.0 or
[all …]
|
| D | robust-futex-ABI.txt | 7 futexes, for kernel assist of cleanup of held locks on task exit.
11 are taken and dropped, without kernel intervention. The only additional
12 kernel intervention required for robust_futexes above and beyond what is
15 1) a one time call, per thread, to tell the kernel where its list of
17 2) internal kernel code at exit, to handle any listed locks held
23 threads in the kernel. Options on the sys_futex(2) system call support
29 necessary list elements exactly as the kernel expects them. If it fails
46 kernel, then it can actually have two such structures - one using 32 bit
48 bit native mode. The kernel, if it is a 64 bit kernel supporting 32 bit
79 robust_futexes. The kernel will only be able to wakeup the next thread
[all …]
|
| D | xz.txt | 18 the Linux kernel.
24 XZ related components in the kernel
37 For decompressing the kernel image, initramfs, and initrd, there
44 for compressing the kernel image.
46 For kernel makefiles, two commands are provided for use with
47 $(call if_needed). The kernel image should be compressed with
58 when encoding files that are supposed to be decoded by the kernel. With
73 by the kernel. 1 MiB is probably the maximum reasonable dictionary
74 size for in-kernel use (maybe more is OK for initramfs). The presets
75 in XZ Utils may not be optimal when creating files for the kernel,
[all …]
|
| D | efi-stub.txt | 4 On the x86 and ARM platforms, a kernel zImage/bzImage can masquerade
15 For arm64, there is no compressed kernel support, so the Image itself
17 kernel. The arm64 EFI stub lives in arch/arm64/kernel/efi-entry.S
18 and arch/arm64/kernel/efi-stub.c.
20 By using the EFI boot stub it's possible to boot a Linux kernel
25 The EFI boot stub is enabled with the CONFIG_EFI_STUB kernel option.
40 **** Passing kernel parameters from the EFI shell
42 Arguments to the kernel can be passed after bzImage.efi, e.g.
52 kernel when it boots.
82 device tree to the kernel. This is done with the "dtb=" command line option,
|
| D | kmemleak.txt | 7 Kmemleak provides a way of detecting possible kernel memory leaks in a
11 reported via /sys/kernel/debug/kmemleak. A similar method is used by the
19 CONFIG_DEBUG_KMEMLEAK in "Kernel hacking" has to be enabled. A kernel
24 # mount -t debugfs nodev /sys/kernel/debug/
25 # cat /sys/kernel/debug/kmemleak
29 # echo scan > /sys/kernel/debug/kmemleak
33 # echo clear > /sys/kernel/debug/kmemleak
35 New leaks will then come up upon reading /sys/kernel/debug/kmemleak
43 /sys/kernel/debug/kmemleak file. The following parameters are supported:
59 the kernel command line.
[all …]
|
| D | intel_txt.txt | 39 Trusted Boot (tboot) is an open source, pre-kernel/VMM module that
41 kernel/VMM.
55 measure or protect the integrity of a running kernel, they all
56 assume the kernel is "good" to begin with. The Integrity
60 To get trust in the initial kernel without using Intel TXT, a
63 executed between system reset through the completion of the kernel
65 Linux kernel, this means all of BIOS, any option ROMs, the
91 the "kernel" (the binary the bootloader executes).
97 incorrect), it will directly launch the kernel with no changes
114 special code into the kernel's MP wakeup sequence.
[all …]
|
| D | gdb-kernel-debugging.txt | 1 Debugging kernel and modules via gdb
4 The kernel debugger kgdb, hypervisors like QEMU or JTAG-based hardware
5 interfaces allow to debug the Linux kernel and its modules during runtime
7 kernel provides a collection of helper scripts that can simplify typical
8 kernel debugging steps. This is a short tutorial about how to enable and use
28 o Build the kernel with CONFIG_GDB_SCRIPTS enabled, but leave
32 o Install that kernel on the guest.
34 Alternatively, QEMU allows to boot the kernel directly using -kernel,
63 o Load module (and main kernel) symbols:
94 o Dump the log buffer of the target kernel:
[all …]
|
| D | BUG-HUNTING | 19 Always try the latest kernel from kernel.org and build from source. If you are
21 instead of to a kernel developer.
33 kernel.
47 - start using git for the kernel source
56 This is how to track down a bug if you know nothing about kernel hacking.
62 . All the kernel tar files from a revision that worked to the
70 you know that 1.3.69 does. Pick a kernel in the middle and build
73 . You'll narrow it down to the kernel that introduced the bug. You
78 - Copy kernel that works into "test". Let's say that 3.62 works,
132 Finally, you take all the info that you have, kernel revisions, bug
[all …]
|
| D | SecurityBugs | 1 Linux kernel developers take security very seriously. As such, we'd
4 Linux kernel security team.
8 The Linux kernel security team can be contacted by email at
9 <security@kernel.org>. This is a private list of security officers
22 The goal of the Linux kernel security team is to work with the
29 bug submitter as well as vendors. However, the kernel security team
37 The Linux kernel security team is not a formal body and therefore unable
|
| D | basic_profiling.txt | 18 http://www.kernel.org/pub/linux/utils/util-linux/
22 Add "profile=2" to the kernel command line.
32 http://oprofile.sourceforge.net/ and add "idle=poll" to the kernel command
35 Configure with CONFIG_PROFILING=y and CONFIG_OPROFILE=y & reboot on new kernel
37 ./configure --with-kernel-support
53 To only report on the kernel, run opreport -l /boot/vmlinux > output_file
|
| D | sysfs-rules.txt | 1 Rules on how to access information in the Linux kernel sysfs
3 The kernel-exported sysfs exports internal kernel implementation details
4 and depends on internal kernel structures and layout. It is agreed upon
5 by the kernel developers that the Linux kernel does not provide a stable
7 may not be stable across kernel releases.
10 low-level userspace applications, with a new kernel release, the users
22 offer any abstraction, it exposes all the kernel driver-core
26 current kernel development. The goal of providing a stable interface
41 kernel implementation details which should not be expected by
46 - identical to the DEVPATH value in the event sent from the kernel
[all …]
|
| D | cputopology.txt | 14 identifier (rather than the kernel's). The actual value is
20 identifier (rather than the kernel's). The actual value is
25 internal kernel map of cpuX's hardware threads within the same
35 internal kernel map of cpuX's hardware threads within the same
45 internal kernel map of cpuX's hardware threads within the same
86 kernel_max: the maximum CPU index allowed by the kernel configuration.
91 of CPUs allowed by the kernel configuration (kernel_max
106 the kernel max which is limited to 0..31 by the NR_CPUS config option
116 In this example, the NR_CPUS config option is 128, but the kernel was
127 See cpu-hotplug.txt for the possible_cpus=NUM kernel start parameter
|
| /linux-4.4.14/arch/arm/mach-orion5x/ |
| D | Kconfig | 14 Say 'Y' here if you want your kernel to support the
21 Say 'Y' here if you want your kernel to support the
28 Say 'Y' here if you want your kernel to support the
36 Say 'Y' here if you want your kernel to support the Marvell
43 Say 'Y' here if you want your kernel to support the
51 Say 'Y' here if you want your kernel to support the
58 Say 'Y' here if you want your kernel to support the
64 Say 'Y' here if you want your kernel to support the
71 Say 'Y' here if you want your kernel to support the
79 Say 'Y' here if you want your kernel to support the
[all …]
|
| /linux-4.4.14/Documentation/development-process/ |
| D | 8.Conclusion | 3 There are numerous sources of information on Linux kernel development and
5 directory found in the kernel source distribution. The top-level HOWTO
7 SubmittingDrivers are also something which all kernel developers should
8 read. Many internal kernel APIs are documented using the kerneldoc
14 Various web sites discuss kernel development at all levels of detail. Your
16 information on many specific kernel topics can be found via the LWN kernel
21 Beyond that, a valuable resource for kernel developers is:
25 And, of course, one should not forget http://kernel.org/, the definitive
26 location for kernel release information.
28 There are a number of books on kernel development:
[all …]
|
| D | 1.Intro | 6 accessible to those who are not intimately familiar with Linux kernel
9 discussion which does not require a deep knowledge of kernel programming to
15 The rest of this section covers the scope of the kernel development process
17 encounter there. There are a great many reasons why kernel code should be
18 merged into the official ("mainline") kernel, including automatic
20 influence the direction of kernel development. Code contributed to the
21 Linux kernel must be made available under a GPL-compatible license.
23 Section 2 introduces the development process, the kernel release cycle, and
27 with kernel development are encouraged to track down and fix bugs as an
36 which can help to ensure that kernel patches are correct.
[all …]
|
| D | 2.Process | 3 Linux kernel development in the early 1990's was a pretty loose affair,
6 course of one year, the kernel has since had to evolve a number of
13 The kernel developers use a loosely time-based release process, with a new
14 major kernel release happening every two or three months. The recent
24 Every 2.6.x release is a major kernel release with new features, internal
27 thus the leading edge of Linux kernel development; the kernel uses a
34 community) is merged into the mainline kernel. The bulk of changes for a
46 first of the "rc" kernels. For the kernel which is destined to be 2.6.40,
50 kernel has begun.
64 will get up to somewhere between -rc6 and -rc9 before the kernel is
[all …]
|
| D | 3.Early-stage | 3 When contemplating a Linux kernel development project, it can be tempting
12 Like any engineering project, a successful kernel enhancement starts with a
21 kernel module intended to hook into the Linux Security Module (LSM)
24 the linux-kernel mailing list, where it immediately ran into problems.
27 immediate problem. To the wider kernel community, though, it was seen as a
37 entire kernel development process; one of them went back to an audio list
40 There are a number of very good Linux kernel developers, but they
47 The reality of the situation was different; the kernel developers were far
54 So, when contemplating a kernel development project, one should obtain
62 - How does the kernel fall short in addressing that problem now?
[all …]
|
| D | 4.Coding | 4 process, the proof of any kernel development project is in the resulting
10 number of ways in which kernel developers can go wrong. Then the focus
19 The kernel has long had a standard coding style, described in
22 a substantial amount of code in the kernel which does not meet the coding
24 hazards for kernel developers.
26 The first of these is to believe that the kernel coding standards do not
28 code to the kernel is very difficult if that code is not coded according to
30 before they will even review it. A code base as large as the kernel
35 Occasionally, the kernel's coding style will run into conflict with an
36 employer's mandated style. In such cases, the kernel's style will have to
[all …]
|
| /linux-4.4.14/arch/arm/mach-ep93xx/ |
| D | Kconfig | 14 Enable kernel support for MaverickCrunch.
21 Say 'Y' here if you want your kernel to support the ADS
31 Say 'Y' here if you want your kernel to support the Cirrus
38 Say 'Y' here if you want your kernel to support the Cirrus
45 Say 'Y' here if you want your kernel to support the Cirrus
52 Say 'Y' here if you want your kernel to support the Cirrus
59 Say 'Y' here if you want your kernel to support the Cirrus
66 Say 'Y' here if you want your kernel to support the Cirrus
73 Say 'Y' here if you want your kernel to support the Cirrus
80 Say 'Y' here if you want your kernel to support the Cirrus
[all …]
|
| /linux-4.4.14/Documentation/ja_JP/ |
| D | HOWTO | 114 linux-api@ver.kernel.org に送ることを勧めます。
153 "Linux kernel patch submission format"
184 Documentation/kernel-docs.txt
224 ニティに参加して何かすることをさがしている場合には、Linux kernel
238 http://selenic.com/mailman/listinfo/kernel-mentors
265 3.x カーネルは Linus Torvalds によってメンテナンスされ、kernel.org
266 の pub/linux/kernel/v3.x/ ディレクトリに存在します。この開発プロセスは
294 に作り込まれた問題を指す) はその都度 Linux-kernel メーリングリスト
299 Andrew Morton が Linux-kernel メーリングリストにカーネルリリースについ
318 3.x.y は "stable" チーム <stable@vger.kernel.org> でメンテされており、必
[all …]
|
| D | stable_kernel_rules.txt | 53 - 上記の規則に従っているかを確認した後に、stable@vger.kernel.org にパッチ
60 - パッチに stable@vger.kernel.org のアドレスが付加されているときには、それ
62 - セキュリティパッチはこのエイリアス (stable@vger.kernel.org) に送られるべ
63 きではなく、代わりに security@kernel.org のアドレスに送られる。
69 い限り)に送られ、linux-kernel メーリングリストにCCされる。
72 かなかった問題が持ちあがり、linux-kernel メンバがパッチに異議を唱え
78 この手続きの詳細については kernel security チームに問い合わせること。
|
| /linux-4.4.14/Documentation/arm64/ |
| D | memory.txt | 7 Linux kernel. The architecture allows up to 4 levels of translation
12 (256TB) virtual addresses, respectively, for both user and kernel. With
16 User addresses have bits 63:48 set to 0 while the kernel addresses have
18 virtual address. The swapper_pg_dir contains only kernel (global)
29 ffffff8000000000 ffffffffffffffff 512GB kernel
37 ffff000000000000 ffffffffffffffff 256TB kernel
45 fffffc0000000000 ffffffffffffffff 4TB kernel
53 ffff000000000000 ffffffffffffffff 256TB kernel
56 For details of the virtual kernel memory layout please see the kernel
89 When using KVM, the hypervisor maps kernel pages in EL2, at a fixed
[all …]
|
| D | booting.txt | 8 is relevant to all public releases of the AArch64 Linux kernel.
17 is passed to the Linux kernel. This may include secure monitor and
26 3. Decompress the kernel image
27 4. Call the kernel image
36 kernel will use for volatile data storage in the system. It performs
54 the 512 MB region starting at text_offset bytes below the kernel Image.
56 3. Decompress the kernel image
61 The AArch64 kernel does not currently provide a decompressor and
68 4. Call the kernel image
73 The decompressed kernel image contains a 64-byte header as follows:
[all …]
|
| /linux-4.4.14/Documentation/ko_KR/ |
| D | HOWTO | 126 "Linux kernel patch submission format"
157 Documentation/kernel-docs.txt
205 만들어진 kernel-mentors 프로젝트가 있다. 그곳은 메일링 리스트이며
207 http://selenic.com/mailman/listinfo/kernel-mentors
234 3.x 커널들은 Linux Torvalds가 관리하며 kernel.org의 pub/linux/kernel/v3.x/
278 3.x.y는 "stable" 팀<stable@vger.kernel.org>에 의해 관리되며 거의 매번 격주로
305 파일에 나열되어 있다. 대부분은 http://git.kernel.org 에서 볼 수 있다.
312 대부분의 이러한 patchwork 사이트는 http://patchwork.kernel.org/ 또는
320 http://git.kernel.org/?p=linux/kernel/git/sfr/linux-next.git
329 bugzilla.kernel.org는 리눅스 커널 개발자들이 커널의 버그를 추적하는 곳이다.
[all …]
|
| /linux-4.4.14/arch/hexagon/lib/ |
| D | memcpy.S | 177 #define kernel R4 /* number of 32byte chunks in kernel */ macro
257 kernel = sub(len, prolog); define
264 epilog = and(kernel, #31);
270 kernel = lsr(kernel, #5); define
281 nokernel = cmp.eq(kernel,#0);
290 p2 = cmp.eq(kernel, #1); /* skip ovr if kernel == 0 */
353 p3 = cmp.gtu(kernel, #0);
355 if(p3.new) kernel = add(kernel, #-1);
360 nokernel = cmp.eq(kernel, #0); /* after adjustment, recheck */
369 loop0(.Loword_loop_25to31, kernel);
[all …]
|
| /linux-4.4.14/arch/nios2/ |
| D | Kconfig | 51 source "kernel/Kconfig.preempt"
53 source "kernel/Kconfig.freezer"
55 source "kernel/Kconfig.hz"
64 The kernel memory allocator divides physically contiguous memory
66 pages. This option selects the largest power of two that the kernel
100 bool "Default bootloader kernel arguments"
104 string "Default kernel command string"
109 pass arguments to the kernel. For these platforms, you can supply
111 other cases you can specify kernel args so that you don't have
115 bool "Force default kernel command string"
[all …]
|
| /linux-4.4.14/Documentation/kbuild/ |
| D | headers_install.txt | 1 Exporting kernel headers for use by userspace
4 The "make headers_install" command exports the kernel's header files in a
7 The linux kernel's exported header files describe the API for user space
8 programs attempting to use kernel services. These kernel header files are
11 system calls. The C library's header files include the kernel header files
13 installed at the default location /usr/include and the kernel headers in
18 means that a program built against a C library using older kernel headers
19 should run on a newer kernel (although it may not have access to new
20 features), but a program built against newer kernel headers may not work on an
21 older kernel.
[all …]
|
| D | modules.txt | 3 This document describes how to build an out-of-tree kernel module.
36 "kbuild" is the build system used by the Linux kernel. Modules must use
53 To build external modules, you must have a prebuilt kernel available
55 Also, the kernel must have been built with modules enabled. If you are
56 using a distribution kernel, there will be a package for the kernel you
60 make sure the kernel contains the information required. The target
61 exists solely as a simple way to prepare a kernel source tree for
65 CONFIG_MODVERSIONS is set; therefore, a full kernel build needs to be
77 To build against the running kernel use:
88 ($KDIR refers to the path of the kernel source directory.)
[all …]
|
| /linux-4.4.14/Documentation/arm/ |
| D | Booting | 10 program that runs before the main kernel. The boot loader is expected
11 to initialise various devices, and eventually call the Linux kernel,
12 passing information to the kernel.
20 4. Setup the kernel tagged list.
22 6. Call the kernel image.
32 kernel will use for volatile data storage in the system. It performs
46 target. This allows the kernel serial driver to automatically detect
47 which serial port it should use for the kernel console (generally
51 option to the kernel via the tagged lists specifying the port, and
54 Documentation/kernel-parameters.txt.
[all …]
|
| D | kernel_mode_neon.txt | 19 code that runs in kernel mode. However, for performance reasons, the NEON/VFP
35 instruction is issued, allowing the kernel to step in and perform the restore if
38 Any use of the NEON/VFP unit in kernel mode should not interfere with this, so
42 should be called before any kernel mode NEON or VFP instructions are issued.
48 Interruptions in kernel mode
51 preserve/restore mechanism for the kernel mode NEON/VFP register contents. This
52 implies that interruptions of a kernel mode NEON section can only be allowed if
54 following rules and restrictions apply in the kernel:
69 software assistance, it signals the kernel by raising an undefined instruction
70 exception. The kernel responds by inspecting the VFP control registers and the
[all …]
|
| D | Porting | 1 Taken from list archive at http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2001-July/00406…
20 the kernel at this address to start it booting. This doesn't have
30 This is the address where the decompressed kernel will be written,
35 The initial part of the kernel is carefully coded to be position
51 kernel various parameters about its execution environment.
61 Virtual start address of the first bank of RAM. During the kernel
74 basis by the kernel. I'll call this the user segment.
77 this the kernel segment.
83 Virtual start address of kernel, normally PAGE_OFFSET + 0x8000.
84 This is where the kernel image ends up. With the latest kernels,
[all …]
|
| D | uefi.txt | 13 makes it possible for the kernel to support additional features:
29 load the kernel directly from the UEFI shell, boot menu, or one of the
32 The kernel image built with stub support remains a valid kernel image for
35 UEFI kernel support on ARM
37 UEFI kernel support on the ARM architectures (arm and arm64) is only available
41 Instead, the kernel reads the UEFI memory map.
43 The stub populates the FDT /chosen node with (and the kernel scans for) the
|
| D | kernel_user_helpers.txt | 4 These are segment of kernel provided user code reachable from user space
5 at a fixed address in kernel memory. This is used to provide user space
6 with some operations which require kernel help because of unimplemented
9 too intimate with the kernel counter part to be left to user libraries.
12 words, the kernel reserves the right to change this code as needed without
30 of not using these kernel helpers if your compiled code is not going to
33 New helpers may be added over time, so an older kernel may be missing some
34 helpers present in a newer kernel. For this reason, programs must check
38 if the required helpers are not provided by the kernel version that
53 running kernel. User space may read this to determine the availability
[all …]
|
| D | memory.txt | 7 kernel uses for ARM processors. It indicates which regions are
12 kernel, and hardware devices.
63 PKMAP_BASE PAGE_OFFSET-1 Permanent kernel mappings
64 One way of mapping HIGHMEM pages into kernel
78 dereferences by both the kernel and user
82 in a non-bootable kernel, or may cause the kernel to (eventually) panic
85 Since future CPUs may impact the kernel mapping layout, user programs
|
| /linux-4.4.14/Documentation/ia64/ |
| D | README | 1 Linux kernel release 2.4.xx for the IA-64 Platform
5 ONLY, to get additional information about the Linux kernel also
6 read the original Linux README provided with the kernel.
8 INSTALLING the kernel:
10 - IA-64 kernel installation is the same as the other platforms, see
16 Compiling and running this kernel requires an IA-64 compliant GCC
21 CONFIGURING the kernel:
26 COMPILING the kernel:
28 - Compiling this kernel doesn't differ from other platform so read
|
| D | fsys.txt | 13 execution to the ia64 linux kernel. We call this mode the
16 - kernel mode:
18 switched over to kernel memory. The user-level state is saved
19 in a pt-regs structure at the top of the kernel memory stack.
22 Both the register stack and the kernel stack are in
29 state remains in the CPU registers and some kernel state may
36 - CPU registers may contain a mixture of user-level and kernel-level
37 state (it is the responsibility of the kernel to ensure that no
38 security-sensitive kernel-level state is leaked back to
50 than it is to running in kernel-mode. Of course, given that the
[all …]
|
| /linux-4.4.14/Documentation/powerpc/ |
| D | firmware-assisted-dump.txt | 21 for dump, with a single operation of echo 1 > /sys/kernel/fadump_release_mem.
22 - Once enabled through kernel boot parameter, fadump can be
23 started/stopped through /sys/kernel/fadump_registered interface (see
31 with a fresh copy of the kernel. In particular,
35 is immediately available to the running kernel. And therefore,
43 -- The first kernel registers the sections of memory with the
46 kernel during early boot.
54 that is required for a kernel to boot successfully when
61 kernel to boot successfully.
68 -- The freshly booted kernel will notice that there is a new
[all …]
|
| /linux-4.4.14/arch/powerpc/boot/ |
| D | zImage.ps3.lds.S | 7 .kernel:vmlinux.bin : { *(.kernel:vmlinux.bin) }
12 .kernel:dtb : { *(.kernel:dtb) }
17 .kernel:initrd : { *(.kernel:initrd) }
|
| D | wrapper | 33 kernel=
136 [ -z "$kernel" ] || usage
137 kernel="$1"
153 if [ -z "$kernel" ]; then
154 kernel=vmlinux
157 elfformat="`${CROSS}objdump -p "$kernel" | grep 'file format' | awk '{print $4}'`"
170 ksection=.kernel:vmlinux.strip
171 isection=.kernel:initrd
249 ksection=.kernel:vmlinux.bin
250 isection=.kernel:initrd
[all …]
|
| D | zImage.lds.S | 47 .kernel:dtb :
50 *(.kernel:dtb)
55 .kernel:vmlinux.strip :
58 *(.kernel:vmlinux.strip)
63 .kernel:initrd :
66 *(.kernel:initrd)
|
| D | README | 2 To extract the kernel vmlinux, System.map, .config or initrd from the zImage binary:
4 objcopy -j .kernel:vmlinux -O binary zImage vmlinux.gz
5 objcopy -j .kernel:System.map -O binary zImage System.map.gz
6 objcopy -j .kernel:.config -O binary zImage config.gz
7 objcopy -j .kernel:initrd -O binary zImage.initrd initrd.gz
|
| D | zImage.coff.lds.S | 23 *(.kernel:dtb)
27 *(.kernel:vmlinux.strip)
31 *(.kernel:initrd)
|
| /linux-4.4.14/arch/c6x/ |
| D | Kconfig | 40 bool "Build a big kernel"
43 This is sufficient for most kernels, but some kernel configurations
46 function calls with 32-bit range. This will make the kernel both
53 # Use the generic interrupt handling code in kernel/irq/
55 source "kernel/Kconfig.freezer"
58 bool "Default bootloader kernel arguments"
66 to pass arguments to the kernel. For these architectures, you should
71 bool "Force default kernel command string"
75 Set this to have arguments from the default kernel command string
79 bool "Build big-endian kernel"
[all …]
|
| /linux-4.4.14/drivers/staging/rdma/ehca/ |
| D | hcp_phyp.c | 60 galpas->kernel.fw_handle = hcall_map_page(paddr_kernel); in hcp_galpas_ctor()
61 if (!galpas->kernel.fw_handle) in hcp_galpas_ctor()
64 galpas->kernel.fw_handle = 0; in hcp_galpas_ctor()
73 if (galpas->kernel.fw_handle) { in hcp_galpas_dtor()
74 int ret = hcall_unmap_page(galpas->kernel.fw_handle); in hcp_galpas_dtor()
79 galpas->user.fw_handle = galpas->kernel.fw_handle = 0; in hcp_galpas_dtor()
|
| D | hipz_fns_core.h | 64 hipz_galpa_store_qp(qp->galpas.kernel, qpx_sqa, in hipz_update_sqa()
71 hipz_galpa_store_qp(qp->galpas.kernel, qpx_rqa, in hipz_update_rqa()
77 hipz_galpa_store_cq(cq->galpas.kernel, cqx_feca, in hipz_update_feca()
85 hipz_galpa_store_cq(cq->galpas.kernel, cqx_n0, in hipz_set_cqx_n0()
88 cqx_n0_reg = hipz_galpa_load_cq(cq->galpas.kernel, cqx_n0); in hipz_set_cqx_n0()
95 hipz_galpa_store_cq(cq->galpas.kernel, cqx_n1, in hipz_set_cqx_n1()
97 cqx_n1_reg = hipz_galpa_load_cq(cq->galpas.kernel, cqx_n1); in hipz_set_cqx_n1()
|
| /linux-4.4.14/Documentation/x86/ |
| D | boot.txt | 4 On the x86 platform, the Linux kernel uses a rather complicated boot
6 well as the desire in the early days to have the kernel itself be a
18 boot loader and the kernel. setup.S made relocatable,
36 Protocol 2.05: (Kernel 2.6.20) Make protected mode kernel relocatable.
66 The traditional memory map for the kernel loader, used for Image or
74 | Stack/heap | For use by the kernel real-mode code.
76 | Kernel setup | The kernel real-mode code.
78 | Kernel boot sector | The kernel legacy boot sector.
80 | Protected-mode kernel | The bulk of the kernel image.
92 When using bzImage, the protected-mode kernel was relocated to
[all …]
|
| D | kernel-stacks | 8 Like all other architectures, x86_64 has a kernel stack for every
11 zombie. While the thread is in user space the kernel stack is empty
15 associated with each CPU. These stacks are only used while the kernel
23 kernel switches from the current task to the interrupt stack. Like
25 for kernel interrupt processing without having to increase the size
30 Switching to the kernel interrupt stack is done by software based on a
54 NMI. arch/x86_64/kernel/entry.S::paranoidentry adjusts the stack
67 when the kernel is very confused (e.g. kernel stack pointer corrupt).
68 Using a separate stack allows the kernel to recover from it well enough
75 NMI can be delivered at any time, including when the kernel is in the
[all …]
|
| D | entry_64.txt | 1 This file documents some of the kernel entries in
5 http://lkml.kernel.org/r/<20110529191055.GC9835%40elte.hu>
8 kernel code. Most of these entry points are registered in
9 arch/x86/kernel/traps.c and implemented in arch/x86/entry/entry_64.S
48 toggles whether gs is the kernel gs or the user gs. The swapgs
51 kernel mode and then when returning to user-space, and precisely
54 So when we have a secondary entry, already in kernel mode, we *must
61 The cheap way is to pick this info off the entry frame on the kernel
62 stack, from the CS of the ptregs area of the kernel stack:
76 js 1f /* negative -> in kernel */
[all …]
|
| D | early-microcode.txt | 6 can fix CPU issues before they are observed during kernel boot time.
14 on Intel: kernel/x86/microcode/GenuineIntel.bin
15 on AMD : kernel/x86/microcode/AuthenticAMD.bin
17 During BSP boot (before SMP starts), if the kernel finds the microcode file in
38 mkdir -p kernel/x86/microcode
39 cp ../microcode.bin kernel/x86/microcode/GenuineIntel.bin (or AuthenticAMD.bin)
|
| /linux-4.4.14/Documentation/ABI/stable/ |
| D | sysfs-transport-srp | 4 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
11 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
20 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
29 Contact: linux-scsi@vger.kernel.org
36 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
44 Contact: linux-scsi@vger.kernel.org
50 Contact: linux-scsi@vger.kernel.org, linux-rdma@vger.kernel.org
|
| D | sysfs-class-udc | 4 Contact: Felipe Balbi <balbi@kernel.org>
12 Contact: Felipe Balbi <balbi@kernel.org>
20 Contact: Felipe Balbi <balbi@kernel.org>
28 Contact: Felipe Balbi <balbi@kernel.org>
36 Contact: Felipe Balbi <balbi@kernel.org>
45 Contact: Felipe Balbi <balbi@kernel.org>
53 Contact: Felipe Balbi <balbi@kernel.org>
61 Contact: Felipe Balbi <balbi@kernel.org>
69 Contact: Felipe Balbi <balbi@kernel.org>
78 Contact: Felipe Balbi <balbi@kernel.org>
[all …]
|
| D | sysfs-driver-ib_srp | 4 Contact: linux-rdma@vger.kernel.org
74 Contact: linux-rdma@vger.kernel.org
80 Contact: linux-rdma@vger.kernel.org
86 Contact: linux-rdma@vger.kernel.org
94 Contact: linux-rdma@vger.kernel.org
101 Contact: linux-rdma@vger.kernel.org
108 Contact: linux-rdma@vger.kernel.org
114 Contact: linux-rdma@vger.kernel.org
121 Contact: linux-rdma@vger.kernel.org
128 Contact: linux-rdma@vger.kernel.org
[all …]
|
| D | sysfs-class-rfkill | 12 Contact: linux-wireless@vger.kernel.org,
21 Contact: linux-wireless@vger.kernel.org
29 Contact: linux-wireless@vger.kernel.org
37 Contact: linux-wireless@vger.kernel.org
48 Contact: linux-wireless@vger.kernel.org
61 Contact: linux-wireless@vger.kernel.org
|
| /linux-4.4.14/arch/tile/gxio/ |
| D | Kconfig | 2 # gxio library, or from kernel space, via kernel IORPC support.
8 # TILE-Gx mPIPE and Trio hardware from kernel space.
13 # Support direct access to the TILE-Gx mPIPE hardware from kernel space.
19 # Support direct access to the TILE-Gx TRIO hardware from kernel space.
25 # Support direct access to the TILE-Gx USB hardware from kernel space.
30 # Support direct access to the TILE-Gx UART hardware from kernel space.
|
| D | iorpc_mpipe.c | 62 params->buffer.kernel.cpa = __cpa; in gxio_mpipe_init_buffer_stack_aux()
63 params->buffer.kernel.size = mem_size; in gxio_mpipe_init_buffer_stack_aux()
64 params->buffer.kernel.pte = __pte; in gxio_mpipe_init_buffer_stack_aux()
65 params->buffer.kernel.flags = mem_flags; in gxio_mpipe_init_buffer_stack_aux()
118 params->buffer.kernel.cpa = __cpa; in gxio_mpipe_init_notif_ring_aux()
119 params->buffer.kernel.size = mem_size; in gxio_mpipe_init_notif_ring_aux()
120 params->buffer.kernel.pte = __pte; in gxio_mpipe_init_notif_ring_aux()
121 params->buffer.kernel.flags = mem_flags; in gxio_mpipe_init_notif_ring_aux()
144 params->interrupt.kernel.x = inter_x; in gxio_mpipe_request_notif_ring_interrupt()
145 params->interrupt.kernel.y = inter_y; in gxio_mpipe_request_notif_ring_interrupt()
[all …]
|
| D | iorpc_uart.c | 28 params->interrupt.kernel.x = inter_x; in gxio_uart_cfg_interrupt()
29 params->interrupt.kernel.y = inter_y; in gxio_uart_cfg_interrupt()
30 params->interrupt.kernel.ipi = inter_ipi; in gxio_uart_cfg_interrupt()
31 params->interrupt.kernel.event = inter_event; in gxio_uart_cfg_interrupt()
|
| D | iorpc_usb_host.c | 28 params->interrupt.kernel.x = inter_x; in gxio_usb_host_cfg_interrupt()
29 params->interrupt.kernel.y = inter_y; in gxio_usb_host_cfg_interrupt()
30 params->interrupt.kernel.ipi = inter_ipi; in gxio_usb_host_cfg_interrupt()
31 params->interrupt.kernel.event = inter_event; in gxio_usb_host_cfg_interrupt()
|
| /linux-4.4.14/kernel/ |
| D | Kconfig.preempt | 14 Select this option if you are building a kernel for a server or
16 raw processing power of the kernel, irrespective of scheduling
22 This option reduces the latency of the kernel by adding more
23 "explicit preemption points" to the kernel code. These new
30 is in kernel mode executing a system call. This allows
34 Select this if you are building a kernel for a desktop system.
41 This option reduces the latency of the kernel by making
42 all kernel code (that is not executing in a critical section)
45 even if it is in kernel mode executing a system call and would
49 and a slight runtime overhead to kernel code.
[all …]
|
| /linux-4.4.14/arch/microblaze/ |
| D | Kconfig | 75 source "kernel/Kconfig.freezer"
81 source "kernel/Kconfig.preempt"
83 source "kernel/Kconfig.hz"
92 bool "Default bootloader kernel arguments"
95 string "Default kernel command string"
100 to pass arguments to the kernel. For these architectures, you should
105 bool "Force default kernel command string"
109 Set this to have arguments from the default kernel command string
117 This kernel feature is useful for number crunching applications
138 bool "Prompt for advanced kernel configuration options"
[all …]
|
| /linux-4.4.14/arch/tile/ |
| D | Kconfig | 165 source "kernel/Kconfig.freezer"
176 smaller kernel memory footprint results from using a smaller
183 This lets you select the page size of the kernel. For best
203 source "kernel/Kconfig.hz"
210 current kernel, and to start another kernel. It is like a reboot
222 If enabled, the kernel will support running TILE-Gx binaries
229 This kernel feature is useful for number crunching applications
254 mapped" by the kernel. The physical memory that's not
257 If you are compiling a kernel which will never run on a
259 "false" here. This will result in the kernel mapping all of
[all …]
|
| /linux-4.4.14/arch/frv/kernel/ |
| D | entry-table.S | 24 # (2) The trap table for kernel mode
35 # The user and kernel trap tables use the same prologue for normal
39 # (5) The fixup table for kernel-trap single-step
47 # The linker script places the user mode and kernel mode trap tables on to
65 # trap table for entry from kernel mode
66 .section .trap.kernel,"ax"
84 .section .trap.fixup.kernel,"a"
97 .section .trap.kernel
100 .section .trap.fixup.kernel
116 .section .trap.kernel
[all …]
|
| /linux-4.4.14/Documentation/frv/ |
| D | gdbstub.txt | 6 The kernel contains a GDB stub that talks GDB remote protocol across a serial
7 port. This permits GDB to single step through the kernel, set breakpoints and
8 trap exceptions that happen in kernel space and interrupt execution. It also
9 permits the NMI interrupt button or serial port events to jump the kernel into
14 generate level 15 interrupts (NMI). The kernel proper cannot see the serial
31 Firstly, a debuggable kernel must be built. To do this, unpack the kernel tree
40 (*) "In-kernel GDB stub"
43 kernel.
54 command line. That tells the kernel to pass system console messages to
60 "Immediate activation" was selected, then the kernel will wait for GDB to
[all …]
|
| D | booting.txt | 29 The kernel will need to be loaded into RAM by RedBoot (or by some alternative
30 boot loader) before it can be run. The kernel image (arch/frv/boot/Image) may
46 The following command will download a raw binary kernel image from the
55 The following command will download a raw binary kernel image across the
78 This will start the kernel running. Note that if the GDB-stub is compiled in,
79 then the kernel will immediately wait for GDB to connect over serial before
80 doing anything else. See the section on kernel debugging with GDB.
82 The kernel command line <CMDLINE> tells the kernel where its console is and
122 "Documentation/kernel-parameters.txt".
149 kernel the IP address of the NFS server providing its root filesystem,
[all …]
|
| D | kernel-ABI.txt | 5 The internal FRV kernel ABI is not quite the same as the userspace ABI. A
12 clobbered in such an event. Also, within the kernel core, it is possible to
22 (*) Internal kernel-mode register ABI
53 Normal kernel mode. There are many additional control registers
59 Exceptions will invoke the appropriate normal kernel mode
76 All kernel mode registers may be accessed, plus a few extra debugging
86 exception prologues for each of user->kernel transition and kernel->kernel
87 transition. There are also user->debug and kernel->debug mode transition
98 GR30 Destroyed by kernel mode entry
100 GR31 MMU Destroyed by TLB miss kernel mode entry
[all …]
|
| D | README.txt | 22 A description of how to boot the kernel image and a summary of the kernel
28 A description of how to debug the kernel using GDB attached by serial
35 MMU linux kernel, and the registers used to support it.
51 A description of how the FR-V kernel's atomic operations work.
|
| D | configuring.txt | 18 the kernel configuration that need to be considered.
24 the kernel with MB93091 CB10, CB11, CB30, CB41, CB60, CB70 and CB451
41 selected. This can be changed dynamically once the kernel is running (see
45 Setup" section of the kernel configuration too:
49 This requests that a uClinux kernel set aside some memory in an uncached
63 This makes the protection register governing access to the core kernel
68 kernel configuration especially for debugging a kernel on this
76 The kernel sources include a number of example default configurations:
|
| /linux-4.4.14/arch/s390/ |
| D | Kconfig.debug | 14 kernel and userspace memory. Accidental memory access is likely
16 Memory access is required for experts who want to debug the kernel.
21 bool "Export kernel pagetable layout to userspace via debugfs"
25 Say Y here if you want to show the kernel pagetable layout in a
26 debugfs file. This information is only useful for kernel developers
27 who are working in architecture specific areas of the kernel.
29 kernel.
|
| D | Kconfig | 174 source "kernel/Kconfig.freezer"
176 source "kernel/livepatch/Kconfig"
224 2086 series). The kernel will be slightly faster but will not work
232 2096 series). The kernel will be slightly faster but will not work
240 2098 series). The kernel will be slightly faster but will not work
248 (2818 and 2817 series). The kernel will be slightly faster but will
256 2827 series). The kernel will be slightly faster but will not work on
264 The kernel will be slightly faster but will not work on older
298 selection of instructions itself, so the resulting kernel will run on
304 Tune the generated code for the target processor for which the kernel
[all …]
|
| /linux-4.4.14/arch/arm/mach-ks8695/ |
| D | Kconfig | 9 Say 'Y' here if you want your kernel to run on the original
15 Say 'Y' here if you want your kernel to run on the D-Link
21 say 'Y' here if you want your kernel to run on the Brivo
27 Say 'Y' here if you want your kernel to support the
34 Say 'Y' here if you want your kernel to support the
41 Say 'Y' here if you want your kernel to support the
49 Say 'Y' here if you want your kernel to support the OpenGear
57 Say 'Y' here if you want your kernel to support the OpenGear
65 Say 'Y' here if you want your kernel to support the OpenGear
73 Say 'Y' here if you want your kernel to support the OpenGear
[all …]
|
| /linux-4.4.14/Documentation/security/ |
| D | apparmor.txt | 3 AppArmor is MAC style security extension for the Linux kernel. It implements
17 Build the kernel
20 security=apparmor on the kernel's command line.
24 kernel's command line
27 policy must be loaded into the kernel from user space (see the Documentation
37 Wiki - http://apparmor.wiki.kernel.org/
39 Kernel module - git://git.kernel.org/pub/scm/linux/kernel/git/jj/apparmor-dev.git
|
| D | LSM.txt | 5 various security checks to be hooked by new kernel extensions. The name
7 loadable kernel modules. Instead, they are selectable at build-time via
9 "security=..." kernel command line argument, in the case where multiple
10 LSMs were built into a given kernel.
19 Without a specific LSM built into the kernel, the default LSM will be the
26 a new LSM is accepted into the kernel when its intent (a description of
|
| /linux-4.4.14/arch/arm/mach-footbridge/ |
| D | Kconfig | 14 Say Y here if you intend to run this kernel on the CATS.
16 Saying N will reduce the size of the Footbridge kernel.
25 Say Y here if you intend to run this kernel on the Compaq
28 Saying N will reduce the size of the Footbridge kernel.
44 Say Y here if you intend to run this kernel on the EBSA285 card
47 Saying N will reduce the size of the Footbridge kernel.
58 Say Y here if you intend to run this kernel on the EBSA285 card
61 Saying N will reduce the size of the Footbridge kernel.
73 Say Y here if you intend to run this kernel on the Rebel.COM
78 Saying N will reduce the size of the Footbridge kernel.
|
| /linux-4.4.14/arch/metag/ |
| D | Kconfig.debug | 10 bool "Use 4Kb for kernel stacks instead of 8Kb"
13 If you say Y here the kernel will use a 4Kb stacksize for the
14 kernel stack attached to each process/thread. This facilitates
22 If you say Y here the kernel will use the Meta hardware trace
27 bool "Poison catch buffer contents on kernel entry"
29 If you say Y here the kernel will write poison data to the
30 catch buffer registers on kernel entry. This will make any
|
| D | Kconfig | 59 source "kernel/Kconfig.freezer"
82 and it has to accommodate user address space, kernel address
85 memory can be "permanently mapped" by the kernel. The physical
88 Depending on the selected kernel/user memory split, minimum
90 option which should result in a slightly faster kernel.
223 bool "Embed DTB in kernel image"
226 Embeds a device tree binary in the kernel image.
233 automatically based on kernel configuration).
236 bool "Default bootloader kernel arguments"
243 to pass arguments to the kernel. For these architectures, you should
[all …]
|
| /linux-4.4.14/tools/testing/selftests/vm/ |
| D | run_vmtests | 63 shmmax=`cat /proc/sys/kernel/shmmax`
64 shmall=`cat /proc/sys/kernel/shmall`
65 echo 268435456 > /proc/sys/kernel/shmmax
66 echo 4194304 > /proc/sys/kernel/shmall
77 echo $shmmax > /proc/sys/kernel/shmmax
78 echo $shmall > /proc/sys/kernel/shmall
|
| /linux-4.4.14/Documentation/infiniband/ |
| D | user_verbs.txt | 10 libibverbs also requires appropriate device-dependent kernel and
12 a Mellanox HCA, you will need the ib_mthca kernel module and the
15 User-kernel communication
17 Userspace communicates with the kernel for slow path, resource
21 system call or context switch into the kernel.
23 Commands are sent to the kernel via write()s on these device files.
25 The structs for commands that require a response from the kernel
33 commands passed through a file descriptor, the kernel can keep track
36 between kernel pointers and opaque userspace handles, so that kernel
38 the kernel into following a bogus pointer.
[all …]
|
| /linux-4.4.14/arch/cris/arch-v10/ |
| D | README.mm | 35 segmentation of the kernel memory space. We use this feature to avoid having
36 to use page-tables to map the physical memory into the kernel's address
38 map during kernel-mode, so that the kernel easily can access the corresponding
41 As a comparison, the Linux/i386 2.0 puts the kernel and physical RAM at
44 map through. That changed in 2.2, putting the kernel/physical RAM at
50 The kernel-mode segmentation map:
54 | kernel seg_f | flash | |
57 | kernel seg_e | flash | |
60 | kernel seg_d | =======> | |
63 | kernel seg_c |==\ | |
[all …]
|
| /linux-4.4.14/scripts/package/ |
| D | builddeb | 196 debhookdir=${KDEB_HOOKDIR:-/etc/kernel}
253 * Custom built Linux kernel.
260 This is a packacked upstream version of the Linux kernel.
263 ftp://ftp.kernel.org/pub/linux/kernel
267 The git repository for mainline kernel development is at:
268 git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
342 Description: Linux kernel headers for $KERNELRELEASE on \${kernel:debarch}
343 This package provides kernel header files for $KERNELRELEASE on \${kernel:debarch}
357 Description: Linux kernel firmware, version $version
358 This package contains firmware from the Linux kernel, version $version.
[all …]
|
| /linux-4.4.14/arch/powerpc/ |
| D | Kconfig | 41 This defines the number of virtual interrupt numbers the kernel
313 source "kernel/Kconfig.freezer"
324 source kernel/Kconfig.hz
325 source kernel/Kconfig.preempt
340 say Y here, the kernel will include code to emulate a floating-point
356 Select this option will enable the kernel to support to emulate
426 current kernel, and to start another kernel. It is like a reboot
428 you can start any kernel with it, not just Linux.
439 bool "Build a kdump crash kernel"
443 Build a kernel suitable for use as a kdump capture kernel.
[all …]
|
| /linux-4.4.14/Documentation/scsi/ |
| D | lpfc.txt | 10 toward the upstream kernel. As such, we removed #ifdefs for older kernels
15 and extended attribute support is now part of the upstream kernel
17 nor a *full* version which has old an new kernel support.
20 kernel.
45 The community supporting kernel.org has driven an effort to remove
51 As a potential new addition to kernel.org, the 8.x driver was asked to
60 patch is part of the standard 2.6.10 kernel.
63 to be present in the kernel. No #define needs to be set to enable support.
68 This source package is targeted for the upstream kernel only. (See notes
70 migrating into the kernel.org kernel.
[all …]
|
| /linux-4.4.14/drivers/staging/iio/Documentation/ |
| D | sysfs-bus-iio-light | 4 Contact: linux-iio@vger.kernel.org
11 Contact: linux-iio@vger.kernel.org
17 Contact: linux-iio@vger.kernel.org
24 Contact: linux-iio@vger.kernel.org
31 Contact: linux-iio@vger.kernel.org
39 Contact: linux-iio@vger.kernel.org
50 Contact: linux-iio@vger.kernel.org
59 Contact: linux-iio@vger.kernel.org
68 Contact: linux-iio@vger.kernel.org
75 Contact: linux-iio@vger.kernel.org
[all …]
|
| D | sysfs-bus-iio-dds | 4 Contact: linux-iio@vger.kernel.org
15 Contact: linux-iio@vger.kernel.org
24 Contact: linux-iio@vger.kernel.org
34 Contact: linux-iio@vger.kernel.org
45 Contact: linux-iio@vger.kernel.org
54 Contact: linux-iio@vger.kernel.org
65 Contact: linux-iio@vger.kernel.org
77 Contact: linux-iio@vger.kernel.org
85 Contact: linux-iio@vger.kernel.org
94 Contact: linux-iio@vger.kernel.org
|
| /linux-4.4.14/arch/parisc/ |
| D | Kconfig | 116 source "kernel/Kconfig.freezer"
129 used for optimizing purposes. In order to compile a kernel
133 Specifying "PA8000" here will allow you to select a 64-bit kernel
183 If you configure the kernel to include many drivers built-in instead
184 as modules, the kernel executable may become too big, so that the
186 your vmlinux kernel. In that case enabling this option will help you
190 a kernel which includes all necessary drivers built-in and which can
193 Enabling this option will probably slow down your kernel.
196 bool "64-bit kernel"
199 Enable this if you want to support 64bit kernel on PA-RISC platform.
[all …]
|
| /linux-4.4.14/arch/mips/netlogic/ |
| D | Kconfig | 9 Add an FDT blob for XLP EVP boards into the kernel.
11 pointer to the kernel. The corresponding DTS file is at
19 Add an FDT blob for XLP VP boards into the kernel.
21 pointer to the kernel. The corresponding DTS file is at
29 Add an FDT blob for XLP FVP board into the kernel.
31 pointer to the kernel. The corresponding DTS file is at
39 Add an FDT blob for XLP GVP board into the kernel.
41 pointer to the kernel. The corresponding DTS file is at
48 Add an FDT blob for XLP RVP board into the kernel.
50 pointer to the kernel. The corresponding DTS file is at
|
| /linux-4.4.14/arch/arm/kernel/ |
| D | sys_oabi-compat.c | 199 struct flock64 kernel; in do_locks() local
207 kernel.l_type = user.l_type; in do_locks()
208 kernel.l_whence = user.l_whence; in do_locks()
209 kernel.l_start = user.l_start; in do_locks()
210 kernel.l_len = user.l_len; in do_locks()
211 kernel.l_pid = user.l_pid; in do_locks()
215 ret = sys_fcntl64(fd, cmd, (unsigned long)&kernel); in do_locks()
219 user.l_type = kernel.l_type; in do_locks()
220 user.l_whence = kernel.l_whence; in do_locks()
221 user.l_start = kernel.l_start; in do_locks()
[all …]
|
| /linux-4.4.14/arch/powerpc/platforms/ |
| D | Kconfig.cputype | 2 bool "64-bit kernel"
7 This option selects whether a 32-bit or a 64-bit kernel
92 This will create a kernel which is optimised for a particular CPU.
93 The resulting kernel may not run on other CPUs, so use this with care.
224 This option enables kernel support for larger than 32-bit physical
237 This option enables kernel support for the Altivec extensions to the
238 PowerPC processor. The kernel currently supports saving and restoring
245 kernel).
254 This option enables kernel support for the Vector Scaler extensions
255 to the PowerPC processor. The kernel currently supports saving and
[all …]
|
| /linux-4.4.14/fs/sysfs/ |
| D | Kconfig | 6 The sysfs filesystem is a virtual filesystem that the kernel uses to
7 export internal kernel objects, their attributes, and their
11 kernel, such as the devices the kernel has discovered on each bus and
13 and other kernel subsystems.
21 the kernel boot command line via its major and minor numbers. For
|
| /linux-4.4.14/Documentation/acpi/ |
| D | initrd_table_override.txt | 30 If BIOS ACPI tables are overridden the kernel will get tainted with the
33 that a workaround is not accepted in the Linux kernel.
35 Still, it can and should be enabled in any kernel, because:
38 compatibility with the Linux kernel.
55 # They must be put into a /kernel/firmware/acpi directory inside the
60 mkdir -p kernel/firmware/acpi
61 cp dsdt.aml kernel/firmware/acpi
66 cp facp.aml kernel/firmware/acpi
67 cp ssdt1.aml kernel/firmware/acpi
70 find kernel | cpio -H newc --create > /boot/instrumented_initrd
[all …]
|
| /linux-4.4.14/drivers/zorro/ |
| D | Kconfig | 8 By default, the kernel contains a database of all known Zorro device
10 user. This database increases the size of the kernel image by about
12 take up kernel memory. Anyway, if you are building an installation
13 floppy or kernel for an embedded system where kernel image size
|
| /linux-4.4.14/arch/x86/ |
| D | Kconfig.debug | 12 of memory, including kernel and userspace memory. Accidental
14 be used by people debugging the kernel. Note that with PAT support
37 Write kernel log output directly into the VGA buffer or to a serial
40 This is useful for kernel debugging when your machine crashes very
50 Write kernel log output directly into the EHCI debug port.
52 This is useful for kernel debugging when your machine crashes very
63 Write kernel log output directly into the EFI framebuffer.
65 This is useful for kernel debugging when your machine crashes very
72 bool "Export kernel pagetable layout to userspace via debugfs"
77 Say Y here if you want to show the kernel pagetable layout in a
[all …]
|
| D | Kconfig | 3 bool "64-bit kernel" if ARCH = "x86"
6 Say yes to build a 64-bit kernel - formerly known as x86_64
7 Say no to build a 32-bit kernel - formerly known as i386
299 source "kernel/Kconfig.freezer"
320 If you say N here, the kernel will run on uni- and multiprocessor
322 you say Y here, the kernel will run on many, but not all,
323 uniprocessor machines. On a uniprocessor machine, the kernel
327 "Pentium" under "Processor family", the kernel will not work on 486
346 names. This is required to support /proc/cpuinfo and a few kernel
348 making those few kernel messages show numeric feature bits instead.
[all …]
|
| /linux-4.4.14/Documentation/firmware_class/ |
| D | README | 9 Today, the most extended way to use firmware in the Linux kernel is linking
21 1), kernel(driver):
23 - kernel searchs the fimware image with name $FIRMWARE directly
34 if firmware_class is built in kernel(the general situation)
42 3), kernel: Discard any previous partial load.
48 5), kernel: grows a buffer in PAGE_SIZE increments to hold the image as it
54 7), kernel: request_firmware() returns and the driver has the firmware
59 8), kernel(driver): Driver code calls release_firmware(fw_entry) releasing
97 about in-kernel persistence:
100 firmware images in non-swappable kernel memory or even in the kernel image
[all …]
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig.debug | 6 bool "Export kernel pagetable layout to userspace via debugfs"
11 Say Y here if you want to show the kernel pagetable layout in a
12 debugfs file. This information is only useful for kernel developers
13 who are working in architecture specific areas of the kernel.
15 kernel.
23 of memory, including kernel and userspace memory. Accidental
25 be used by people debugging the kernel.
34 # traces, you can get a slightly smaller kernel by setting this option to
41 If you say N here, the resulting kernel will be slightly smaller and
43 when a problem occurs with the kernel, the information that is
[all …]
|
| /linux-4.4.14/Documentation/trace/ |
| D | kprobetrace.txt | 15 To enable this feature, build your kernel with CONFIG_KPROBE_EVENT=y.
19 /sys/kernel/debug/tracing/kprobe_events, and enable it via
20 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/enabled.
38 @ADDR : Fetch memory at ADDR (ADDR should be in kernel)
58 kernel space. This means it will fail and store NULL if the string container
90 /sys/kernel/debug/tracing/kprobe_profile.
100 …echo 'p:myprobe do_sys_open dfd=%ax filename=%dx flags=%cx mode=+4($stack)' > /sys/kernel/debug/tr…
109 echo 'r:myretprobe do_sys_open $retval' >> /sys/kernel/debug/tracing/kprobe_events
114 /sys/kernel/debug/tracing/events/kprobes/<EVENT>/format.
116 cat /sys/kernel/debug/tracing/events/kprobes/myprobe/format
[all …]
|
| D | events.txt | 10 without creating custom kernel modules to register probe functions
14 the kernel developer must provide code snippets which define how the
25 /sys/kernel/debug/tracing/available_events.
28 to /sys/kernel/debug/tracing/set_event. For example:
30 # echo sched_wakeup >> /sys/kernel/debug/tracing/set_event
38 # echo '!sched_wakeup' >> /sys/kernel/debug/tracing/set_event
42 # echo > /sys/kernel/debug/tracing/set_event
46 # echo *:* > /sys/kernel/debug/tracing/set_event
55 # echo 'irq:*' > /sys/kernel/debug/tracing/set_event
60 The events available are also listed in /sys/kernel/debug/tracing/events/ hierarchy
[all …]
|
| D | mmiotrace.txt | 1 In-kernel memory-mapped I/O tracing
35 $ mount -t debugfs debugfs /sys/kernel/debug
36 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
37 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
39 $ echo "X is up" > /sys/kernel/debug/tracing/trace_marker
40 $ echo nop > /sys/kernel/debug/tracing/current_tracer
47 Make sure debugfs is mounted to /sys/kernel/debug.
49 $ mount -t debugfs debugfs /sys/kernel/debug
54 $ echo mmiotrace > /sys/kernel/debug/tracing/current_tracer
57 $ cat /sys/kernel/debug/tracing/trace_pipe > mydump.txt &
[all …]
|
| D | events-nmi.txt | 5 /sys/kernel/debug/tracing/events/nmi
12 NMI handlers are hogging large amounts of CPU time. The kernel
29 Note that the kernel's output is in milliseconds, but the input
32 cd /sys/kernel/debug/tracing/events/nmi/nmi_handler
38 $ cat /sys/kernel/debug/tracing/trace_pipe
|
| /linux-4.4.14/arch/arm/mach-ixp4xx/ |
| D | Kconfig | 12 Say 'Y' here if you want your kernel to support Linksys's
20 Say 'Y' here if you want your kernel to support the Gateworks
28 Say 'Y' here if you want your kernel to support the Giant
36 Say 'Y' here if you want your kernel to support the ADI
44 Say 'Y' here if you want your kernel to support Gateway's
52 Say 'Y' here if you want your kernel to support Netgear's
59 Say 'Y' here if you want your kernel to support Intel's
66 Say 'Y' here if you want your kernel to support Intel's
73 Say 'Y' here if you want your kernel to support Intel's
80 Say 'Y' here if you want your kernel to support GORAMO
[all …]
|
| /linux-4.4.14/Documentation/networking/ |
| D | openvswitch.txt | 4 The Open vSwitch kernel module allows flexible userspace control over
10 The kernel module implements multiple "datapaths" (analogous to
18 When a packet arrives on a vport, the kernel module processes it by
23 packets of the same type entirely in-kernel).
31 kernel module to remain relevant, it must be possible for newer
39 kernel module passes a packet to userspace, it also passes along the
42 kernel-provided version:
45 kernel's, then nothing special is necessary.
47 - If the kernel's flow key includes more fields than the userspace
48 version of the flow key, for example if the kernel decoded IPv6
[all …]
|
| D | skfp.txt | 70 From v2.01 on, the driver is integrated in the linux kernel sources.
72 supported by the kernel.
91 support may not be enabled in your kernel.
103 Reason: Either the router's kernel is not configured for IP
150 - in kernel 2.3.99
154 - Changes for 2.3.45 kernel
171 - Integration in Linux kernel sources
180 - Compilation with kernel version 2.2.13 failed
194 - Support for kernel versions 2.2.x added
195 - Kernel patch instead of private duplicate of kernel functions
[all …]
|
| /linux-4.4.14/Documentation/power/ |
| D | freezing-of-tasks.txt | 7 kernel threads are controlled during hibernation or system-wide suspend (on some
14 PF_NOFREEZE unset (all user space processes and some kernel threads) are
20 freeze_processes() (defined in kernel/power/process.c) is called. A system-wide
24 fake signal to all user space processes, and wakes up all the kernel threads.
26 results in a call to __refrigerator() (defined in kernel/freezer.c), which sets
30 to as 'the freezer' (these functions are defined in kernel/power/process.c,
31 kernel/freezer.c & include/linux/freezer.h). User space processes are generally
32 frozen before kernel threads.
39 signal-handling code, but the freezable kernel threads need to call it
43 calling try_to_freeze(). The main loop of a freezable kernel thread may look
[all …]
|
| /linux-4.4.14/arch/s390/kernel/ |
| D | head_kdump.S | 16 # kdump entry (new kernel - not yet relocated)
32 lghi %r2,0 # Yes: Start kdump kernel
68 mvc 0(256,%r10),0(%r5) # Copy old kernel to tmp
69 mvc 0(256,%r5),0(%r11) # Copy new kernel to old
77 basr %r14,%r14 # Start relocated kernel
83 # Startup of kdump (relocated new kernel)
88 0: lpswe .Lrestart_psw-0b(%r13) # Start new kernel...
|
| /linux-4.4.14/Documentation/x86/x86_64/ |
| D | uefi.txt | 6 Although the tools below are _not_ needed for building the kernel,
12 2. Booting Linux kernel on UEFI x86_64 platform requires bootloader
19 - Build the kernel with the following configuration.
29 kernel image built in first step and corresponding
32 - Boot to EFI shell and invoke elilo choosing the kernel image built
35 kernel command line parameters to turn off some or all EFI runtime
41 physical RAM by using the following kernel command line parameter.
|
| /linux-4.4.14/arch/mips/ath79/ |
| D | Kconfig | 14 Say 'Y' here if you want your kernel to support the
26 Say 'Y' here if you want your kernel to support the
38 Say 'Y' here if you want your kernel to support the
50 Say 'Y' here if you want your kernel to support the
61 Say 'Y' here if you want your kernel to support the
71 Say 'Y' here if you want your kernel to support the
75 prompt "Build a DTB in the kernel"
78 Select a devicetree that should be built into the kernel.
|
| /linux-4.4.14/arch/alpha/kernel/ |
| D | vmlinux.lds.S | 10 PHDRS { kernel PT_LOAD; note PT_NOTE; }
28 } :kernel
32 NOTES :kernel :note
35 } :kernel
|
| /linux-4.4.14/scripts/ksymoops/ |
| D | README | 1 ksymoops has been removed from the kernel. It was always meant to be a
2 free standing utility, not linked to any particular kernel version.
4 ftp://ftp.<country>.kernel.org/pub/linux/utils/kernel/ksymoops together
|
| /linux-4.4.14/arch/mn10300/ |
| D | Kconfig.debug | 6 bool "Using serial port during decompressing kernel"
12 "Ok, booting the kernel.\n" on console.
19 If you say Y here the kernel will execute a list of misaligned memory
21 correctly. If it does not, the kernel will throw a BUG.
27 Kprobes allows you to trap at almost any kernel address and
30 for kernel debugging, non-intrusive instrumentation and testing.
34 bool "Remote GDB kernel debugging"
39 If you say Y here, it will be possible to remotely debug the kernel
40 using gdb. This enlarges your kernel ELF image disk size by several
42 RAM to avoid excessive linking time. This is only useful for kernel
[all …]
|
| /linux-4.4.14/arch/sh/ |
| D | Kconfig.debug | 14 in FLASH or EPROM. The kernel will use standard BIOS calls during
32 bool "Use 4Kb for kernel stacks instead of 8Kb"
35 If you say Y here the kernel will use a 4Kb stacksize for the
36 kernel stack attached to each process/thread. This facilitates
42 bool "Use separate kernel stacks when processing interrupts"
45 If you say Y here the kernel will use separate kernel stacks
47 overflowing the process kernel stacks.
57 the kernel in size a bit, most users will want to say N here.
68 the cost of an increase in overall kernel size.
|
| /linux-4.4.14/lib/ |
| D | Kconfig.debug | 15 The behavior is also controlled by the kernel command line
16 parameter printk.time=1. See Documentation/kernel-parameters.txt
33 This build option allows you to read kernel boot messages
35 specified in milliseconds on the kernel command line,
54 Compiles debug level messages into the kernel, which would not
59 enlarges the kernel text size by about 2%.
121 bool "Compile the kernel with debug info"
124 If you say Y here the resulting kernel image will include
125 debugging info resulting in a larger kernel image.
126 This adds debug symbols to the kernel and modules (gcc -g), and
[all …]
|
| D | Kconfig.kgdb | 6 bool "KGDB: kernel debugger"
11 kernel using gdb. It is recommended but not required, that
12 you also turn on the kernel config option
15 kernel debugger is available at http://kgdb.sourceforge.net
41 a kernel boot arguments "kgdbwait kgdbts=V1F100"
49 to pass in a kernel parameter
74 KDB frontend for kernel
98 setting with kdb.cmd_enable=X kernel command line option will
113 This integer controls the behaviour of kdb when the kernel gets a
120 kernel is still usable in this situation.
[all …]
|
| /linux-4.4.14/drivers/char/hw_random/ |
| D | Kconfig | 17 into the kernel's random number generator. That is usually
29 This driver provides kernel-side support for a generic Random
44 This driver provides kernel-side support for the Random Number
57 This driver provides kernel-side support for the Random Number
70 This driver provides kernel-side support for the Random Number
83 This driver provides kernel-side support for the Random Number
96 This driver provides kernel-side support for the Random Number
109 This driver provides kernel-side support for the RNG200
122 This driver provides kernel-side support for the Random Number
135 This driver provides kernel-side support for the Random Number
[all …]
|
| /linux-4.4.14/arch/hexagon/ |
| D | Kconfig | 38 Platforms that don't load the kernel at zero set this.
62 # Use the generic interrupt handling code in kernel/irq/:
105 string "Default kernel command string"
109 to pass arguments to the kernel. For these, you should supply some
117 Enables SMP support in the kernel. If unsure, say "Y"
126 kernel will support. The maximum supported value is 6 and the
130 approximately eight kilobytes to the kernel image.
154 source "kernel/Kconfig.hz"
159 source "kernel/Kconfig.freezer"
|
| /linux-4.4.14/arch/arc/ |
| D | Kconfig.debug | 6 bool "Use 16Kb for kernel stacks instead of 8Kb"
8 If you say Y here the kernel will use a 16Kb stacksize for the
9 kernel stack attached to each process/thread. The default is 8K.
10 This increases the resident kernel footprint and will cause less
|
| /linux-4.4.14/Documentation/filesystems/ |
| D | ramfs-rootfs-initramfs.txt | 76 to check for and handle an empty list, it's smaller and simpler for the kernel
83 default. To force ramfs, add "rootfstype=ramfs" to the kernel command
90 extracted into rootfs when the kernel boots up. After extracting, the kernel
95 archive is extracted into it, the kernel will fall through to the older code
102 linked into the linux kernel image. (The directory linux-*/usr is devoted
106 such as ext2, that needed a driver built into the kernel), while the new
109 kernel's cpio extraction code is not only extremely small, it's also
113 some setup and then returned to the kernel, while the init program from
114 initramfs is not expected to return to the kernel. (If /init needs to hand
133 The 2.6 kernel build process always creates a gzipped cpio format initramfs
[all …]
|
| D | befs.txt | 42 the kernel. Because of this naming conflict, on Linux the BeOS
49 Apply the patchfile to your kernel source tree.
50 Assuming that your kernel source is in /foo/bar/linux and the patchfile
60 step 2. Configuration & make kernel
62 The linux kernel has many compile-time options. Most of them are beyond the
71 The BeFS module is not a standard part of the linux kernel, so you must first
78 Save your kernel configuration and then build your kernel.
82 See the kernel howto <http://www.linux.com/howto/Kernel-HOWTO.html> for
|
| /linux-4.4.14/kernel/gcov/ |
| D | Kconfig | 1 menu "GCOV-based kernel profiling"
4 bool "Enable gcov-based kernel profiling"
15 for the entire kernel. To enable profiling for specific files or
44 This options activates profiling for the entire kernel.
48 Note that a kernel compiled with profiling flags will be significantly
50 which are not linked to the kernel image to prevent linker errors.
59 In such a case use this option to adjust the format used in the kernel
|
| /linux-4.4.14/tools/testing/selftests/ftrace/test.d/ftrace/ |
| D | fgraph-filter-stack.tc | 19 if [ -e /proc/sys/kernel/stack_tracer_enabled ]; then
20 echo 0 > /proc/sys/kernel/stack_tracer_enabled
54 echo 1 > /proc/sys/kernel/stack_tracer_enabled
73 echo 0 > /proc/sys/kernel/stack_tracer_enabled
|
| /linux-4.4.14/arch/um/ |
| D | .gitignore | 1 kernel/config.c
2 kernel/config.tmp
3 kernel/vmlinux.lds
|
| D | Kconfig.debug | 9 This allows profiling of a User-Mode Linux kernel with the gprof
15 If you're involved in UML kernel development and want to use gprof,
28 If you're involved in UML kernel development and want to use gcov,
35 Write kernel log output directly to stdout.
37 This is useful for kernel debugging when your machine crashes very
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | nfsroot.txt | 6 Updated 2006 by Nico Schottelius <nico-kernel-nfsroot@schottelius.org>
29 In the networking options, kernel level autoconfiguration can be selected,
39 When the kernel has been loaded by a boot loader (see below) it needs to be
42 This can be established using the following kernel command line parameters:
48 real device but just a synonym to tell the kernel to use NFS instead of
84 This parameter tells the kernel how to configure IP addresses of devices
90 If this parameter is missing from the kernel command line, all fields are
92 this means that the kernel tries to configure everything using
147 into the kernel will be used, regardless of the value of
152 on or any: use any protocol available in the kernel
[all …]
|
| D | rpc-server-gss.txt | 2 rpcsec_gss support for kernel RPC servers
6 implement RPCGSS authentication in kernel RPC servers such as the NFS
26 The Linux kernel, at the moment, supports only the KRB5 mechanism, and
29 GSSAPI is a complex library, and implementing it completely in kernel is
40 kernel, but leave the initial context establishment to userspace. We
60 than a few housand groups (the current hard limit in the kernel is 65K
62 back to the kernel (4KiB).
74 This upcall mechanism uses the kernel rpc client and connects to the gssproxy
81 To provide backward compatibility, the kernel defaults to using the
|
| /linux-4.4.14/Documentation/hid/ |
| D | uhid.txt | 8 With UHID, a user-space transport driver can create kernel hid-devices for each
10 events provided from the kernel to user-space and vice versa.
62 an HID_INPUT2 event with your raw data payload. If the kernel wants to send data
66 Those requests are always synchronous. That means, the kernel sends
69 the response via UHID_GET_REPORT_REPLY and UHID_SET_REPORT_REPLY to the kernel.
70 The kernel blocks internal driver-execution during such round-trips (times out
82 the kernel. The kernel will parse the event immediately and if the event ID is
91 event to the kernel. The payload is of type struct uhid_create2_req and
97 UHID_INPUT events can be sent to the kernel.
102 You must send UHID_CREATE2 before sending input to the kernel! This event
[all …]
|
| /linux-4.4.14/Documentation/s390/ |
| D | zfcpdump.txt | 11 This zfcpdump implementation consists of a Linux dump kernel together with
18 The kernel part of zfcpdump is implemented as a debugfs file under "zcore/mem",
23 dump enabled kernel with the zcore driver, the kernel config option
29 Since kernel version 3.12 also the /proc/vmcore file can also be used to access
32 To get a valid zfcpdump kernel configuration use "make zfcpdump_defconfig".
34 The s390 zipl tool looks for the zfcpdump kernel and optional initrd/initramfs
37 * kernel: <zfcpdump directory>/zfcpdump.image
43 initrd. It can also be included in a built-in kernel initramfs. The application
|
| /linux-4.4.14/arch/unicore32/ |
| D | Kconfig.debug | 10 of memory, including kernel and userspace memory. Accidental
12 be used by people debugging the kernel.
22 Write kernel log output directly into the ocd or to a serial port.
24 This is useful for kernel debugging when your machine crashes very
30 # These options are only for real kernel hackers who want to get their hands dirty.
36 in the kernel. This is helpful if you are debugging code that
|
| D | Kconfig | 71 source "kernel/Kconfig.freezer"
145 source "kernel/Kconfig.preempt"
147 source "kernel/Kconfig.hz"
171 string "Default kernel command string"
175 bool "Always use the default kernel command string"
178 Always use the default kernel command string, even if the boot
179 loader passes other arguments to the kernel.
181 command-line options your boot loader passes to the kernel.
195 source "kernel/power/Kconfig"
|
| /linux-4.4.14/arch/m32r/ |
| D | Kconfig.debug | 9 Unmap pages from the kernel linear mapping after free_pages().
14 bool "Compile the kernel with frame pointers"
16 If you say Y here the resulting kernel image will be slightly larger
18 If you don't debug the kernel, you can say N, but we may not be able
|
| /linux-4.4.14/drivers/base/ |
| D | Kconfig | 7 The uevent helper program is forked by the kernel for
10 used to hook hotplug scripts into kernel device events. It
25 via /proc/sys/kernel/hotplug or via /sys/kernel/uevent_helper
32 In this filesystem, the kernel driver core maintains device
48 bool "Automount devtmpfs at /dev, after the kernel mounted the rootfs"
51 This will instruct the kernel to automatically mount the
52 devtmpfs filesystem at /dev, directly after the kernel has
89 bool "Include in-kernel firmware blobs in kernel binary"
93 The kernel source tree includes a number of firmware 'blobs'
101 into the kernel directly, where request_firmware() will find
[all …]
|
| /linux-4.4.14/arch/ia64/ |
| D | Kconfig | 8 source "kernel/Kconfig.freezer"
61 <linux-ia64@vger.kernel.org>.
151 This selects the system type of your hardware. A "generic" kernel
153 a kernel for your specific system, it will be faster and smaller.
178 Build a kernel that runs on HP zx1 and sx1000 systems. This adds
185 Build a kernel that runs on HP zx1 and sx1000 systems even when they
189 wasting some kernel memory (about 2MB by default).
196 Selecting this option will optimize the kernel for use on sn2 based
197 systems, but the resulting kernel binary will not run on other
208 Selecting this option will optimize the kernel for use on UV based
[all …]
|
| /linux-4.4.14/arch/arm/mach-iop32x/ |
| D | Kconfig | 13 Say Y here if you want to run your kernel on the GLAN Tank
20 Say Y here if you want to run your kernel on the Intel IQ80321
27 Say Y here if you want to run your kernel on the Intel EP80219
34 Say Y here if you want to run your kernel on the Thecus n2100
40 Say Y here if you want to run your kernel on the Lanner EM7210
|
| /linux-4.4.14/arch/frv/ |
| D | Kconfig.debug | 6 bool "Remote GDB kernel debugging"
11 If you say Y here, it will be possible to remotely debug the kernel
12 using gdb. This enlarges your kernel ELF image disk size by several
14 RAM to avoid excessive linking time. This is only useful for kernel
45 would like kernel messages to be formatted into GDB $O packets so
|
| /linux-4.4.14/arch/m68k/ |
| D | Kconfig.debug | 17 Write kernel log output directly to a serial port.
21 Pass "earlyprintk" on the kernel command line to get a
24 This is useful for kernel debugging when your machine crashes very
33 Enable debugging symbols on kernel build.
44 Do not output any debug BUG messages within the kernel.
|
| D | Kconfig.machine | 11 you plan to use this kernel on an Amiga, say Y here and browse the
21 this kernel on an Atari, say Y here and browse the material
49 Say Y here if you want to build a kernel for a 680x0 based VME
60 build a kernel which can run on MVME147 single-board computers. If
70 kernel which can run on MVME162, MVME166, MVME167, MVME172, and
81 build a kernel which can run on BVME4000 and BVME6000 boards. If
92 experimental. If you plan to try to use the kernel on such a machine
108 If you don't want to compile a kernel for a Sun 3x, say N.
133 If you don't want to compile a kernel exclusively for a Sun 3, say N.
311 If you say Y here kernel will try to collect command
[all …]
|
| /linux-4.4.14/security/ |
| D | Kconfig | 10 bool "Restrict unprivileged access to the kernel syslog"
13 This enforces restrictions on unprivileged users reading the kernel
27 configured into your kernel.
78 This option enables support for booting the kernel with the
81 of the kernel. If the system does not support Intel(R) TXT, this
86 create a robust initial kernel measurement and verification, which
87 helps to ensure that kernel security mechanisms are functioning
89 of the kernel itself.
92 confidence that their hardware is running the VMM or kernel that
100 Intel TXT support in a kernel boot.
[all …]
|
| /linux-4.4.14/arch/arm/mach-mvebu/ |
| D | Kconfig | 34 Say 'Y' here if you want your kernel to support boards based
49 Say 'Y' here if you want your kernel to support boards based
64 Say 'Y' here if you want your kernel to support boards based
78 Say 'Y' here if you want your kernel to support boards based
88 Say 'Y' here if you want your kernel to support boards based
102 Say 'Y' here if you want your kernel to support the
117 Say 'Y' here if you want your kernel to support boards based
|
| /linux-4.4.14/arch/arm/mach-gemini/ |
| D | Kconfig | 9 Say Y here if you intend to run this kernel on a
16 Say Y here if you intend to run this kernel on a
23 Say Y here if you intend to run this kernel on a
30 Say Y here if you intend to run this kernel on a
|
| /linux-4.4.14/drivers/staging/speakup/ |
| D | Kconfig | 9 kernel, it can speak everything on the text console from
48 synthesizer. You can say y to build it into the kernel,
57 synthesizer. You can say y to build it into the kernel,
65 synthesizer. You can say y to build it into the kernel,
73 You can say y to build it into the kernel, or m to
81 synthesizer. You can say y to build it into the kernel,
90 synthesizer. You can say y to build it into the kernel,
100 kernel, or m to build it as a module. See the
134 kernel, or m to build it as a module. See the
145 kernel, or m to build it as a module. See the
[all …]
|
| /linux-4.4.14/Documentation/sysctl/ |
| D | kernel.txt | 1 Documentation for /proc/sys/kernel/* kernel version 2.2.10
10 /proc/sys/kernel/ and is valid for Linux kernel version 2.2.
14 kernel. Since some of the files _can_ be used to screw up your
19 show up in /proc/sys/kernel:
115 See Doc*/kernel/power/video.txt, it allows mode of video boot to be
122 This variable has no effect and may be removed in future kernel
139 type_of_loader field in the kernel header; the encoding is kept for
163 Controls the kernel's callhome behavior in case of a kernel panic.
169 nothing happens in case of a kernel panic. If this value is set to "1"
170 the complete kernel oops message is send to the IBM customer service
[all …]
|
| D | sunrpc.txt | 1 Documentation for /proc/sys/sunrpc/* kernel version 2.2.10
9 /proc/sys/sunrpc and is valid for Linux kernel version 2.2.
13 the Linux kernel. This stuff is used for NFS, KNFSD and
19 These flags are for kernel hackers only. You should read the
|
| /linux-4.4.14/arch/openrisc/ |
| D | Kconfig | 57 source "kernel/Kconfig.freezer"
104 source kernel/Kconfig.hz
105 source kernel/Kconfig.preempt
122 string "Default kernel command string"
126 to pass arguments to the kernel. For these architectures, you should
136 Now this puts kernel into infinite loop after first oops. Till
137 your kernel crashes this doesn't have any influence.
146 in kernel.
|
| /linux-4.4.14/Documentation/ABI/ |
| D | README | 1 This directory attempts to document the ABI between the Linux kernel and
30 these interfaces, so that the kernel developers can easily
36 the kernel, but are marked to be removed at some later point in
42 been removed from the kernel.
53 the "testing" stage, so that kernel developers can work
66 Interfaces may be removed from obsolete and the kernel as long as the
71 kernel tree without going through the obsolete state first.
82 commonly installed to /boot, or in any invocation of the kernel build
86 type of any kernel symbol, either in System.map files or the kernel binary
|
| /linux-4.4.14/tools/lguest/ |
| D | lguest.txt | 6 Lguest is designed to be a minimal 32-bit x86 hypervisor for the Linux kernel,
14 - Kernel module which runs in a normal kernel.
22 - No ABI: being tied to a specific kernel anyway, you can change anything.
27 - The easiest way to run lguest is to use same kernel as guest and host.
30 You will need to configure your kernel with the following options:
36 "Alignment value to which kernel should be aligned" = 0x100000
53 to build it. If you didn't build your kernel in-tree, use "make
79 vmlinux: the kernel image found in the top of your build directory. You
89 kernel boot parameters.
120 to provide entropy to the guest kernel's /dev/random.
|
| /linux-4.4.14/arch/mips/ |
| D | Kconfig.debug | 14 This option enables special console drivers which allow the kernel
17 This is useful for kernel debugging when your machine crashes very
36 bool "Built-in kernel command line"
40 by default specifies the kernel command line options. However,
42 default kernel command line or add a few extra options to it.
44 command line options directly into the kernel. For that, you
56 string "Default kernel command string"
61 pass arguments to the kernel. For these platforms, and for the cases
65 kernel args so that you don't have to set them up in board prom
76 By setting this option to 'Y' you will have your kernel ignore
[all …]
|
| /linux-4.4.14/Documentation/virtual/ |
| D | 00-INDEX | 1 Virtualization support in the Linux kernel.
7 - Describes the Linux kernel pv_ops to support different hypervisors
11 - User Mode Linux, builds/runs Linux kernel as a userspace program.
|
| /linux-4.4.14/Documentation/vm/ |
| D | highmem.txt | 27 impossible for the kernel to keep all of the available physical memory mapped
28 at all times. This means the kernel needs to start using temporary mappings of
35 In the i386 arch, for example, we choose to map the kernel into every process's
37 kernel entry/exit. This means the available virtual memory space (4GiB on
38 i386) has to be divided between user and kernel space.
41 userspace and the top 1GiB for kernel space:
51 This means that the kernel can at most map 1GiB of physical memory at any one
56 Other architectures that have mm context tagged TLBs can have separate kernel
65 The kernel contains several ways of creating temporary mappings:
128 manipulate the kernel's page tables, the data TLB and/or the MMU's registers.
[all …]
|
| /linux-4.4.14/fs/proc/ |
| D | Kconfig | 7 your hard disk: the files are created on the fly by the kernel when
28 This option will enlarge your kernel by about 67 KB. Several
35 Provides a virtual ELF core file of the live kernel. This can
44 Exports the dump image of crashed kernel in ELF format.
53 certain kernel parameters and variables on the fly without requiring
54 a recompile of the kernel or reboot of the system. The primary
59 option will enlarge the kernel by at least 8 KB.
62 building a kernel for install/rescue disks or your system is very
73 interfaces will reduce the size of the kernel by approximately 4kb.
|
| /linux-4.4.14/arch/mips/cavium-octeon/ |
| D | Kconfig | 29 bool "Build the kernel to be used as a 2nd kernel on the same chip"
32 This option configures this kernel to be linked at a different
33 address and use the 2nd uart for output. This allows a kernel built
38 bool "Lock often used kernel code in the L2"
41 Enable locking parts of the kernel into the L2 cache.
76 Lock the kernel's implementation of memcpy() into L2.
|
| /linux-4.4.14/Documentation/target/ |
| D | tcmu-design.txt | 24 TCM is another name for LIO, an in-kernel iSCSI target (server).
25 Existing TCM targets run in the kernel. TCMU (TCM in Userspace)
29 The existing kernel provides modules for different SCSI transport
33 built-in modules are implemented entirely as kernel code.
38 SCSI commands ("fabrics"), the Linux kernel target, LIO, also modularizes
43 these are implemented entirely as kernel code.
46 use case that other non-kernel target solutions, such as tgt, are able
57 difficult, because LIO is entirely kernel code. Instead of undertaking
59 kernel, another approach is to create a userspace pass-through
83 - Allow future flexibility in user & kernel implementations
[all …]
|