Home
last modified time | relevance | path

Searched full:plain (Results 1 – 25 of 431) sorted by relevance

12345678910>>...18

/Linux-v6.6/tools/testing/crypto/chacha20-s390/
Dtest-cipher.c51 static int test_lib_chacha(u8 *revert, u8 *cipher, u8 *plain) in test_lib_chacha() argument
72 chacha_crypt_arch(chacha_state, cipher, plain, data_size, 20); in test_lib_chacha()
126 static int test_skcipher(char *name, u8 *revert, u8 *cipher, u8 *plain) in test_skcipher() argument
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()
248 pr_info("could not allocate plain buffer\n"); in chacha_s390_test_init()
252 memset(plain, 'a', data_size); in chacha_s390_test_init()
253 get_random_bytes(plain, (data_size > 256 ? 256 : data_size)); in chacha_s390_test_init()
[all …]
/Linux-v6.6/lib/
DKconfig.kcsan37 The compiler instruments plain compound read-write operations
39 distinguish them from other plain accesses. This is currently
199 plain accesses by default (depending on !KCSAN_STRICT) reduce the
216 bool "Assume that plain aligned writes up to word size are atomic"
220 Assume that plain aligned writes up to word size are atomic by
223 races due to conflicts where the only plain accesses are aligned
224 writes up to word size: conflicts between marked reads and plain
226 notice that data races between two conflicting plain aligned writes
234 additional filtering. Conflicting marked atomic reads and plain
236 plain reads and marked writes to result in "unknown origin" reports.
[all …]
Dtest_printf.c233 pr_warn("crng possibly not yet initialized. plain 'p' buffer contains \"%s\"", in plain_format()
273 pr_warn("crng possibly not yet initialized. plain 'p' buffer contains \"%s\"", in plain_hash_to_buffer()
302 plain(void) in plain() function
307 pr_warn("skipping plain 'p' tests"); in plain()
314 pr_warn("plain 'p' does not appear to be hashed\n"); in plain()
321 pr_warn("hashing plain 'p' has unexpected format\n"); in plain()
334 * to be called after plain(). in test_hashed()
785 plain(); in test_pointer()
/Linux-v6.6/tools/memory-model/Documentation/
Daccess-marking.txt17 1. Plain C-language accesses (unmarked), for example, "a = b;"
33 Neither plain C-language accesses nor data_race() (#1 and #2 above) place
39 preferable to data_race(), which in turn is usually preferable to plain
44 KCSAN will complain about many types of data races involving plain
54 data_race() and even plain C-language accesses is preferable to
85 concurrently with updates to x. Then using plain C-language writes
95 In theory, plain C-language loads can also be used for this use case.
119 In theory, plain C-language loads can also be used for this use case.
140 In theory, plain C-language loads can also be used for this use case.
156 Plain C-language stores can also be used for this use case. However,
[all …]
Dexplanation.txt33 25. PLAIN ACCESSES AND DATA RACES
933 Plain-coherence: This requires that plain memory accesses
940 "rcu" and "plain-coherence" axioms are specific to the LKMM.
1032 the w-post-bounded relation defined below in the PLAIN ACCESSES AND
2164 PLAIN ACCESSES AND DATA RACES
2171 accesses such as x or y = 0 are simply called "plain" accesses.
2173 Early versions of the LKMM had nothing to say about plain accesses.
2175 by plain accesses are not concurrently read or written by any other
2177 of transformations or optimizations of code containing plain accesses,
2203 But since P0's load from x is a plain access, the compiler may decide
[all …]
/Linux-v6.6/tools/memory-model/
Dlinux-kernel.cat83 let to-w = rwdep | (overwrite & int) | (addr ; [Plain] ; wmb)
173 (* Plain accesses and data races *)
176 (* Warn about plain writes and marked accesses in the same region *)
177 let mixed-accesses = ([Plain & W] ; (po-loc \ barrier) ; [Marked]) |
178 ([Marked] ; (po-loc \ barrier) ; [Plain & W])
186 (* Boundaries for lifetimes of plain accesses *)
194 (* Visibility and executes-before for plain accesses *)
202 let pre-race = ext & ((Plain * M) | ((M \ IW) * Plain))
204 (* Coherence requirements for plain accesses *)
208 empty (wr-incoh | rw-incoh | ww-incoh) as plain-coherence
Dlinux-kernel.bell75 (* Compute marked and plain memory accesses *)
78 let Plain = M \ Marked
80 (* Redefine dependencies to include those carried through plain accesses *)
/Linux-v6.6/drivers/gpu/drm/ci/xfails/
Drockchip-rk3399-fails.txt13 kms_flip@plain-flip-fb-recreate,Fail
14 kms_flip@plain-flip-fb-recreate-interruptible,Fail
15 kms_flip@plain-flip-ts-check,Fail
16 kms_flip@plain-flip-ts-check-interruptible,Fail
/Linux-v6.6/Documentation/dev-tools/
Dkcsan.rst124 * ``CONFIG_KCSAN_ASSUME_PLAIN_WRITES_ATOMIC``: Assume that plain aligned writes
127 causes KCSAN to not report data races due to conflicts where the only plain
192 *plain access*; they *conflict* if both access the same memory location, and at
193 least one is a write. For a more thorough discussion and definition, see `"Plain
196 .. _"Plain Accesses and Data Races" in the LKMM: https://git.kernel.org/pub/scm/linux/kernel/git/to…
253 compiler instrumenting plain accesses. For each instrumented plain access:
264 To detect data races between plain and marked accesses, KCSAN also annotates
276 Each plain memory access for which a watchpoint is set up, is also selected for
312 "prefetch" accesses. Also recall that watchpoints are only set up for plain
/Linux-v6.6/kernel/kcsan/
Dpermissive.h44 * Rules here are only for plain read accesses, so that we still report in kcsan_ignore_data_race()
45 * data races between plain read-write accesses. in kcsan_ignore_data_race()
67 * than 1 bit changed, the plain accesses are safe despite the presence in kcsan_ignore_data_race()
/Linux-v6.6/Documentation/fb/
Ds3fb.rst19 I tested s3fb on Trio64 (plain, V+ and V2/DX) and Virge (plain, VX, DX),
40 hardware, i get best results from plain S3 Trio32 card - about 75 MHz). This
/Linux-v6.6/tools/memory-model/litmus-tests/
Ddep+plain.litmus1 C dep+plain
6 * This litmus test demonstrates that in LKMM, plain accesses
/Linux-v6.6/include/uapi/linux/netfilter/
Dnfnetlink_osf.h94 * plain numeric value. Can also be made as plain numeric value which
/Linux-v6.6/Documentation/devicetree/bindings/pci/
Dfaraday,ftpci100.yaml15 plain and dual PCI. The plain version embeds a cascading interrupt controller
21 The plain variant has 128MiB of non-prefetchable memory space, whereas the
/Linux-v6.6/tools/testing/selftests/bpf/progs/
Dlocal_kptr_stash.c26 struct plain_local __kptr *plain; member
91 res = bpf_kptr_xchg(&mapval->plain, res); in stash_plain()
/Linux-v6.6/Documentation/core-api/
Dprotection-keys.rst75 behavior of a plain mprotect(). For instance if you do this::
98 the plain mprotect() permissions are violated.
/Linux-v6.6/Documentation/process/
Dsecurity-bugs.rst29 Please send plain text emails without attachments where possible.
34 reproduction steps, and follow it with a proposed fix, all in plain text.
Demail-clients.rst24 ``text/plain``. However, attachments are generally frowned upon because
28 It's also strongly recommended that you use plain text in your email body,
333 - Open messages only as plain text! Go to the main window
334 :menuselection:`Main Menu-->View-->Message Body As-->Plain Text`!
/Linux-v6.6/tools/testing/selftests/net/forwarding/
Dtc_mpls_l2vpn.sh11 # | (Plain Ethernet traffic)
43 # | (Plain Ethernet traffic)
/Linux-v6.6/drivers/video/logo/
Dpnmtologo.c142 /* Plain PBM/PGM/PPM */ in read_image()
171 /* Plain PBM */ in read_image()
180 /* Plain PGM */ in read_image()
189 /* Plain PPM */ in read_image()
/Linux-v6.6/drivers/gpu/drm/vc4/
Dvc4_qpu_defines.h67 /* 0-31 are the plain regfile a or b fields */
81 /* 0-31 are the plain regfile a or b fields */
/Linux-v6.6/arch/hexagon/kernel/
Dtrampoline.S17 /* plain sigreturn is gone. */
/Linux-v6.6/net/mac80211/
Dfils_aead.c67 const u8 *plain, size_t plain_len, in aes_siv_encrypt() argument
81 addr[num_elem] = plain; in aes_siv_encrypt()
101 tmp = kmemdup(plain, plain_len, GFP_KERNEL); in aes_siv_encrypt()
/Linux-v6.6/tools/lib/perf/Documentation/
Dmanpage-bold-literal.xsl6 <!-- render literal text as bold (instead of plain or monospace);
/Linux-v6.6/tools/perf/Documentation/
Dmanpage-bold-literal.xsl6 <!-- render literal text as bold (instead of plain or monospace);

12345678910>>...18