| /linux-6.15/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)
|
| /linux-6.15/drivers/net/ethernet/mellanox/mlx5/core/ |
| H A D | cmd.c | 274 ent->lay->sig = ~xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in set_signature()
310 sig = xor8_buf(ent->lay, 0, sizeof(*ent->lay)); in verify_signature()
895 dump_buf(ent->lay->in, sizeof(ent->lay->in), 1, offset, ent->idx); in dump_command()
898 dump_buf(ent->lay->out, sizeof(ent->lay->out), 1, offset, ent->idx); in dump_command()
902 dump_buf(ent->lay, sizeof(*ent->lay), 0, offset, ent->idx); in dump_command()
980 struct mlx5_cmd_layout *lay; in cmd_work_handler() local
1036 ent->lay = lay; in cmd_work_handler()
1037 memset(lay, 0, sizeof(*lay)); in cmd_work_handler()
1038 memcpy(lay->in, ent->in->first.data, sizeof(lay->in)); in cmd_work_handler()
1046 lay->token = ent->token; in cmd_work_handler()
[all …]
|
| H A D | pagealloc.c | 690 struct mlx5_cmd_layout *lay; in optimal_reclaimed_pages() local
693 ret = (sizeof(lay->out) + MLX5_BLKS_FOR_RECLAIM_PAGES * sizeof(block->data) - in optimal_reclaimed_pages()
|
| /linux-6.15/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-6.15/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-6.15/Documentation/devicetree/bindings/mtd/ |
| H A D | brcm,brcmnand.yaml | 139 determines how the hardware BCH engine will lay
|
| /linux-6.15/Documentation/core-api/ |
| H A D | packing.rst | 45 logically. The question is: where do we lay this bit out in memory?
|
| /linux-6.15/include/linux/mlx5/ |
| H A D | driver.h | 830 struct mlx5_cmd_layout *lay; member
|
| /linux-6.15/Documentation/driver-api/ |
| H A D | xillybus.rst | 304 to lay around in the DMA buffers between read() and write() anyhow.
|
| /linux-6.15/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-6.15/arch/s390/tools/ |
| H A D | opcodes.txt | 814 e371 lay RXY_RRRD
|
| /linux-6.15/Documentation/process/ |
| H A D | 2.Process.rst | 487 you can lay your hands on". Usually the way to do this is to work
|
| /linux-6.15/Documentation/scsi/ |
| H A D | ChangeLog.sym53c8xx | 460 - Revamp slightly the Symbios NVRAM lay-out based on the excerpt of
|
| /linux-6.15/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-6.15/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 | 3143 to lay programs.
|