| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/arm/gcc-arm-10.3-2021.07-x86_64-arm-none-linux-gnueabihf/lib/gcc/arm-none-linux-gnueabihf/10.3.1/plugin/include/ |
| H A D | tree-ssa-live.h | 73 /* True if this map is for out-of-ssa, otherwise for live range
201 /* ---------------- live on entry/exit info ------------------------------
203 This structure is used to represent live range information on SSA based
205 live-on-entry information and live-on-exit information can be calculated.
206 As well, partitions are marked as to whether they are global (live
209 The live-on-entry information is per block. It provide a bitmap for
210 each block which has a bit set for each partition that is live on entry to
213 The live-on-exit information is per block. It provides a bitmap for each
214 block indicating which partitions are live on exit from the block.
219 Uses in a PHI are considered LIVE-ON-EXIT to the block from which they
[all …]
|
| /OK3568_Linux_fs/prebuilts/gcc/linux-x86/aarch64/gcc-arm-10.3-2021.07-x86_64-aarch64-none-linux-gnu/lib/gcc/aarch64-none-linux-gnu/10.3.1/plugin/include/ |
| H A D | tree-ssa-live.h | 73 /* True if this map is for out-of-ssa, otherwise for live range
201 /* ---------------- live on entry/exit info ------------------------------
203 This structure is used to represent live range information on SSA based
205 live-on-entry information and live-on-exit information can be calculated.
206 As well, partitions are marked as to whether they are global (live
209 The live-on-entry information is per block. It provide a bitmap for
210 each block which has a bit set for each partition that is live on entry to
213 The live-on-exit information is per block. It provides a bitmap for each
214 block indicating which partitions are live on exit from the block.
219 Uses in a PHI are considered LIVE-ON-EXIT to the block from which they
[all …]
|
| /OK3568_Linux_fs/kernel/tools/testing/selftests/livepatch/ |
| H A D | test-livepatch.sh | 21 if [[ "$(cat /proc/cmdline)" != "$MOD_LIVEPATCH: this has been live patched" ]] ; then
29 if [[ "$(cat /proc/cmdline)" == "$MOD_LIVEPATCH: this has been live patched" ]] ; then
58 grep 'live patched' /proc/cmdline > /dev/kmsg
59 grep 'live patched' /proc/meminfo > /dev/kmsg
63 grep 'live patched' /proc/cmdline > /dev/kmsg
64 grep 'live patched' /proc/meminfo > /dev/kmsg
69 grep 'live patched' /proc/cmdline > /dev/kmsg
70 grep 'live patched' /proc/meminfo > /dev/kmsg
75 grep 'live patched' /proc/cmdline > /dev/kmsg
76 grep 'live patched' /proc/meminfo > /dev/kmsg
[all …]
|
| /OK3568_Linux_fs/kernel/Documentation/ABI/testing/ |
| H A D | sysfs-kernel-livepatch | 4 Contact: live-patching@vger.kernel.org
6 Interface for kernel live patching
9 each loaded live patch module.
14 Contact: live-patching@vger.kernel.org
22 Contact: live-patching@vger.kernel.org
31 Contact: live-patching@vger.kernel.org
39 Contact: live-patching@vger.kernel.org
53 Contact: live-patching@vger.kernel.org
61 Contact: live-patching@vger.kernel.org
|
| /OK3568_Linux_fs/kernel/Documentation/devicetree/ |
| H A D | of_unittest.rst | 13 is attached to the live tree dynamically, independent of the machine's
117 blob. And finally, if the machine's device tree (i.e live tree) is present,
118 then it attaches the unflattened test data tree to the live tree, else it
119 attaches itself as a live device tree.
122 live tree as explained below. To explain the same, the test data tree described
123 in Figure 2 is attached to the live tree described in Figure 1::
134 Figure 2: Example test data tree to be attached to live tree.
136 According to the scenario above, the live tree is already present so it isn't
141 given parent in live tree. But, if parent already has a child then the new node
143 data node is attached to the live tree above (Figure 1), the final structure is
[all …]
|
| /OK3568_Linux_fs/buildroot/package/unscd/ |
| H A D | nscd.conf | 9 positive-time-to-live passwd 600
10 negative-time-to-live passwd 20
15 positive-time-to-live group 3600
16 negative-time-to-live group 60
22 # thus could lead to problems if the positive-time-to-live is
28 positive-time-to-live hosts 3600
29 negative-time-to-live hosts 20
|
| /OK3568_Linux_fs/device/rockchip/common/scripts/ |
| H A D | check-debian.sh | 5 if [ ! -e "/usr/share/live/build/data/debian-cd/$RK_DEBIAN_VERSION" ]; then
7 echo "Your live-build doesn't support $RK_DEBIAN_VERSION"
9 echo "sudo apt-get remove live-build"
10 echo "git clone https://salsa.debian.org/live-team/live-build.git --depth 1 -b debian/1%20230131"
11 echo "cd live-build"
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-core/initrdscripts/ |
| H A D | initramfs-module-setup-live_1.0.bb | 1 SUMMARY = "initramfs-framework module for live booting"
11 SRC_URI = "file://setup-live"
17 install -m 0755 ${WORKDIR}/setup-live ${D}/init.d/80-setup-live
20 FILES:${PN} = "/init.d/80-setup-live"
|
| /OK3568_Linux_fs/yocto/poky/meta/recipes-extended/images/ |
| H A D | core-image-testcontroller-initramfs.bb | 4 # use -testfs live-install scripts
5 PACKAGE_INSTALL = "initramfs-live-boot initramfs-live-install-testfs initramfs-live-install-efi-tes…
23 # Use the same restriction as initramfs-live-install-testfs
|
| /OK3568_Linux_fs/buildroot/docs/manual/ |
| H A D | beyond-buildroot.txt | 24 ==== Live CD
26 To build a live CD image, enable the _iso image_ option in the
31 You can build a live CD image with either IsoLinux, Grub or Grub 2 as
33 as a live CD and live USB (through the _Build hybrid image_ option).
35 You can test your live CD image using QEMU:
|
| /OK3568_Linux_fs/kernel/drivers/gpu/drm/i915/selftests/ |
| H A D | i915_selftest.c | 71 int (*live)(struct drm_i915_private *); member
81 #define selftest(n, f) [live_##n] = { .name = #n, { .live = f } },
87 #define selftest(n, f) [perf_##n] = { .name = #n, { .live = f } },
160 err = st->live(data); in __run_selftests()
205 if (!i915_selftest.live) in i915_live_selftests()
208 err = run_selftests(live, pdev_to_i915(pdev)); in i915_live_selftests()
210 i915_selftest.live = err; in i915_live_selftests()
214 if (i915_selftest.live < 0) { in i915_live_selftests()
215 i915_selftest.live = -ENOTTY; in i915_live_selftests()
435 module_param_named_unsafe(live_selftests, i915_selftest.live, int, 0400);
[all …]
|
| /OK3568_Linux_fs/u-boot/doc/driver-model/ |
| H A D | livetree.txt | 1 Driver Model with Live Device Tree
13 This document describes U-Boot's support for a 'live' device tree, meaning
40 modified at run-time, a live tree is much faster. Even if no modification
41 is necessary, parsing the tree once and using a live tree from then on
48 In U-Boot a live device tree ('livetree') is currently supported only
53 node (when the live tree node is not yet set up) or a livetree node. The
63 hood it uses ofnode so it works with both flat and live device trees.
103 flat and live device trees. See include/dm/read.h for a list of functions.
171 There is full phandle support for live tree. All functions make use of
261 Live tree support was introduced in U-Boot 2017.07. There is still quite a bit
|
| /OK3568_Linux_fs/kernel/Documentation/admin-guide/media/ |
| H A D | gspca-cardlist.rst | 21 zc3xx 041e:041e Creative WebCam Live!
40 zc3xx 041e:4036 Creative Live !
44 sq930x 041e:403c Creative Live! Ultra
45 sq930x 041e:403d Creative Live! Ultra for Notebooks
46 sq930x 041e:4041 Creative Live! Motion
47 zc3xx 041e:4051 Creative Live!Cam Notebook Pro (VF0250)
48 ov519 041e:4052 Creative Live! VISTA IM
49 zc3xx 041e:4053 Creative Live!Cam Video IM
50 vc032x 041e:405b Creative Live! Cam Notebook Ultra (VC0130)
51 ov519 041e:405f Creative Live! VISTA VF0330
[all …]
|
| /OK3568_Linux_fs/kernel/net/rxrpc/ |
| H A D | net_ns.c | 18 if (rxnet->live) in rxrpc_client_conn_reap_timeout()
27 if (rxnet->live) in rxrpc_service_conn_reap_timeout()
36 if (rxnet->live) in rxrpc_peer_keepalive_timeout()
48 rxnet->live = true; in rxrpc_init_net()
107 rxnet->live = false; in rxrpc_init_net()
118 rxnet->live = false; in rxrpc_exit_net()
|
| /OK3568_Linux_fs/kernel/drivers/of/ |
| H A D | resolver.c | 231 * of_resolve_phandles - Relocate and resolve overlay against live tree
236 * does not conflict with the live expanded devicetree. Update references
238 * in @overlay that refer to the live expanded devicetree.
240 * Phandle values in the live tree are in the range of
247 * the name of a symbol (a label) in the live tree. The values of each
250 * corresponding to that symbol in the live tree. Update the references in
251 * the overlay with the phandle values in the live tree.
255 * Resolving and applying @overlay to the live expanded devicetree must be
325 pr_err("node label '%s' not found in live devicetree symbols table\n", in of_resolve_phandles()
|
| H A D | overlay.c | 29 * @in_livetree: @np is a node in the live devicetree
33 * in the live devicetree where the overlay subtree is targeted to be grafted
35 * also recurses to the next level of the live devicetree, as long as overlay
36 * subtree node also exists in the live devicetree. When a node in the overlay
37 * subtree does not exist at the same level in the live devicetree, target->np
65 * @cset: changeset to apply fragments to live device tree
98 * of_resolve_phandles() finds the largest phandle in the live tree.
99 * of_overlay_apply() may add a larger phandle to the live tree.
187 * need to be adjusted to be the correct path for the live device tree.
283 * If @overlay_prop does not already exist in live devicetree, add changeset
[all …]
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-base-arm64/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-arm64.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-lxde-armhf/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-armhf.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-gnome-arm64/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-arm64.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-xfce-arm64/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-arm64.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-base-armhf/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-armhf.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-lxde-arm64/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-arm64.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-xfce-armhf/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-armhf.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/debian/ubuntu-build-service/bullseye-gnome-armhf/ |
| H A D | Makefile | 5 # Calls all necessary live-build programs in the correct order to complete
8 # You need live-build package installed and superuser privileges.
26 sudo mv chroot.packages.live $(PKGSFILE);
27 sudo mv live-image-armhf.tar.tar.gz $(TARGZFILE);
|
| /OK3568_Linux_fs/kernel/Documentation/driver-api/nvdimm/ |
| H A D | firmware-activate.rst | 41 either 'live', or 'quiesce'. A value of 'quiesce' triggers the kernel to
44 modifications of system memory. A value of 'live' attempts
50 'live' or 'quiesce', where 'live' indicates that the firmware
53 expect and injects a quiet period for the memory controller, but 'live'
|