Searched full:specifically (Results 1 – 25 of 1166) sorted by relevance
12345678910>>...47
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/elkhartlake/ |
| D | frontend.json | 49 …ack fetches to the exact same cache line or byte chunk count as one. Specifically, the event coun…
57 …ck fetches to the exact same cache line and byte chunk count as one. Specifically, the event coun…
65 …ck fetches to the exact same cache line and byte chunk count as one. Specifically, the event coun…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/snowridgex/ |
| D | frontend.json | 49 …ack fetches to the exact same cache line or byte chunk count as one. Specifically, the event coun…
57 …ck fetches to the exact same cache line and byte chunk count as one. Specifically, the event coun…
65 …ck fetches to the exact same cache line and byte chunk count as one. Specifically, the event coun…
|
| /kernel/linux/linux-6.6/Documentation/arch/arm64/ |
| D | arm-acpi.rst | 190 - DBG2 (DeBuG port table 2), section 5.2.6, specifically Table 5-6.
192 - APMT (Arm Performance Monitoring unit Table), section 5.2.6, specifically Table 5-6.
194 …m Generic diagnostic Dump and Reset Device Interface Table), section 5.2.6, specifically Table 5-6.
197 Table), section 5.2.6, specifically Table 5-6.
201 section 5.2.6, specifically Table 5-6.
204 the IORT (Input Output Remapping Table, section 5.2.6, specifically
228 specifically Table 5-6)
231 specifically Table 5-6)
247 section 5.2.6, specifically Table 5-6.
250 Table), section 5.2.6, specifically Table 5-6.
[all …]
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | frontend.json | 4 …e accesses which hit in a single cache line count as one ICACHE.HIT. Specifically, the event coun…
14 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
24 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | frontend.json | 4 …e accesses which hit in a single cache line count as one ICACHE.HIT. Specifically, the event coun…
16 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
28 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/goldmont/ |
| D | frontend.json | 38 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
46 …e accesses which hit in a single cache line count as one ICACHE.HIT. Specifically, the event coun…
54 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/goldmontplus/ |
| D | frontend.json | 38 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
46 …e accesses which hit in a single cache line count as one ICACHE.HIT. Specifically, the event coun…
54 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
|
| /kernel/linux/linux-6.6/Documentation/driver-api/surface_aggregator/ |
| D | overview.rst | 24 host. On the Surface Book 2, specifically, it additionally provides an
28 restructured for 7th generation devices and on those, specifically Surface
50 communicate via HID, specifically using a HID-over-I2C device, whereas on
|
| D | internal.rst | 73 It, specifically, distinguishes events from request responses, matches
257 Specifically, the packet priority must only be accessed while holding the
275 them, specifically priority and state for tracing. In those cases, proper
451 them, specifically the state for tracing. In those cases, proper access is
470 layer takes on more of a management role. Specifically, it handles device
497 number of request IDs is reserved for use in events only, specifically one
532 for them. Specifically, they will, by default, receive all events from the
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/knightslanding/ |
| D | floating-point.json | 11 … the number of vector SSE, AVX, AVX2, AVX-512 micro-ops retired. More specifically, it counts pack…
19 … the number of scalar SSE, AVX, AVX2, AVX-512 micro-ops retired. More specifically, it counts scal…
|
| /kernel/linux/linux-5.10/tools/perf/pmu-events/arch/x86/tremontx/ |
| D | frontend.json | 4 …accesses which miss in a single cache line count as one ICACHE.MISS. Specifically, the event coun…
16 … multiple fetches to a single cache line count as one ICACHE.ACCESS. Specifically, the event coun…
|
| /kernel/linux/linux-6.6/tools/perf/pmu-events/arch/x86/alderlaken/ |
| D | frontend.json | 14 …ack fetches to the exact same cache line or byte chunk count as one. Specifically, the event coun…
22 …ck fetches to the exact same cache line and byte chunk count as one. Specifically, the event coun…
|
| /kernel/linux/linux-6.6/drivers/platform/surface/ |
| D | Kconfig | 54 Specifically, this driver may be needed for battery status reporting,
140 detachable input peripherals, specifically the keyboard cover (containing
170 some devices, specifically the Surface Book 3, will not be supported.
211 More specifically, this driver provides ACPI platform profile support
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/arm/ |
| D | arm,versatile.yaml | 23 evaluation board specifically for the ARM926EJ-S. It can be connected
30 PCI host controller. Like the sibling board, it is done specifically
|
| /kernel/linux/linux-6.6/Documentation/devicetree/bindings/arm/ |
| D | arm,versatile.yaml | 23 evaluation board specifically for the ARM926EJ-S. It can be connected
30 PCI host controller. Like the sibling board, it is done specifically
|
| /kernel/linux/linux-6.6/drivers/platform/surface/aggregator/ |
| D | Kconfig | 36 only 5th and later generations are currently supported. Specifically,
65 Specifically, exports error injection hooks to be used with the
|
| /kernel/linux/linux-6.6/drivers/scsi/esas2r/ |
| D | esas2r_log.h | 74 * the following macros are provided specifically for debugging and tracing
76 * debugging and tracing events. esas2r_hdebug is provided specifically for
|
| /kernel/linux/linux-5.10/drivers/scsi/esas2r/ |
| D | esas2r_log.h | 74 * the following macros are provided specifically for debugging and tracing
76 * debugging and tracing events. esas2r_hdebug is provided specifically for
|
| /kernel/linux/linux-5.10/Documentation/powerpc/ |
| D | booting.rst | 6 During the development of the Linux/ppc64 kernel, and more specifically, the
26 to define nodes for on chip devices and other buses that don't specifically fit
|
| /kernel/linux/linux-5.10/arch/arm/mach-pxa/ |
| D | mfp-pxa2xx.h | 17 * and adds the below two bits specifically for pxa2xx:
42 /* specifically for enabling wakeup on keypad GPIOs */
|
| /kernel/linux/linux-6.6/arch/arm/mach-pxa/ |
| D | mfp-pxa2xx.h | 17 * and adds the below two bits specifically for pxa2xx:
42 /* specifically for enabling wakeup on keypad GPIOs */
|
| /kernel/linux/linux-6.6/Documentation/powerpc/ |
| D | booting.rst | 6 During the development of the Linux/ppc64 kernel, and more specifically, the
26 to define nodes for on chip devices and other buses that don't specifically fit
|
| /kernel/linux/linux-6.6/include/linux/ |
| D | blk-crypto-profile.h | 82 * specifying the data unit number (DUN). Specifically, the range of
90 * Specifically, the i'th bit of modes_supported[crypto_mode] is set if
|
| /kernel/linux/linux-5.10/drivers/net/wan/lmc/ |
| D | Makefile | 4 # Specifically the 1000,1200,5200,5245
|
| /kernel/linux/linux-6.6/include/drm/ |
| D | drm_utils.h | 4 * Specifically this file is for function prototypes for functions which
|
12345678910>>...47