Home
last modified time | relevance | path

Searched refs:ran (Results 1 – 25 of 40) sorted by relevance

12

/Linux-v6.1/tools/tracing/rtla/src/
Drtla.c49 goto ran; in run_command()
52 goto ran; in run_command()
56 ran: in run_command()
/Linux-v6.1/Documentation/admin-guide/
Dnumastat.rst34 local_node A process ran on this node's CPU,
37 other_node A process ran on a different node's CPU
Dmono.rst61 4) Check that ``.exe`` binaries can be ran without the need of a
/Linux-v6.1/drivers/gpu/drm/stm/
Dltdc.c666 enum drm_color_range ran = state->color_range; in ltdc_set_ycbcr_coeffs() local
675 if (ran != DRM_COLOR_YCBCR_LIMITED_RANGE && ran != DRM_COLOR_YCBCR_FULL_RANGE) { in ltdc_set_ycbcr_coeffs()
676 DRM_ERROR("color range %d not supported, use limited range by default\n", ran); in ltdc_set_ycbcr_coeffs()
678 ran = DRM_COLOR_YCBCR_LIMITED_RANGE; in ltdc_set_ycbcr_coeffs()
681 DRM_DEBUG_DRIVER("Color encoding=%d, range=%d\n", enc, ran); in ltdc_set_ycbcr_coeffs()
683 ltdc_ycbcr2rgb_coeffs[enc][ran][0]); in ltdc_set_ycbcr_coeffs()
685 ltdc_ycbcr2rgb_coeffs[enc][ran][1]); in ltdc_set_ycbcr_coeffs()
/Linux-v6.1/tools/memory-model/scripts/
DREADME48 judge whether the test ran correctly. Not normally run manually,
/Linux-v6.1/drivers/nvme/target/
Dfc.c1110 u64 ran; in nvmet_fc_alloc_target_assoc() local
1137 get_random_bytes(&ran, sizeof(ran) - BYTES_FOR_QID); in nvmet_fc_alloc_target_assoc()
1138 ran = ran << BYTES_FOR_QID_SHIFT; in nvmet_fc_alloc_target_assoc()
1143 if (ran == tmpassoc->association_id) { in nvmet_fc_alloc_target_assoc()
1149 assoc->association_id = ran; in nvmet_fc_alloc_target_assoc()
/Linux-v6.1/Documentation/RCU/
Dtorture.rst87 * "nt": The number of times rcutorture ran RCU read-side code from
244 "TREE04"). If a given scenario ran more than once (as in "--configs
250 If the test ran in a git repository, then this file contains the commit
Dstallwarn.rst43 ran and how often it should be expected to run. It can also
297 since the grace-period kthread ran. The "jiffies_till_next_fqs"
317 kthread last ran on CPU 5.
332 Here "cpu" indicates that the grace-period kthread last ran on CPU 4,
/Linux-v6.1/Documentation/driver-api/usb/
Dbulk-streams.rst44 streams, or the xHCI driver ran out of memory), or the number of streams the
/Linux-v6.1/Documentation/timers/
Dhrtimers.rst152 the hrtimer implementation details in praxis, and we also ran the posix
153 timer tests in order to ensure specification compliance. We also ran
/Linux-v6.1/Documentation/ABI/testing/
Dsysfs-devices-platform-stratix10-rsu113 2 both first and second stage bootloader ran
Dsysfs-bus-most282 Indicates whether channel ran out of buffers.
/Linux-v6.1/Documentation/driver-api/media/drivers/
Dradiotrack.rst26 I have a RadioTrack card from back when I ran an MS-Windows platform. After
/Linux-v6.1/Documentation/driver-api/
Disa.rst9 pointed out that (ALSA) ISA drivers ran into the problem of not having
/Linux-v6.1/Documentation/scheduler/
Dsched-stats.rst147 last ran on a different cpu in this domain
/Linux-v6.1/Documentation/dev-tools/kunit/
Drunning_tips.rst169 Then we'd see output like this in dmesg signaling the test ran and passed:
Drun_wrapper.rst314 might pass/fail based on what ran before it.
/Linux-v6.1/Documentation/ABI/stable/
Dsysfs-driver-ib_srp190 request to the target because it ran out of credits. For more
/Linux-v6.1/drivers/staging/most/Documentation/ABI/
Dsysfs-class-most.txt314 Indicates whether current channel ran out of buffers.
/Linux-v6.1/tools/memory-model/Documentation/
Dglossary.txt168 store after earlier memory references that ran on that same CPU.
/Linux-v6.1/drivers/mtd/nand/raw/
Dmeson_nand.c63 #define CMDRWGEN(cmd_dir, ran, bch, short_mode, page_size, pages) \ argument
66 ((ran) << 19) | \
/Linux-v6.1/Documentation/sparc/oradax/
Doracle-dax.rst367 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
433 if (completion_area[0] != 1) { /* section 36.2.2, 1 = command ran and succeeded */
/Linux-v6.1/tools/perf/Documentation/
Dperf-report.txt88 - cpu: cpu number the task ran at the time of sample
89 - socket: processor socket number the task ran at the time of sample
/Linux-v6.1/Documentation/process/
D3.Early-stage.rst28 the linux-kernel mailing list, where it immediately ran into problems.
/Linux-v6.1/Documentation/driver-api/nvdimm/
Dnvdimm.rst554 1. Why not "volume" for instance? "volume" ran the risk of confusing

12