Searched full:live (Results 1 – 25 of 140) sorted by relevance
123456
| /Documentation/ABI/testing/ |
| 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
69 Contact: live-patching@vger.kernel.org
[all …]
|
| D | debugfs-vfio | 15 of vfio devices that support live migration.
16 The debugfs of each vfio device that supports live migration
23 Description: Read the live migration status of the vfio device.
|
| /Documentation/devicetree/ |
| D | of_unittest.rst | 13 is attached to the live tree dynamically, independent of the machine's
138 blob. And finally, if the machine's device tree (i.e live tree) is present,
139 then it attaches the unflattened test data tree to the live tree, else it
140 attaches itself as a live device tree.
143 live tree as explained below. To explain the same, the test data tree described
144 in Figure 2 is attached to the live tree described in Figure 1::
155 Figure 2: Example test data tree to be attached to live tree.
157 According to the scenario above, the live tree is already present so it isn't
162 given parent in live tree. But, if parent already has a child then the new node
164 data node is attached to the live tree above (Figure 1), the final structure is
[all …]
|
| D | dynamic-resolution-notes.rst | 19 1. Get the maximum device tree phandle value from the live tree + 1.
24 in the live tree. This is the label used to tag the node.
|
| /Documentation/driver-api/nvdimm/ |
| 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'
|
| /Documentation/devicetree/bindings/display/xlnx/ |
| D | xlnx,zynqmp-dpsub.yaml | 21 Live Video --->| | --> | Audio | Audio | |---> | PHY1 |
23 Live Audio --->| | --> | | || +-------------+ |
31 live audio/video streams from the programmable logic. The Video Rendering
72 dp_vtc_pixel_clk_in is the non-live video clock (from Processing
75 dp_live_video_in_clk is the live video clock (from Programmable
129 description: The live video input from the programmable logic
133 description: The live graphics input from the programmable logic
137 description: The live audio input from the programmable logic
|
| /Documentation/bpf/ |
| D | bpf_prog_run.rst | 49 returned to userspace. A separate mode for live execution of XDP programs is
52 Running XDP programs in "live frame mode"
55 The ``BPF_PROG_RUN`` command has a separate mode for running live XDP programs,
62 The live packet mode is optimised for high performance execution of the supplied
67 - When executing an XDP program in live frame mode, the result of the execution
80 the regular (non-live) mode. The XDP program will be executed as though the
|
| /Documentation/networking/ |
| D | net_failover.rst | 24 datapath. It also enables hypervisor controlled live migration of a VM with
65 be brought UP during live migration to allow uninterrupted communication.
113 Live Migration of a VM with SR-IOV VF & virtio-net in STANDBY mode
116 net_failover also enables hypervisor controlled live migration to be supported
120 Here is a sample script that shows the steps to initiate live migration from
153 virsh detach-device --live --config $DOMAIN $VF_XML
163 virsh migrate --live --persistent $DOMAIN qemu+ssh://$REMOTE_HOST/system
183 virsh attach-device --config --live vm01 vf.xml
|
| D | failover.rst | 17 datapath. It also allows live migration of VMs with direct attached VFs by
|
| /Documentation/admin-guide/media/ |
| 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 …]
|
| /Documentation/admin-guide/gpio/ |
| D | gpio-sim.rst | 29 **Attribute:** ``/config/gpio-sim/gpio-device/live``
33 name (e.g. ``'gpio-sim.0'``). The ``'live'`` attribute allows to trigger the
74 Once the confiuration is complete, the ``'live'`` attribute must be set to 1 in
77 successfully probed and if this doesn't happen, writing to ``'live'`` will
|
| D | gpio-virtuser.rst | 31 **Attribute:** ``/config/gpio-consumer/example-name/live``
42 The ``'live'`` attribute allows to trigger the actual creation of the device
95 Once the confiuration is complete, the ``'live'`` attribute must be set to 1 in
98 to be successfully probed and if this doesn't happen, writing to ``'live'`` will
|
| /Documentation/admin-guide/LSM/ |
| D | tomoyo.rst | 12 https://tomoyo.sourceforge.net/1.8/ubuntu12.04-live.html
13 https://tomoyo.sourceforge.net/1.8/centos6-live.html
|
| /Documentation/sound/cards/ |
| D | index.rst | 9 sb-live-mixer
|
| /Documentation/livepatch/ |
| D | reliable-stacktrace.rst | 15 functions may have live state and therefore may not be safe to patch. One way
16 to identify which functions are live is to use a stacktrace.
19 functions with live state, and best-effort approaches which can be helpful for
21 to provide a *reliable* stacktrace which ensures it never omits any live
172 location. For trampolines which are not subject to live patching, where an
262 Unwinders typically assume the link register is always live, but this
|
| /Documentation/devicetree/bindings/fpga/ |
| D | fpga-region.yaml | 121 4. The Device Tree overlay is accepted into the live tree.
143 An FPGA Region that exists in the live Device Tree reflects the current state.
144 If the live tree shows a "firmware-name" property or child nodes under an FPGA
147 FPGA. After reprogramming is successful, the overlay is accepted into the live
177 In all cases the live DT must have the FPGA Manager, FPGA Bridges (if any), and
189 applied, the live DT must include the FPGA Manager, FPGA Bridges, and a
255 search path. If this property shows up in a live device tree it indicates
|
| /Documentation/networking/device_drivers/ethernet/amd/ |
| D | pds_vfio_pci.rst | 14 The ``pds-vfio-pci`` module is a PCI driver that supports Live Migration
41 # Create single VF for Live Migration via pds_core
|
| /Documentation/admin-guide/mm/ |
| D | userfaultfd.rst | 294 machine which experiences a real hardware memory error. Later, we live migrate
303 QEMU/KVM is using the ``userfaultfd`` syscall to implement postcopy live
304 migration. Postcopy live migration is one form of memory
308 KVM kernel code had to be modified in order to add postcopy live
317 It is generally beneficial to run one pass of precopy live migration
318 just before starting postcopy live migration, in order to avoid
321 The implementation of postcopy live migration currently uses one
352 doesn't need to keep any per-page state bitmap relative to the live
|
| /Documentation/features/debug/uprobes/ |
| D | arch-support.txt | 4 # description: arch supports live patched user probes
|
| /Documentation/features/debug/kprobes/ |
| D | arch-support.txt | 4 # description: arch supports live patched kernel probe
|
| /Documentation/features/debug/optprobes/ |
| D | arch-support.txt | 4 # description: arch supports live patched optprobes
|
| /Documentation/features/core/jump-labels/ |
| D | arch-support.txt | 4 # description: arch supports live patched, high efficiency branches
|
| /Documentation/features/debug/kprobes-on-ftrace/ |
| D | arch-support.txt | 4 # description: arch supports combined kprobes and ftrace live patching
|
| /Documentation/filesystems/ext4/ |
| D | bitmaps.rst | 19 the bitmaps and group descriptor live inside the group. Unfortunately,
|
| /Documentation/devicetree/bindings/clock/ |
| D | mobileye,eyeq5-clk.yaml | 12 Its registers live in a shared region called OLB.
|
123456