| /openbmc/qemu/target/hexagon/imported/ |
| H A D | ldst.idef | 23 #define STD_LD_AMODES(TAG,OPER,DESCR,ATTRIB,SHFT,SEMANTICS,SCALE)\
24 …io, OPER"(Rs32+#s11:"SHFT")", ATTRIB,DESCR,{fIMMEXT(siV); fEA_RI(RsV,siV); SEMANTICS; })\
25 …"(Rt32<<#u2+#U6)", ATTRIB,DESCR,{fMUST_IMMEXT(UiV); fEA_IRs(UiV,RtV,uiV); SEMANTICS;})\
26 …Re32=#U6)", ATTRIB,DESCR,{fMUST_IMMEXT(UiV); fEA_IMM(UiV); SEMANTICS; ReV=UiV; })\
27 …#_pr, OPER"(Rx32++Mu2)", ATTRIB,DESCR,{fEA_REG(RxV); fPM_M(RxV,MuV); SEMANTICS;})\
28 …pbr, OPER"(Rx32++Mu2:brev)", ATTRIB,DESCR,{fEA_BREVR(RxV); fPM_M(RxV,MuV); SEMANTICS;})\
29 …#_pi, OPER"(Rx32++#s4:"SHFT")", ATTRIB,DESCR,{fEA_REG(RxV); fPM_I(RxV,siV); SEMANTICS;})\
30 …OPER"(Rx32++#s4:"SHFT":circ(Mu2))",ATTRIB,DESCR,{fEA_REG(RxV); fPM_CIRI(RxV,siV,MuV); SEMANTICS;})\
31 …+I:circ(Mu2))", ATTRIB,DESCR,{fEA_REG(RxV); fPM_CIRR(RxV,fREAD_IREG(MuV)<<SCALE,MuV); SEMANTICS;})
104 #define STD_ST_AMODES(TAG,DEST,OPER,DESCR,ATTRIB,SHFT,SEMANTICS,SCALE)\
[all …]
|
| /openbmc/linux/drivers/net/wireless/ath/ath6kl/ |
| H A D | bmi.h | 54 * Semantics: Host is done using BMI
62 * Semantics: Host reads ATH6KL memory
73 * Semantics: Host writes ATH6KL memory
84 * Semantics: Causes ATH6KL to execute code
95 * Semantics: Set Target application starting address
104 * Semantics: Read a 32-bit Target SOC register.
114 * Semantics: Write a 32-bit Target SOC register.
126 * Semantics: Fetch the 4-byte Target information
141 * Semantics: Install a ROM Patch.
155 * Semantics: Uninstall a previously-installed ROM Patch,
[all …]
|
| /openbmc/qemu/target/hexagon/ |
| H A D | README | 22 This has all the instruction and packet semantics
25 *.idef Instruction semantics definition
63 Instruction semantics "{ RdV=RsV+RtV;}"
101 when the packet commits (see "Packet Semantics" below).
106 C semantics (aka short code)
117 The instruction semantics C code relies heavily on macros. In cases where the
118 C semantics are specified only with macros, we can override the default with
119 the short semantics option and #define the macros to generate TCG code. One
123 Instruction semantics "{ fEA_REG(RsV); fLOAD_LOCKED(1,4,u,EA,RdV) }"
159 the instruction. This makes it easy to override the instruction semantics with
[all …]
|
| H A D | gen_tcg_func_table.py | 29 "Emit opaque macro calls with instruction semantics"
31 parser.add_argument("semantics", help="semantics file")
34 hex_common.read_semantics_file(args.semantics)
|
| H A D | gen_opcodes_def.py | 31 parser.add_argument("semantics", help="semantics file")
34 hex_common.read_semantics_file(args.semantics)
|
| H A D | gen_op_attribs.py | 31 parser.add_argument("semantics", help="semantics file")
34 hex_common.read_semantics_file(args.semantics)
|
| H A D | gen_decodetree.py | 66 # They don't correspond to actual operands in the instruction semantics
197 description="Emit opaque macro calls with instruction semantics"
199 parser.add_argument("semantics", help="semantics file")
204 hex_common.read_semantics_file(args.semantics)
|
| /openbmc/linux/Documentation/kbuild/ |
| H A D | Kconfig.recursion-issue-02 | 9 # kconfig semantics which are documented here. One known practical implication
11 # drivers if they share a common core requirement and use disjoint semantics to
18 # A perhaps not so obvious implication of this is that, if semantics on these
31 # due to the disjoint use of semantics on expressing each bell's relationship
43 # problem consisted on matching semantics with newly introduced features.
|
| /openbmc/linux/Documentation/ |
| H A D | atomic_bitops.txt | 36 SEMANTICS
63 Except for a successful test_and_set_bit_lock() which has ACQUIRE semantics,
64 clear_bit_unlock() which has RELEASE semantics and test_bit_acquire which has
65 ACQUIRE semantics.
|
| /openbmc/linux/Documentation/locking/ |
| H A D | locktypes.rst | 86 Owner semantics
90 semantics:
140 rw_semaphore complies by default with the strict owner semantics, but there
193 semantics:
205 PREEMPT_RT kernel due to the PREEMPT_RT specific spinlock_t semantics.
224 The semantics of spinlock_t change with the state of PREEMPT_RT.
227 exactly the same semantics.
233 based on rt_mutex which changes the semantics:
250 PREEMPT_RT kernels preserve all other spinlock_t semantics:
309 implementation, thus changing semantics:
[all …]
|
| /openbmc/linux/arch/sparc/include/uapi/asm/ |
| H A D | fcntl.h | 23 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
25 * for O_DSYNC semantics now, but using the correct symbolic name for it.
26 * This new value is used to request true Posix O_SYNC semantics. It is
28 * new headers get at least O_DSYNC semantics on older kernels.
|
| /openbmc/linux/arch/alpha/include/uapi/asm/ |
| H A D | fcntl.h | 20 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
22 * for O_DSYNC semantics now, but using the correct symbolic name for it.
23 * This new value is used to request true Posix O_SYNC semantics. It is
25 * new headers get at least O_DSYNC semantics on older kernels.
|
| /openbmc/linux/arch/mips/include/uapi/asm/ |
| H A D | fcntl.h | 24 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
26 * for O_DSYNC semantics now, but using the correct symbolic name for it.
27 * This new value is used to request true Posix O_SYNC semantics. It is
29 * new headers get at least O_DSYNC semantics on older kernels.
|
| /openbmc/linux/include/linux/ |
| H A D | atomic.h | 16 * - Acquire: Provides ACQUIRE semantics, _acquire suffix.
17 * - Release: Provides RELEASE semantics, _release suffix.
21 * semantics apply only to the load and RELEASE semantics only to the
|
| /openbmc/linux/Documentation/devicetree/bindings/mips/cavium/ |
| H A D | ciu3.txt | 13 The second cell indicates the triggering semantics, and may have a
14 value of either 4 for level semantics, or 1 for edge semantics.
|
| /openbmc/linux/include/uapi/linux/ |
| H A D | rseq.h | 66 * semantics. This field should only be read by the thread which
78 * Read by user-space with single-copy atomicity semantics. This
106 * atomicity semantics. This field should only be updated by the
136 * user-space with single-copy atomicity semantics. This field should
144 * user-space with single-copy atomicity semantics. This field should
|
| /openbmc/qemu/docs/devel/ |
| H A D | atomics.rst | 19 and atomic operations. The semantics of concurrent memory accesses are governed
298 either *acquire* or *release* semantics\ [#rmw]_. This has two effects:
312 The concept of acquire and release semantics is not exclusive to atomic
314 acquire or release semantics. For example:
316 - ``pthread_mutex_lock`` has acquire semantics, ``pthread_mutex_unlock`` has
317 release semantics and synchronizes with a ``pthread_mutex_lock`` for the
320 - ``pthread_cond_signal`` and ``pthread_cond_broadcast`` have release semantics;
321 ``pthread_cond_wait`` has both release semantics (synchronizing with
322 ``pthread_mutex_lock``) and acquire semantics (synchronizing with
325 - ``pthread_create`` has release semantics and synchronizes with the start
[all …]
|
| /openbmc/linux/tools/testing/selftests/rseq/ |
| H A D | rseq-abi.h | 66 * semantics. This field should only be read by the thread which
78 * Read by user-space with single-copy atomicity semantics. This
106 * atomicity semantics. This field should only be updated by the
152 * user-space with single-copy atomicity semantics. This field should
160 * user-space with single-copy atomicity semantics. This field should
|
| /openbmc/linux/Documentation/bpf/ |
| H A D | graph_ds_impl.rst | 7 implementation of semantics specific to those data structures.
15 semantics or APIs are made or implied here.
30 Luckily, some restrictions which necessitated the use of BPF map semantics are
33 and semantics more closely match those exposed to the rest of the kernel.
40 Unless otherwise stated, examples and semantics below apply to both graph data
50 for kfuncs, the API and semantics for these data structures can be evolved in
116 obvious. The verifier could enforce the same semantics as for ``bpf_obj_drop``,
|
| /openbmc/u-boot/doc/imx/mkimage/ |
| H A D | mxsimage.txt | 23 Each configuration file uses very simple instruction semantics and a few
25 These semantics and rules will be outlined now.
32 - The "SECTION" instruction has the following semantics:
44 - The "TAG" instruction has the following semantics:
100 - The DCD block has the following semantics:
|
| /openbmc/linux/include/sound/ |
| H A D | snd_wavefront.h | 56 #define mpu_command_port base + 1 /* write semantics */
57 #define mpu_status_port base + 1 /* read semantics */
59 #define status_port base + 3 /* read semantics */
60 #define control_port base + 3 /* write semantics */
|
| /openbmc/linux/include/asm-generic/bitops/ |
| H A D | instrumented-lock.h | 21 * This operation is atomic and provides release barrier semantics.
51 * This operation is atomic and provides acquire barrier semantics if
68 * This operation is atomic and provides release barrier semantics.
|
| /openbmc/linux/tools/include/uapi/asm-generic/ |
| H A D | fcntl.h | 67 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
69 * for O_DSYNC semantics now, but using the correct symbolic name for it.
70 * This new value is used to request true Posix O_SYNC semantics. It is
72 * new headers get at least O_DSYNC semantics on older kernels.
|
| /openbmc/linux/include/uapi/asm-generic/ |
| H A D | fcntl.h | 67 * Before Linux 2.6.33 only O_DSYNC semantics were implemented, but using
69 * for O_DSYNC semantics now, but using the correct symbolic name for it.
70 * This new value is used to request true Posix O_SYNC semantics. It is
72 * new headers get at least O_DSYNC semantics on older kernels.
|
| /openbmc/linux/Documentation/filesystems/ |
| H A D | virtiofs.rst | 28 guest and host to increase performance and provide semantics that are not
68 Mapping /dev/fuse to virtqueues requires solving differences in semantics
71 prioritize certain requests over others. Virtqueues have queue semantics and
|