Searched refs:lay (Results 1 – 18 of 18) sorted by relevance
| /linux/arch/s390/kernel/ |
| H A D | reipl.S | 32 lay %r1,__LC_FPREGS_SAVE_AREA(%r13)
50 lay %r1,__LC_FP_CREG_SAVE_AREA(%r13)
53 lay %r1,__LC_CPU_TIMER_SAVE_AREA(%r13)
56 lay %r1,__LC_PREFIX_SAVE_AREA(%r13)
61 lay %r1,__LC_CLOCK_COMP_SAVE_AREA(%r13)
64 lay %r1,__LC_PSW_SAVE_AREA(%r13)
|
| H A D | entry.S | 166 lay %r4,__TASK_pid(%r3)
|
| /linux/drivers/net/ethernet/mellanox/mlx5/core/ |
| H A D | cmd.c | 275 ent->lay->sig = ~xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in set_signature()
292 own = READ_ONCE(ent->lay->status_own); in poll_timeout()
315 sig = xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in verify_signature()
900 dump_buf(ent->lay->in, sizeof(ent->lay->in), 1, offset, ent->idx); in dump_command()
901 offset += sizeof(ent->lay->in); in dump_command()
903 dump_buf(ent->lay->out, sizeof(ent->lay->out), 1, offset, ent->idx); in dump_command()
904 offset += sizeof(ent->lay->out); in dump_command()
907 dump_buf(ent->lay, sizeof(*ent->lay), 0, offset, ent->idx); in dump_command()
908 offset += sizeof(*ent->lay); in dump_command()
984 struct mlx5_cmd_layout *lay; in cmd_work_handler() local
[all …]
|
| H A D | pagealloc.c | 693 struct mlx5_cmd_layout *lay; in optimal_reclaimed_pages() local
696 ret = (sizeof(lay->out) + MLX5_BLKS_FOR_RECLAIM_PAGES * sizeof(block->data) - in optimal_reclaimed_pages()
|
| /linux/arch/s390/net/ |
| H A D | bpf_timed_may_goto.S | 33 lay %r15,-FRAME_SIZE(%r15)
36 lay %r2,0(%r12,%r13)
|
| /linux/Documentation/userspace-api/media/v4l/ |
| H A D | vidioc-g-selection.rst | 77 rectangle. The original rectangle must lay inside the adjusted one.
80 rectangle. The adjusted rectangle must lay inside the original one.
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | group_descr.rst | 17 property to group several block groups into a flex group and lay out all
|
| /linux/Documentation/core-api/ |
| H A D | packing.rst | 45 logically. The question is: where do we lay this bit out in memory?
|
| /linux/include/linux/mlx5/ |
| H A D | driver.h | 846 struct mlx5_cmd_layout *lay; member
|
| /linux/Documentation/driver-api/ |
| H A D | xillybus.rst | 304 to lay around in the DMA buffers between read() and write() anyhow.
|
| /linux/Documentation/devicetree/ |
| H A D | usage-model.rst | 258 About now is a good time to lay out an example. Here is part of the
|
| /linux/arch/s390/tools/ |
| H A D | opcodes.txt | 814 e371 lay RXY_RRRD
|
| /linux/Documentation/process/ |
| H A D | 2.Process.rst | 484 you can lay your hands on". Usually the way to do this is to work
|
| /linux/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 460 - Revamp slightly the Symbios NVRAM lay-out based on the excerpt of
|
| /linux/Documentation/bpf/ |
| H A D | bpf_devel_QA.rst | 53 The following steps lay out how to start a CI run for your patches:
|
| /linux/Documentation/admin-guide/ |
| H A D | verify-bugs-and-bisect-regressions.rst | 277 The following steps lay the groundwork for all further tasks.
1086 *The steps in this section lay the groundwork for all further tests.*
|
| H A D | reporting-issues.rst | 1741 art will lay some groundwork to improve the situation over time.
|
| H A D | cgroup-v2.rst | 3270 to lay programs.
|