| /external/llvm/test/CodeGen/X86/ |
| D | stack-protector.ll | 1 ; RUN: llc -mtriple=i386-pc-linux-gnu < %s -o - | FileCheck --check-prefix=LINUX-I386 %s
2 ; RUN: llc -mtriple=x86_64-pc-linux-gnu < %s -o - | FileCheck --check-prefix=LINUX-X64 %s
3 ; RUN: llc -code-model=kernel -mtriple=x86_64-pc-linux-gnu < %s -o - | FileCheck --check-prefix=LIN…
4 ; RUN: llc -mtriple=x86_64-apple-darwin < %s -o - | FileCheck --check-prefix=DARWIN-X64 %s
5 ; RUN: llc -mtriple=amd64-pc-openbsd < %s -o - | FileCheck --check-prefix=OPENBSD-AMD64 %s
6 ; RUN: llc -mtriple=i386-pc-windows-msvc < %s -o - | FileCheck -check-prefix=MSVC-I386 %s
29 ; LINUX-I386-LABEL: test1a:
30 ; LINUX-I386-NOT: calll __stack_chk_fail
31 ; LINUX-I386: .cfi_endproc
33 ; LINUX-X64-LABEL: test1a:
[all …]
|
| /external/arm-trusted-firmware/docs/plat/ |
| D | rpi3.rst | 4 The `Raspberry Pi 3`_ is an inexpensive single-board computer that contains four
5 Arm Cortex-A53 cores.
7 The following instructions explain how to use this port of the TF-A with the
10 officially supported kernel is a AArch32 kernel. This doesn't mean that this
11 port of TF-A can't boot a AArch64 kernel. The `Linux tree fork`_ maintained by
13 `AArch64 kernel build instructions`_.
16 which is available from both the Non-secure and Secure worlds. This port
18 elements like PSCI to support the Linux kernel.
21 ------
34 - If a file called ``kernel8.img`` is located on the ``boot`` partition of the
[all …]
|
| /external/trusty/arm-trusted-firmware/docs/plat/ |
| D | rpi3.rst | 4 The `Raspberry Pi 3`_ is an inexpensive single-board computer that contains four
5 Arm Cortex-A53 cores.
7 The following instructions explain how to use this port of the TF-A with the
10 officially supported kernel is a AArch32 kernel. This doesn't mean that this
11 port of TF-A can't boot a AArch64 kernel. The `Linux tree fork`_ maintained by
13 `AArch64 kernel build instructions`_.
16 which is available from both the Non-secure and Secure worlds. This port
18 elements like PSCI to support the Linux kernel.
21 ------
34 - If a file called ``kernel8.img`` is located on the ``boot`` partition of the
[all …]
|
| /external/google-breakpad/docs/ |
| D | linux_system_calls.md | 3 Linux implements its userland-to-kernel transition using a special library
4 called linux-gate.so that is mapped by the kernel into every process. For more
7 http://www.trilithium.com/johan/2005/08/linux-gate/
10 kernel\_vsyscall does not use EBP to point to the frame pointer.
13 lines in the symbol file. If you look in src/client/linux/data you will see
14 symbol files for linux-gate.so for both Intel & AMD(the implementation of
15 kernel\_vsyscall changes depending on the CPU manufacturer). When processing
16 minidumps from Linux 2.6, having these symbol files is necessary for walking the
24 The particular details of understanding the linux-gate.so symbol files can be
28 previous frame when the EIP is inside kernel\_vsyscall, and we do that by
[all …]
|
| /external/linux-kselftest/android/ |
| D | README.md | 7 ------------------
9 Kselftest is a collection of tests included within the Linux kernel repository
15 22 of these tests are executed in both 32-bit and 64-bit mode. There are many
20 ----------------------------
22 The Kselftest source is located at external/linux-kselftest in the Android
24 repository from the Linux kernel repository. This is not an exact mirror of
28 is located at test/vts-testcase/kernel/linux_kselftest. Some noteworthy
31 * `external/linux-kselftest/Android.bp`: Lists build rules for the kselftest modules built in Soong.
32 * `external/linux-kselftest/android/`: Contains Android-specific files, aside from Android.[bp, mk]…
33 * `external/linux-kselftest/android/README`: Lists details on why particular tests are not enabled …
[all …]
|
| /external/toybox/mkroot/ |
| D | README | 1 mkroot - simple linux system builder
3 Compiles a toybox-based root filesystem and kernel that can boot under qemu.
6 launched via ./run-qemu.sh (which assumes you have QEMU installed, KVM
12 --- Quick Start
14 To install the build prerequisites: download toybox source, linux kernel source,
18 $ git clone https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux
19 $ wget https://landley.net/bin/toolchains/latest/i686-linux-musl-cross.tar.xz
21 $ tar xvJCf ccc i686-linux-musl-cross.tar.xz
25 $ mkroot/mkroot.sh CROSS=i686 LINUX=linux
26 $ root/i686/run-qemu.sh
[all …]
|
| /external/mesa3d/docs/ci/ |
| D | kernel.rst | 1 Upreving Linux Kernel
4 Occasionally, the GitLab CI needs a Linux Kernel update to enable new kernel
6 Kernel uprevs in GitLab CI are relatively simple, but prone to lots of
7 side-effects since many devices from different platforms are involved in the
10 Kernel repository
11 -----------------
13 The Linux Kernel used in the GitLab CI is stored at the following repository:
14 https://gitlab.freedesktop.org/gfx-ci/linux
16 It is common that Mesa kernel brings some patches that were not merged on the
17 Linux mainline, that is why Mesa has its own kernel version which should be used
[all …]
|
| /external/libbpf/ |
| D | SYNC.md | 2 …<source media="(prefers-color-scheme: dark)" srcset="assets/libbpf-logo-sideways-darkbg.png" width…
3 <img src="assets/libbpf-logo-sideways.png" width="40%">
9 Libbpf *authoritative source code* is developed as part of [bpf-next Linux source
10 tree](https://kernel.googlesource.com/pub/scm/linux/kernel/git/bpf/bpf-next) under
13 Most of the mundane mechanical things like bpf and bpf-next tree merge, Git
14 history transformation, cherry-picking relevant commits, re-generating
15 auto-generated headers, etc. are taken care by
16 [sync-kernel.sh script](https://github.com/libbpf/libbpf/blob/master/scripts/sync-kernel.sh).
20 This document goes over the process of syncing libbpf sources from Linux repo
25 ------------------
[all …]
|
| /external/bcc/ |
| D | INSTALL.md | 3 * [Kernel Configuration](#kernel-configuration)
5 - [Debian](#debian---binary)
6 - [Ubuntu](#ubuntu---binary)
7 - [Fedora](#fedora---binary)
8 - [Arch](#arch---binary)
9 - [Gentoo](#gentoo---portage)
10 - [openSUSE](#opensuse---binary)
11 - [RHEL](#rhel---binary)
12 - [Amazon Linux 1](#amazon-linux-1---binary)
13 - [Amazon Linux 2](#amazon-linux-2---binary)
[all …]
|
| /external/ltp/testcases/kernel/device-drivers/v4l/user_space/doc/ |
| D | results.html | 1 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
4 <meta content="text/html;charset=ISO-8859-2" http-equiv="Content-Type">
5 <title>v4l-test: Resutls</title>
14 <h1>v4l-test: Results</h1>
16 The following list collects the problems which were found by using the v4l-test
22 …<a href="http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=8bbd90ce80d39…
23 …V4L/DVB (11293): uvcvideo: Add zero fill for VIDIOC_ENUM_FMT</a> in mainline kernel since 2.6.30-r…
27 <a href="http://marc.info/?l=linux-kernel&m=123800004409412&w=2">
29 <a href="http://marc.info/?l=linux-kernel&m=123818844519630&w=2">
34 <a href="http://marc.info/?l=linux-kernel&m=123750098719906&w=2">
[all …]
|
| /external/libtracefs/ |
| D | README | 4 https://git.kernel.org/pub/scm/libs/libtrace/libtracefs.git/
8 https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
41 linux-trace-users@vger.kernel.org
43 Subscribe: http://vger.kernel.org/vger-lists.html#linux-trace-users
44 Archives: https://lore.kernel.org/linux-trace-users/
48 linux-trace-devel@vger.kernel.org
50 Subscribe: http://vger.kernel.org/vger-lists.html#linux-trace-devel
51 Archives: https://lore.kernel.org/linux-trace-devel/
54 by the Linux kernel.
56 https://www.kernel.org/doc/html/v5.4/process/submitting-patches.html
|
| /external/ltp/testcases/open_posix_testsuite/conformance/interfaces/mmap/ |
| D | coverage.txt | 42 11-2: Will fail with glibc-2.3 & linux kernel 2.6.0-test2.
45 11-3: Same as 11-2.
47 13-1: Will fail with glibc-2.3 & linux kernel 2.6.0-test2.
50 14-1: Will fail with glibc-2.3 & linux kernel 2.6.0-test2.
53 24-2: Will fail with glibc-2.3 & linux kernel 2.6.0-test2.
56 25-1: Freezes with glibc-3.4 & linux kernel 2.5.67
58 28-1: Will fail with glibc-2.3 & linux kernel 2.6.0-test2.
60 29-1: Will trigger SIGBUS (freezes with glibc-3.4 * linux kernel 2.5.67)
62 31-1: Will fail with glibc-2.3 & linux kernel 2.6.0-test2.
|
| /external/libtraceevent/ |
| D | README | 4 https://git.kernel.org/pub/scm/libs/libtrace/libtraceevent.git/
37 linux-trace-users@vger.kernel.org
39 Subscribe: http://vger.kernel.org/vger-lists.html#linux-trace-users
40 Archives: https://lore.kernel.org/linux-trace-users/
44 linux-trace-devel@vger.kernel.org
46 Subscribe: http://vger.kernel.org/vger-lists.html#linux-trace-devel
47 Archives: https://lore.kernel.org/linux-trace-devel/
50 by the Linux kernel.
52 https://www.kernel.org/doc/html/v5.4/process/submitting-patches.html
|
| /external/rust/crates/memmap2/src/ |
| D | advice.rs | 2 /// See [madvise()](https://man7.org/linux/man-pages/man2/madvise.2.html) map page.
10 pub fn normal() -> Self { in normal()
18 pub fn random() -> Self { in random()
27 pub fn sequential() -> Self { in sequential()
35 pub fn will_need() -> Self { in will_need()
43 /// so the kernel can free resources associated with it.)
49 /// from the up-to-date contents of the underlying mapped file
51 /// shmem-based techniques such as System V shared memory
52 /// segments) or zero-fill-on-demand pages for anonymous
57 /// range. The kernel is free to delay freeing the pages
[all …]
|
| /external/seccomp-tests/ |
| D | README.md | 1 # Seccomp-BPF Kernel Self-Test Suite
3 This repository contains a mirror of the upstream Linux kernel test suite for the Seccomp-BPF
9 Rather than hold the entire Linux history in this repository, only the subdirectory for the Seccomp
10 selftests are preserved here. In order to sync this repository to the upstream Linux, follow these
13 The pristine copy of the upstream source is kept on a branch called upstream-master. This branch is
16 ### First-Time Setup
23 …git remote add upstream-linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git -t …
32 git remote update upstream-linux
37 git checkout -b update-YYYYMMDD upstream-linux/master
42 git filter-branch --subdirectory-filter tools/testing/selftests/seccomp
[all …]
|
| /external/bpftool/scripts/ |
| D | README.md | 5 ## gh-label-release-assets.sh
22 ## sync-kernel.sh
24 ### Synchronize Linux and bpftool mirror
27 related files) from the Linux kernel repository.
29 Synchronization is usually performed against the `bpf-next` and `bpf` trees,
36 to the latest `bpf-next` and `bpf` tree, and records to what kernel commits it
37 was brought up-to-date. To ensure optimal compatibility between the bpftool
46 However, you need a local copy of the Linux Git repository on your system
50 $ git clone 'https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git' linux
51 $ cd linux
[all …]
|
| /external/rust/crates/rustix/src/thread/ |
| D | id.rs | 12 /// - [Linux]
14 /// [Linux]: https://man7.org/linux/man-pages/man2/gettid.2.html
17 pub fn gettid() -> Pid { in gettid()
26 /// process granular, but on Linux they are per-thread. Thus, this call only
30 /// For details on this distinction, see the C library vs. kernel differences
31 /// in the [manual page][linux_notes]. This call implements the kernel
35 /// - [POSIX]
36 /// - [Linux]
39 /// [Linux]: https://man7.org/linux/man-pages/man2/setuid.2.html
40 /// [linux_notes]: https://man7.org/linux/man-pages/man2/setuid.2.html#NOTES
[all …]
|
| /external/toolchain-utils/compiler_wrapper/testdata/cros_nonhardened_golden/ |
| D | gcc_sanitizer_args.json | 7 "./x86_64-cros-linux-gnu-gcc.real",
8 "--sysroot=/usr/x86_64-cros-linux-gnu",
9 "-Wno-maybe-uninitialized",
10 "-Wno-unused-local-typedefs",
11 "-Wno-deprecated-declarations",
12 "-Wtrampolines",
13 "-static-libgcc",
14 "-fsanitize=kernel-address",
16 "-L/usr/x86_64-cros-linux-gnu/usr/lib64",
17 "-mno-movbe"
[all …]
|
| /external/trusty/arm-trusted-firmware/plat/marvell/armada/a3k/common/ |
| D | a3700_ea.c | 4 * SPDX-License-Identifier: BSD-3-Clause
21 * building TF-A with compile option HANDLE_EA_EL3_FIRST_NS=1
32 * In most cases this indicates a bug in U-Boot or Linux kernel driver in plat_ea_handler()
33 * pci-aardvark.c which implements access to A3700 PCIe config space. in plat_ea_handler()
39 * Following patches fix that bug in U-Boot and Linux kernel drivers: in plat_ea_handler()
40 * https://source.denx.de/u-boot/u-boot/-/commit/eccbd4ad8e4e182638eafbfb87ac139c04f24a01 in plat_ea_handler()
41 * https://git.kernel.org/stable/c/f18139966d072dab8e4398c95ce955a9742e04f7 in plat_ea_handler()
43 * As a hacky workaround for unpatched U-Boot and Linux kernel drivers in plat_ea_handler()
53 * hack that we need only because of bugs in old U-Boot and Linux kernel in plat_ea_handler()
54 * versions and because it was decided that TF-A would implement this in plat_ea_handler()
[all …]
|
| /external/toolchain-utils/compiler_wrapper/testdata/cros_hardened_golden/ |
| D | gcc_sanitizer_args.json | 7 "./x86_64-cros-linux-gnu-gcc.real",
8 "--sysroot=/usr/x86_64-cros-linux-gnu",
9 "-fno-reorder-blocks-and-partition",
10 "-Wno-unused-local-typedefs",
11 "-Wno-maybe-uninitialized",
12 "-fcommon",
13 "-fstack-protector-strong",
14 "-D_FORTIFY_SOURCE=3",
15 "-fno-omit-frame-pointer",
16 "-static-libgcc",
[all …]
|
| /external/trace-cmd/ |
| D | CONTRIBUTE | 2 to do so for trace-cmd.
7 https://bugzilla.kernel.org/buglist.cgi?component=Trace-cmd%2FKernelshark
11 http://vger.kernel.org/vger-lists.html#linux-trace-devel
13 Patches should be sent to linux-trace-devel@vger.kernel.org
17 git clone git://git.kernel.org/pub/scm/utils/trace-cmd/trace-cmd.git
33 trace-cmd: Add CONTRIBUTE file
35 Even though this repo is for trace-cmd, start the topic with
36 "trace-cmd:" because the commits will end up as patches to a mailing
39 "record" command, you may start the title with "trace-cmd record:".
46 is. You can make statements like "This is needed for a <future-feature>
[all …]
|
| /external/arm-trusted-firmware/plat/marvell/armada/a3k/common/ |
| D | a3700_ea.c | 4 * SPDX-License-Identifier: BSD-3-Clause
27 return "S-EL1"; in get_el_str()
33 * building TF-A with compile option HANDLE_EA_EL3_FIRST=1
44 * In most cases this indicates a bug in U-Boot or Linux kernel driver in plat_ea_handler()
45 * pci-aardvark.c which implements access to A3700 PCIe config space. in plat_ea_handler()
51 * Following patches fix that bug in U-Boot and Linux kernel drivers: in plat_ea_handler()
52 * https://source.denx.de/u-boot/u-boot/-/commit/eccbd4ad8e4e182638eafbfb87ac139c04f24a01 in plat_ea_handler()
53 * https://git.kernel.org/stable/c/f18139966d072dab8e4398c95ce955a9742e04f7 in plat_ea_handler()
55 * As a hacky workaround for unpatched U-Boot and Linux kernel drivers in plat_ea_handler()
65 * hack that we need only because of bugs in old U-Boot and Linux kernel in plat_ea_handler()
[all …]
|
| /external/iproute2/man/man8/ |
| D | tc-bpf.8 | 1 .TH "BPF classifier and actions in tc" 8 "18 May 2015" "iproute2" "Linux"
3 BPF \- BPF programmable classifier and actions for ingress/egress
9 .B object-file
30 .B object-file
42 .B bytecode-file
55 .B bytecode-file
69 implementing small programs which can safely be loaded into the kernel
70 and thus executed in a tiny virtual machine from kernel space. An in-kernel
72 crashes nor leaks data from the kernel.
74 In Linux, it's generally considered that eBPF is the successor of cBPF.
[all …]
|
| /external/bpftool/ |
| D | README.md | 4 This is a mirror of [bpf-next Linux source tree's
5 `tools/bpf/bpftool`](https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/tree/tools/bp…
6 directory, plus its few dependencies from under `kernel/bpf/`, and its
9 All the gory details of syncing can be found in `scripts/sync-kernel.sh`
12 Some header files in this repo (`include/linux/*.h`) are reduced versions of
14 [bpf-next](https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf-next.git/)'s
15 `tools/include/linux/*.h` to make compilation successful.
18 -------------------------------
22 post](https://qmonnet.github.io/whirl-offload/2021/09/23/bpftool-features-thread/).
24 All general BPF questions, including kernel functionality, bpftool features and
[all …]
|
| /external/ltp/.github/ |
| D | pull_request_template.md | 3 <!--
4 … requests, the *preferred* way is sending patches to our mailing list: https://lore.kernel.org/ltp/
5 …tps://github.com/linux-test-project/ltp/wiki/C-Test-Case-Tutorial#7-submitting-the-test-for-review…
6 LTP mailing list is archived at: https://lore.kernel.org/ltp/.
9 * Commits should be signed: Signed-off-by: Your Name <me@example.org>, see
10 https://www.kernel.org/doc/html/latest/process/submitting-patches.html#sign-your-work-the-developer…
13 https://www.kernel.org/doc/html/latest/process/submitting-patches.html#split-changes
14 https://www.kernel.org/doc/html/latest/process/submitting-patches.html#describe-your-changes
15 https://cbea.ms/git-commit/
17 * New code should follow Linux kernel coding style, see
[all …]
|