Searched refs:plain (Results 1 – 19 of 19) sorted by relevance
| /tools/testing/crypto/chacha20-s390/ |
| A D | test-cipher.c | 173 sg_init_one(&sk.sginp, plain, data_size); in test_skcipher()
238 u8 *plain = NULL, *revert = NULL; in chacha_s390_test_init() local
246 plain = vmalloc(data_size); in chacha_s390_test_init()
247 if (!plain) { in chacha_s390_test_init()
252 memset(plain, 'a', data_size); in chacha_s390_test_init()
278 16, 1, plain, in chacha_s390_test_init()
286 if (memcmp(plain, revert, data_size)) { in chacha_s390_test_init()
301 if (memcmp(plain, revert, data_size)) { in chacha_s390_test_init()
323 if (memcmp(plain, revert, data_size)) { in chacha_s390_test_init()
342 if (plain) in chacha_s390_test_init()
[all …]
|
| /tools/memory-model/litmus-tests/ |
| A D | dep+plain.litmus | 1 C dep+plain
6 * This litmus test demonstrates that in LKMM, plain accesses
|
| /tools/memory-model/Documentation/ |
| A D | access-marking.txt | 39 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
45 preferable to data_race(), which in turn is usually preferable to plain
50 KCSAN will complain about many types of data races involving plain
60 data_race() and even plain C-language accesses is preferable to
91 concurrently with updates to x. Then using plain C-language writes
101 In theory, plain C-language loads can also be used for this use case.
125 In theory, plain C-language loads can also be used for this use case.
146 In theory, plain C-language loads can also be used for this use case.
196 by default, refraining from flagging plain C-language stores:
304 should) be plain C-language accesses. One benefit of making them be
[all …]
|
| A D | explanation.txt | 933 Plain-coherence: This requires that plain memory accesses
940 "rcu" and "plain-coherence" axioms are specific to the LKMM.
2238 3. at least one of them is plain,
2400 again, now using plain accesses for buf:
2429 machine instructions the compiler generates for the plain
2452 general. Suppose R is a plain load and we want to show that R
2504 The LKMM includes a second way to pre-bound plain accesses, in
2656 they don't make sense even for plain accesses.
2668 executes before, even if one or both is plain).
2681 Perhaps it could say more (for example, plain accesses might
[all …]
|
| A D | simple.txt | 240 It can be quite tempting to use plain C-language accesses for lockless
|
| A D | ordering.txt | 502 might (and sometimes does) split a plain C-language store into multiple
|
| /tools/testing/selftests/bpf/progs/ |
| A D | local_kptr_stash.c | 53 struct plain_local __kptr *plain; member
146 res = bpf_kptr_xchg(&mapval->plain, res); in stash_plain()
|
| /tools/memory-model/ |
| A D | linux-kernel.cat | 186 (* Warn about plain writes and marked accesses in the same region *)
196 (* Boundaries for lifetimes of plain accesses *)
204 (* Visibility and executes-before for plain accesses *)
214 (* Coherence requirements for plain accesses *)
218 empty (wr-incoh | rw-incoh | ww-incoh) as plain-coherence
|
| A D | linux-kernel.bell | 87 (* Compute marked and plain memory accesses *)
92 (* Redefine dependencies to include those carried through plain accesses *)
|
| /tools/testing/selftests/net/ |
| A D | xfrm_policy.sh | 142 local plain=$5
145 ip -net $ns xfrm policy add dst $plain dir out priority 10 action allow
|
| A D | bind_wildcard.c | 785 TEST_F(bind_wildcard, plain) in TEST_F() argument
|
| /tools/bpf/bpftool/Documentation/ |
| A D | bpftool-prog.rst | 202 print to the standard output (as plain text, or JSON if relevant option was
|
| /tools/power/cpupower/po/ |
| A D | zh_CN.po | 16 "Content-Type: text/plain; charset=UTF-8\n"
|
| A D | ka.po | 17 "Content-Type: text/plain; charset=UTF-8\n"
|
| A D | fr.po | 17 "Content-Type: text/plain; charset=ISO-8859-1\n"
|
| A D | cs.po | 18 "Content-Type: text/plain; charset=UTF-8\n"
|
| A D | it.po | 17 "Content-Type: text/plain; charset=UTF-8\n"
|
| A D | pt.po | 15 "Content-Type: text/plain; charset=UTF-8\n"
|
| A D | de.po | 16 "Content-Type: text/plain; charset=UTF-8\n"
|
Completed in 25 milliseconds