| /freebsd/sys/contrib/device-tree/Bindings/interrupt-controller/ |
| H A D | fsl,mu-msi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/fsl,mu-msi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Frank Li <Frank.Li@nxp.com>
16 for one processor (A side) to signal the other processor (B side) using
20 different clocks (from each side of the different peripheral buses).
21 Therefore, the MU must synchronize the accesses from one side to the
23 registers (Processor A-side, Processor B-side).
28 - $ref: /schemas/interrupt-controller/msi-controller.yaml#
[all …]
|
| /freebsd/contrib/llvm-project/llvm/include/llvm/IR/ |
| H A D | FixedPointBuilder.h | 1 //===- llvm/FixedPointBuilder.h - Builder for fixed-point ops ---*- C++ -*-===//
5 // SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 //===----------------------------------------------------------------------===//
9 // This file defines the FixedPointBuilder class, which is used as a convenient
10 // way to lower fixed-point arithmetic operations to LLVM IR.
12 //===----------------------------------------------------------------------===//
55 Value *Zero = Constant::getNullValue(Result->getType()); in Convert()
64 ? B.CreateAShr(Result, SrcScale - DstScale, "downscale") in Convert()
65 : B.CreateLShr(Result, SrcScale - DstScale, "downscale"); in Convert()
74 Result = B.CreateShl(Result, DstScale - SrcScale, "upscale"); in Convert()
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/silvermont/ |
| H A D | virtual-memory.json | 13 "BriefDescription": "Total cycles for all the page walks. (I-side and D-side)",
17 … cycle when a data (D) page walk or instruction (I) page walk is in progress. Since a pagewalk im…
22 "BriefDescription": "Duration of D-side page-walks in core cycles",
26 … when a D-side (walks due to a load) page walk is in progress. Page walk duration divided by numbe…
31 "BriefDescription": "D-side page-walks",
36 …cDescription": "This event counts when a data (D) page walk is completed or started. Since a page…
41 "BriefDescription": "Duration of I-side page-walks in core cycles",
45 …a I-side (walks due to an instruction fetch) page walk is in progress. Page walk duration divided …
50 "BriefDescription": "I-side page-walks",
55 …when an instruction (I) page walk is completed or started. Since a page walk implies a TLB miss, …
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/devfreq/ |
| H A D | rk3399_dmc.txt | 4 - compatible: Must be "rockchip,rk3399-dmc".
5 - devfreq-events: Node to get DDR loading, Refer to
7 rockchip-dfi.txt
8 - clocks: Phandles for clock specified in "clock-names" property
9 - clock-names : The name of clock used by the DFI, must be
11 - operating-points-v2: Refer to Documentation/devicetree/bindings/opp/opp-v2.yaml
13 - center-supply: DMC supply node.
14 - status: Marks the node enabled/disabled.
15 - rockchip,pmu: Phandle to the syscon managing the "PMU general register
19 - interrupts: The CPU interrupt number. The interrupt specifier
[all …]
|
| /freebsd/crypto/openssl/doc/designs/quic-design/ |
| H A D | quic-fc.md | 5 ---------------------------------
8 transmission of stream data could be prevented by connection-level flow control,
9 by stream-level flow control, or both. Flow control uses a credit-based model in
11 bytes allowed to be sent on a stream, or across all streams, since the beginning
14 It is important to note that both connection and stream-level flow control
16 level counts the total number of logical bytes sent on a given stream. Note that
17 this does not count retransmissions; thus, if a byte is sent, lost, and sent
19 that the total number of logical bytes sent on a given stream is equivalent to
32 Connection-level flow control is controlled by the `MAX_DATA` frame;
33 stream-level flow control is controlled by the `MAX_STREAM_DATA` frame.
[all …]
|
| /freebsd/usr.bin/rpcgen/ |
| H A D | rpcgen.1 | 1 .\" Copyright 1985-1993 Sun Microsystems, Inc.
13 .Op Fl a
54 utility is a tool that generates C code to implement an
59 is a language similar to C known as
73 generates a header in
77 server-side stubs in
79 and client-side stubs in
92 that can be customized to suit a particular application.
100 .Fl a
106 then the client side sample file is written to
[all …]
|
| /freebsd/secure/lib/libcrypto/man/man7/ |
| H A D | provider-digest.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "PROVIDER-DIGEST 7ossl"
58 .TH PROVIDER-DIGEST 7ossl 2025-09-30 3.5.4 OpenSSL
64 provider\-digest \- The digest library <\-> provider functions
119 (see "Provider Functions" in \fBprovider\-base\fR\|(7)).
121 All these "functions" have a corresponding function type definition
122 named \fBOSSL_FUNC_{name}_fn\fR, and a helper function to retrieve the
134 macros in \fBopenssl\-core_dispatch.h\fR\|(7), as follows:
156 A digest algorithm implementation may not implement all of these functions.
163 \&\fBOSSL_FUNC_digest_newctx()\fR should create and return a pointer to a provider side
[all …]
|
| H A D | provider-cipher.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "PROVIDER-CIPHER 7ossl"
58 .TH PROVIDER-CIPHER 7ossl 2025-09-30 3.5.4 OpenSSL
64 provider\-cipher \- The cipher library <\-> provider functions
149 (see "Provider Functions" in \fBprovider\-base\fR\|(7)).
151 All these "functions" have a corresponding function type definition
152 named \fBOSSL_FUNC_{name}_fn\fR, and a helper function to retrieve the
164 macros in \fBopenssl\-core_dispatch.h\fR\|(7), as follows:
193 A cipher algorithm implementation may not implement all of these functions.
194 In order to be a consistent set of functions there must at least be a complete
[all …]
|
| H A D | provider-mac.7 | 1 .\" -*- mode: troff; coding: utf-8 -*-
57 .IX Title "PROVIDER-MAC 7ossl"
58 .TH PROVIDER-MAC 7ossl 2025-09-30 3.5.4 OpenSSL
64 provider\-mac \- The mac library <\-> provider functions
112 (see "Provider Functions" in \fBprovider\-base\fR\|(7)).
114 All these "functions" have a corresponding function type definition
115 named \fBOSSL_FUNC_{name}_fn\fR, and a helper function to retrieve the
127 macros in \fBopenssl\-core_dispatch.h\fR\|(7), as follows:
148 A mac algorithm implementation may not implement all of these functions.
149 In order to be a consistent set of functions, at least the following functions
[all …]
|
| /freebsd/contrib/bmake/unit-tests/ |
| H A D | cond-token-var.mk | 1 # $NetBSD: cond-token-var.mk,v 1.14 2025/06/28 22:39:28 rillig Exp $
5 # Note the fine distinction between a variable and an expression.
6 # A variable has a name and a value. To access the value, one writes an
7 # expression of the form ${VAR}. This is a simple
20 # A defined variable may appear on either side of the comparison.
28 # A variable that appears on the left-hand side must be defined.
34 # A variable that appears on the right-hand side must be defined.
40 # A defined variable may appear as an expression of its own.
44 # An undefined variable on its own generates a parse error.
49 # The :U modifier turns an undefined expression into a defined expression.
[all …]
|
| H A D | parse-var.mk | 1 # $NetBSD: parse-var.mk,v 1.10 2024/06/02 15:31:26 rillig Exp $
16 # command-line variable
18 # target-local variable
23 # parse-balanced
25 # eval-defined
26 # eval-keep-undefined
27 # eval-keep-dollar-and-undefined
30 # without -dL
31 # with -dL
45 # for the long forms, EOF after parsing a modifier
[all …]
|
| /freebsd/crypto/openssl/doc/internal/man3/ |
| H A D | ossl_rcu_lock_new.pod | 12 - perform read-copy-update locking
31 OpenSSL can be safely used in multi-threaded applications provided that
32 support for the underlying OS threading API is built-in. Currently, OpenSSL
34 any multi-threading support, for example on platforms that don't provide
35 any threading support or that provide a threading API that is not yet
39 Read-Copy-Update (RCU) locks, which allow for always nonblocking read paths.
41 The following multi-threading functions are provided:
64 ossl_rcu_lock_new() allocates a new RCU lock. The I<num_writers> param
65 indicates the number of write side threads which may execute
67 larger to obtain increased write side throughput at the cost of additional
[all …]
|
| /freebsd/crypto/openssl/doc/man7/ |
| H A D | provider-digest.pod | 5 provider-digest - The digest library E<lt>-E<gt> provider functions
62 (see L<provider-base(7)/Provider Functions>).
64 All these "functions" have a corresponding function type definition
65 named B<OSSL_FUNC_{name}_fn>, and a helper function to retrieve the
75 macros in L<openssl-core_dispatch.h(7)>, as follows:
95 A digest algorithm implementation may not implement all of these functions.
103 OSSL_FUNC_digest_newctx() should create and return a pointer to a provider side
104 structure for holding context information during a digest operation.
105 A pointer to this context will be passed back in a number of the other digest
110 OSSL_FUNC_digest_freectx() is passed a pointer to the provider side digest context in
[all …]
|
| H A D | provider-mac.pod | 5 provider-mac - The mac library E<lt>-E<gt> provider functions
55 (see L<provider-base(7)/Provider Functions>).
57 All these "functions" have a corresponding function type definition
58 named B<OSSL_FUNC_{name}_fn>, and a helper function to retrieve the
68 macros in L<openssl-core_dispatch.h(7)>, as follows:
87 A mac algorithm implementation may not implement all of these functions.
88 In order to be a consistent set of functions, at least the following functions
96 OSSL_FUNC_mac_newctx() should create and return a pointer to a provider side
97 structure for holding context information during a mac operation.
98 A pointer to this context will be passed back in a number of the other mac
[all …]
|
| H A D | provider-cipher.pod | 5 provider-cipher - The cipher library E<lt>-E<gt> provider functions
92 (see L<provider-base(7)/Provider Functions>).
94 All these "functions" have a corresponding function type definition
95 named B<OSSL_FUNC_{name}_fn>, and a helper function to retrieve the
105 macros in L<openssl-core_dispatch.h(7)>, as follows:
132 A cipher algorithm implementation may not implement all of these functions.
133 In order to be a consistent set of functions there must at least be a complete
134 set of "encrypt" functions, or a complete set of "decrypt" functions, or a
135 single "cipher" function. Similarly, there can be a complete set of pipeline
136 "encrypt" functions, and/or a complete set of pipeline "decrypt" functions.
[all …]
|
| /freebsd/share/examples/ppp/ |
| H A D | login-auth | 1 #! /usr/local/bin/wish8.0 -f
17 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
29 # Display a window to request a users password, expecting a login name
47 text .l.prompt -width $pwidth -height 1 -relief flat;
49 pack .l.prompt -side left;
50 .l.prompt configure -state disabled;
51 text .l.value -width $vwidth -height 1;
53 pack .l.value -side right;
54 .l.value configure -state disabled;
55 pack .l -side top -padx $fxpad -pady $fypad;
[all …]
|
| H A D | chap-auth | 1 #! /usr/local/bin/wish8.0 -f
17 # IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
29 # Display a window to request a users CHAP secret, accepting the relevant
50 text .$n.prompt -width $pwidth -height 1 -relief flat;
52 pack .$n.prompt -side left;
53 .$n.prompt configure -state disabled;
60 text .$n.value -width $vwidth -height 1;
62 pack .$n.value -side right;
65 .$n.value configure -state normal -takefocus 0;
68 .$n.value configure -state disabled;
[all …]
|
| /freebsd/contrib/ofed/librdmacm/man/ |
| H A D | rdma_accept.3 | 1 .\" Licensed under the OpenIB.org BSD license (FreeBSD Variant) - See COPYING.md
2 .TH "RDMA_ACCEPT" 3 "2014-05-27" "librdmacm" "Librdmacm Programmer's Manual" librdmacm
4 rdma_accept \- Called to accept a connection request.
18 Called from the listening side to accept a connection or datagram
21 Returns 0 on success, or -1 on error. If an error occurs, errno will be
24 Unlike the socket accept routine, rdma_accept is not called on a
27 events give the user a newly created rdma_cm_id, similar to a new
28 socket, but the rdma_cm_id is bound to a specific RDMA device.
32 by the conn_param parameter when accepting a connection or datagram
43 References a user-controlled data buffer. The contents of the buffer are
[all …]
|
| H A D | rdma_connect.3 | 1 .\" Licensed under the OpenIB.org BSD license (FreeBSD Variant) - See COPYING.md
2 .TH "RDMA_CONNECT" 3 "2010-07-19" "librdmacm" "Librdmacm Programmer's Manual" librdmacm
4 rdma_connect \- Initiate an active connection request.
17 For an rdma_cm_id of type RDMA_PS_TCP, this call initiates a connection request
18 to a remote destination. For an rdma_cm_id of type RDMA_PS_UDP, it initiates
19 a lookup of the remote QP providing the datagram service.
21 Returns 0 on success, or -1 on error. If an error occurs, errno will be
24 Users must have resolved a route to the destination address
32 References a user-controlled data buffer. The contents of the buffer are
33 copied and transparently passed to the remote side as part of the
[all …]
|
| H A D | rdma_get_cm_event.3 | 1 .\" Licensed under the OpenIB.org BSD license (FreeBSD Variant) - See COPYING.md
2 .TH "RDMA_GET_CM_EVENT" 3 "2007-10-31" "librdmacm" "Librdmacm Programmer's Manual" librdmacm
4 rdma_get_cm_event \- Retrieves the next pending communication event.
17 Retrieves a communication event. If no events are pending, by default,
20 Returns 0 on success, or -1 on error. If an error occurs, errno will be
35 RDMA_CM_EVENT_CONNECT_REQUEST, then this references a new id for that
46 is non-zero and is either set to an errno or a transport specific value.
59 References any user-specified data associated with RDMA_CM_EVENT_CONNECT_REQUEST
61 that specified by the remote side when calling rdma_connect or rdma_accept.
67 sent by the remote side. Any additional space in the buffer will be
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/powerpc/power9/ |
| H A D | translation.json | 15 …che was reloaded with Shared (S) data from another core's L2 on the same chip due to a demand load"
20 "BriefDescription": "Double-Precion or Quad-Precision instruction completed"
25 …escription": "A Page Table Entry was loaded into the TLB from another chip's memory on the same No…
35 …A Page Table Entry was loaded into the TLB with Shared (S) data from another chip's L2 or L3 on th…
45 …"BriefDescription": "Finish stall due to a vector fixed point instruction in the execution pipelin…
50 "BriefDescription": "LSU Finished a PPC instruction (up to 4 per cycle)"
60 …A Page Table Entry was loaded into the TLB with Shared (S) data from another chip's L2 or L3 on a …
65 …"BriefDescription": "Completion stall due to a long latency vector fixed point instruction (divisi…
70 …on": "The processor's data cache was reloaded from a location other than the local core's L2 due t…
75 …n": "A Page Table Entry was loaded into the TLB either shared or modified data from another core's…
[all …]
|
| H A D | pipeline.json | 10 "BriefDescription": "Number of I-ERAT reloads"
15 …te that this count is per slice, so if a load spans multiple slices this event will increment mult…
25 …"BriefDescription": "Finish stall because the NTF instruction was a multi-cycle instruction issued…
30 …ded either shared or modified data from another core's L2/L3 on the same chip due to a marked load"
35 …ription": "A Page Table Entry was loaded into the TLB from another chip's L4 on a different Node o…
40 …"BriefDescription": "A Page Table Entry was loaded into the TLB from local core's L2 without confl…
80 …ription": "A Page Table Entry was loaded into the TLB with Modified (M) data from another core's L…
90 …r's data cache was reloaded from another chip's L4 on a different Node or Group (Distant) due to a…
95 …escription": "A Page Table Entry was loaded into the TLB with Modified (M) data from another core'…
100 …rbitration onto the issue pipe to another instruction (from the same thread or a different thread)"
[all …]
|
| /freebsd/sys/contrib/device-tree/Bindings/memory-controllers/ |
| H A D | rockchip,rk3399-dmc.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controller
[all...] |
| /freebsd/share/doc/psd/15.yacc/ |
| H A D | ss4 | 1 .\" Copyright (C) Caldera International Inc. 2001-2002. All rights reserved.
27 .\" WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
39 Yacc turns the specification file into a C program, which
52 of a finite state machine with a stack.
70 A move of the parser is done as follows:
73 whether it needs a lookahead token to decide
89 Whenever a shift action is taken, there is always
90 a lookahead token.
107 the right hand side of a grammar rule,
109 an instance of the rule, replacing the right hand side
[all …]
|
| /freebsd/lib/libpmc/pmu-events/arch/x86/knightslanding/ |
| H A D | virtual-memory.json | 3 "BriefDescription": "Counts the number of load micro-ops retired that cause a DTLB miss",
17 …"PublicDescription": "This event counts every cycle when a data (D) page walk or instruction (I) p…
22 …"BriefDescription": "Counts the total number of core cycles for all the D-side page walks. The cyc…
30 …"BriefDescription": "Counts the total D-side page walks that are completed or started. The page wa…
39 …"BriefDescription": "Counts the total number of core cycles for all the I-side page walks. The cyc…
43 …"PublicDescription": "This event counts every cycle when an I-side (walks due to an instruction fe…
48 "BriefDescription": "Counts the total I-side page walks that are completed.",
57 "BriefDescription": "Counts the total page walks that are completed (I-side and D-side)",
|