/linux-4.1.27/Documentation/ |
D | cputopology.txt | 2 Export CPU topology info via sysfs. Items (attributes) are similar 5 1) /sys/devices/system/cpu/cpuX/topology/physical_package_id: 11 2) /sys/devices/system/cpu/cpuX/topology/core_id: 17 3) /sys/devices/system/cpu/cpuX/topology/book_id: 23 4) /sys/devices/system/cpu/cpuX/topology/thread_siblings: 28 5) /sys/devices/system/cpu/cpuX/topology/core_siblings: 33 6) /sys/devices/system/cpu/cpuX/topology/book_siblings: 39 drivers/base/topology.c, is to export the 4 or 6 attributes. The two book 43 these macros in include/asm-XXX/topology.h: 54 To be consistent on all architectures, include/linux/topology.h [all …]
|
D | IRQ-domain.txt | 37 other IRQ topology data sources. 166 To support such a hardware topology and make software architecture match
|
D | clk.txt | 55 The members above make up the core of the clk tree topology. The clk 112 Nothing about clock topology or accounting, such as enable_count or
|
D | media-framework.txt | 19 Discovering a device internal topology, and configuring it at runtime, is one
|
D | cpu-hotplug.txt | 97 no locking rules as of now. Typical usage is to init topology during boot,
|
D | 00-INDEX | 137 - documentation on how CPU topology info is exported via sysfs.
|
D | kernel-parameters.txt | 3618 topology= [S390] 3621 topology information if the hardware supports this. 3629 topology updates sent by the hypervisor to this
|
/linux-4.1.27/arch/x86/kernel/ |
D | vsmp_64.c | 179 unsigned int cfg, topology, node_shift, maxcpus; in vsmp_cap_cpus() local 195 topology = readl(address); in vsmp_cap_cpus() 196 node_shift = (topology >> 16) & 0x7; in vsmp_cap_cpus() 200 maxcpus = (topology & ((1 << node_shift) - 1)) + 1; in vsmp_cap_cpus()
|
D | Makefile | 40 obj-y += pci-dma.o quirks.o topology.o kdebugfs.o
|
/linux-4.1.27/Documentation/devicetree/bindings/arm/ |
D | topology.txt | 2 ARM topology binding description 27 ARM topology bindings allow one to associate cpu nodes with hierarchical groups 31 The remainder of this document provides the topology bindings for ARM, based 39 A topology description containing phandles to cpu nodes that are not compliant 46 The ARM CPU topology is defined within the cpu-map node, which is a direct 47 child of the cpus node and provides a container where the actual topology 52 Usage: Optional - On ARM SMP systems provide CPUs topology to the OS. 53 ARM uniprocessor systems do not require a topology 58 subnodes describe the CPU topology. 78 The nodes describing the CPU topology (cluster/core/thread) can only [all …]
|
D | vexpress.txt | 96 Platform topology 100 different setups, the device tree should describe platform topology.
|
D | vexpress-sysreg.txt | 65 topology properties - see main vexpress node documentation for more
|
D | fw-cfg.txt | 31 virtual NUMA topology, and so on.
|
/linux-4.1.27/drivers/parport/ |
D | daisy.c | 44 } *topology = NULL; variable 65 for (p = &topology; *p && (*p)->devnum<devnum; p = &(*p)->next) in add_dev() 180 p = &topology; in parport_daisy_fini() 194 if (!topology) numdevs = 0; in parport_daisy_fini() 215 struct daisydev *p = topology; in parport_open()
|
/linux-4.1.27/Documentation/ABI/testing/ |
D | sysfs-devices-system-cpu | 19 Description: CPU topology files that describe kernel limits related to 70 What: /sys/devices/system/cpu/cpu#/topology/core_id 71 /sys/devices/system/cpu/cpu#/topology/core_siblings 72 /sys/devices/system/cpu/cpu#/topology/core_siblings_list 73 /sys/devices/system/cpu/cpu#/topology/physical_package_id 74 /sys/devices/system/cpu/cpu#/topology/thread_siblings 75 /sys/devices/system/cpu/cpu#/topology/thread_siblings_list 78 Description: CPU topology files that describe a logical CPU's relationship
|
D | sysfs-ata | 6 Provide a place in sysfs for storing the ATA topology of the system. This allows 27 topology, 15 ata_link objects are created.
|
D | sysfs-bus-pci-devices-cciss | 40 drive topology changes.
|
/linux-4.1.27/drivers/firewire/ |
D | Makefile | 6 core-iso.o core-topology.o core-transaction.o
|
/linux-4.1.27/tools/power/cpupower/ |
D | ToDo | 3 - Use bitmask functions to parse CPU topology more robust
|
/linux-4.1.27/arch/avr32/include/asm/ |
D | Kbuild | 20 generic-y += topology.h
|
/linux-4.1.27/arch/metag/kernel/ |
D | Makefile | 24 obj-y += topology.o
|
/linux-4.1.27/drivers/base/ |
D | Makefile | 7 topology.o container.o property.o cacheinfo.o
|
/linux-4.1.27/arch/um/include/asm/ |
D | Kbuild | 27 generic-y += topology.h
|
/linux-4.1.27/arch/cris/include/asm/ |
D | Kbuild | 26 generic-y += topology.h
|
/linux-4.1.27/arch/parisc/include/asm/ |
D | Kbuild | 26 generic-y += topology.h
|
/linux-4.1.27/arch/tile/kernel/ |
D | setup.c | 1180 HV_Topology topology = hv_inquire_topology(); in validate_hv() local 1181 BUG_ON(topology.coord.x != 0 || topology.coord.y != 0); in validate_hv() 1182 if (topology.width != 1 || topology.height != 1) { in validate_hv() 1184 topology.width, topology.height); in validate_hv()
|
/linux-4.1.27/Documentation/devicetree/bindings/mips/img/ |
D | pistachio.txt | 13 A CPU sub-node is also required for at least CPU 0. Since the topology may
|
/linux-4.1.27/arch/xtensa/include/asm/ |
D | Kbuild | 30 generic-y += topology.h
|
/linux-4.1.27/arch/parisc/kernel/ |
D | Makefile | 12 topology.o
|
/linux-4.1.27/tools/perf/util/ |
D | svghelper.c | 693 struct topology { struct 700 static void scan_thread_topology(int *map, struct topology *t, int cpu, int *pos) in scan_thread_topology() argument 717 static void scan_core_topology(int *map, struct topology *t) in scan_core_topology() 760 struct topology t; in svg_build_topology_map()
|
/linux-4.1.27/arch/m68k/include/asm/ |
D | Kbuild | 33 generic-y += topology.h
|
/linux-4.1.27/tools/perf/Documentation/ |
D | perf-timechart.txt | 60 --topology:: 61 Sort CPUs according to topology.
|
D | perf-script.txt | 206 It currently includes: cpu and numa topology of the host system.
|
D | perf-report.txt | 267 It currently includes: cpu and numa topology of the host system.
|
/linux-4.1.27/arch/sh/kernel/ |
D | Makefile | 20 syscalls_$(BITS).o time.o topology.o traps.o \
|
/linux-4.1.27/Documentation/ABI/stable/ |
D | firewire-cdev | 51 during its entire life time. Bus topology changes, and hence 53 need to be aware of topology.
|
/linux-4.1.27/arch/x86/kernel/cpu/ |
D | Makefile | 15 obj-y := intel_cacheinfo.o scattered.o topology.o
|
/linux-4.1.27/arch/s390/kernel/ |
D | Makefile | 42 obj-$(CONFIG_SCHED_BOOK) += topology.o
|
/linux-4.1.27/arch/blackfin/include/asm/ |
D | Kbuild | 43 generic-y += topology.h
|
/linux-4.1.27/arch/arm64/kernel/ |
D | Makefile | 27 arm64-obj-$(CONFIG_SMP) += smp.o smp_spin_table.o topology.o
|
/linux-4.1.27/arch/arc/include/asm/ |
D | Kbuild | 46 generic-y += topology.h
|
/linux-4.1.27/drivers/scsi/bfa/ |
D | bfad_bsg.c | 309 if (iocmd->attr.topology != BFA_PORT_TOPOLOGY_NONE) in bfad_iocmd_port_get_attr() 939 if ((fcport->cfg.topology == BFA_PORT_TOPOLOGY_LOOP) && in bfad_iocmd_ratelim() 940 (fcport->topology == BFA_PORT_TOPOLOGY_LOOP)) in bfad_iocmd_ratelim() 976 if ((fcport->cfg.topology == BFA_PORT_TOPOLOGY_LOOP) && in bfad_iocmd_ratelim_speed() 977 (fcport->topology == BFA_PORT_TOPOLOGY_LOOP)) in bfad_iocmd_ratelim_speed() 2310 if ((fcport->cfg.topology == BFA_PORT_TOPOLOGY_LOOP) || in bfad_iocmd_cfg_trunk() 2311 (fcport->topology == BFA_PORT_TOPOLOGY_LOOP)) in bfad_iocmd_cfg_trunk() 2344 if ((fcport->cfg.topology == BFA_PORT_TOPOLOGY_LOOP) || in bfad_iocmd_trunk_get_attr() 2345 (fcport->topology == BFA_PORT_TOPOLOGY_LOOP)) in bfad_iocmd_trunk_get_attr() 2367 if ((fcport->cfg.topology == BFA_PORT_TOPOLOGY_LOOP) && in bfad_iocmd_qos() [all …]
|
D | bfa_svc.c | 3115 port_cfg->topology = BFA_PORT_TOPOLOGY_P2P; in bfa_fcport_attach() 3191 fcport->topology = pevent->link_state.topology; in bfa_fcport_update_linkinfo() 3193 if (fcport->topology == BFA_PORT_TOPOLOGY_LOOP) { in bfa_fcport_update_linkinfo() 3219 bfa_trc(fcport->bfa, fcport->topology); in bfa_fcport_update_linkinfo() 3226 fcport->topology = BFA_PORT_TOPOLOGY_NONE; in bfa_fcport_reset_linkinfo() 3539 fcport->topology = BFA_PORT_TOPOLOGY_P2P; in bfa_trunk_scn() 3831 if ((fcport->cfg.topology == BFA_PORT_TOPOLOGY_LOOP) && in bfa_fcport_cfg_speed() 3879 bfa_fcport_cfg_topology(struct bfa_s *bfa, enum bfa_port_topology topology) in bfa_fcport_cfg_topology() argument 3883 bfa_trc(bfa, topology); in bfa_fcport_cfg_topology() 3884 bfa_trc(bfa, fcport->cfg.topology); in bfa_fcport_cfg_topology() [all …]
|
D | bfa_defs_svc.h | 949 u8 topology; /* bfa_port_topology */ member 998 enum bfa_port_topology topology; /* current topology */ member 1098 u8 topology; /* P2P/LOOP bfa_port_topology */ member
|
D | bfa_defs.h | 725 u8 topology; /* boot topology setting */ member 736 u8 topology; /* boot topology setting */ member
|
D | bfa_svc.h | 474 enum bfa_port_topology topology; /* current topology */ member
|
/linux-4.1.27/arch/arm64/include/asm/ |
D | Kbuild | 52 generic-y += topology.h
|
/linux-4.1.27/arch/c6x/include/asm/ |
D | Kbuild | 56 generic-y += topology.h
|
/linux-4.1.27/arch/hexagon/include/asm/ |
D | Kbuild | 55 generic-y += topology.h
|
/linux-4.1.27/arch/unicore32/include/asm/ |
D | Kbuild | 58 generic-y += topology.h
|
/linux-4.1.27/arch/nios2/include/asm/ |
D | Kbuild | 58 generic-y += topology.h
|
/linux-4.1.27/Documentation/devicetree/bindings/dma/ |
D | shdma.txt | 5 the same configuration. To describe this topology we require all compatible
|
/linux-4.1.27/arch/openrisc/include/asm/ |
D | Kbuild | 66 generic-y += topology.h
|
/linux-4.1.27/arch/ia64/kernel/ |
D | Makefile | 14 unwind.o mca.o mca_asm.o topology.o dma-mapping.o
|
/linux-4.1.27/Documentation/networking/ |
D | switchdev.txt | 8 Lets describe a topology a bit. Imagine the following example:
|
D | arcnet-hardware.txt | 35 There are two "types" of ARCnet - STAR topology and BUS topology. This 156 The BUS topology is very similar to the one used by Ethernet. The only 186 anywhere in middle of a cable in a STAR topology network. And more - you 217 There are also hubs for the TP topology. There is nothing difficult 426 cable-connector and it's for changing to star or bus topology; 556 the PC120, PC110 and PC100 star topology boards and the PC220, PC210 and 557 PC200 bus topology boards). 707 star or bus topology. 709 it is removed, the board can be used in a bus topology. 934 star or bus topology. [all …]
|
D | batman-adv.txt | 101 sive to topology changes, but will also increase the overhead.
|
D | bonding.txt | 2092 In a topology such as the example above, the active-backup and 2122 In general, however, in a multiple switch topology, the ARP 2239 networking interfaces, the switch, and the topology of the 2242 coalescing), and a "many to many" topology will reorder at a 2260 active-backup: There is not much advantage in this network topology to 2283 mode in this type of network topology. 2286 topology. The 802.3ad mode is an IEEE standard, so all peers 2374 another. One reason to employ a topology such as this is for an 2403 availability. The ARP monitor will function in this topology, but its 2503 largely due to the network topology inside the BladeCenter, detailed [all …]
|
D | cs89x0.txt | 111 topology.
|
/linux-4.1.27/arch/arm/kernel/ |
D | Makefile | 76 obj-$(CONFIG_ARM_CPU_TOPOLOGY) += topology.o
|
/linux-4.1.27/Documentation/devicetree/bindings/phy/ |
D | phy-miphy365x.txt | 17 nodes to describe the controller's topology. These nodes
|
D | phy-miphy28lp.txt | 15 nodes to describe the controller's topology. These nodes
|
/linux-4.1.27/drivers/uwb/ |
D | Kconfig | 15 The topology is peer to peer; however, higher level
|
/linux-4.1.27/arch/mips/kernel/ |
D | Makefile | 9 syscall.o time.o topology.o traps.o unaligned.o watch.o \
|
/linux-4.1.27/drivers/xen/ |
D | Kconfig | 182 PCI topology starts at 00.00.0, or (1) for passthrough if you want 183 the PCI devices topology appear the same as in the host.
|
/linux-4.1.27/Documentation/usb/ |
D | proc_usb_info.txt | 89 in the first 4 columns of each "T:" line (topology info: 90 Lev, Prnt, Port, Cnt) can be used to build a USB topology diagram. 124 | | |__Level in topology for this bus
|
/linux-4.1.27/Documentation/scsi/ |
D | scsi_fc_transport.txt | 230 - The FC topology is not Point-to-Point 350 - If the driver detects the topology is loop, non-fabric, or the 370 for the physical port only (link speed, topology setting, etc). This 430 topology type and existence of the fabric. As this is not applicable to
|
/linux-4.1.27/Documentation/devicetree/bindings/powerpc/fsl/ |
D | pamu.txt | 81 this device is connect. The PAMU topology is represented in
|
/linux-4.1.27/Documentation/scheduler/ |
D | sched-domains.txt | 66 retain the traditional SMT->SMP->NUMA topology (or some subset of that). This
|
/linux-4.1.27/include/drm/ |
D | drm_crtc.h | 1449 char topology[8]); 1451 char topology[8]);
|
/linux-4.1.27/drivers/media/ |
D | Kconfig | 93 topology and configure it dynamically.
|
/linux-4.1.27/Documentation/video4linux/ |
D | fimc.txt | 72 during initialization. The internal device topology can be easily discovered
|
/linux-4.1.27/Documentation/power/powercap/ |
D | powercap.txt | 25 control topology of the system. In that case, it is possible to apply power
|
/linux-4.1.27/tools/perf/ |
D | builtin-timechart.c | 63 topology; member 1519 if (!tchart->topology) in process_header() 1951 OPT_BOOLEAN('t', "topology", &tchart.topology, in cmd_timechart()
|
/linux-4.1.27/drivers/scsi/lpfc/ |
D | lpfc_sli4.h | 190 uint16_t topology; member
|
D | lpfc_mbox.c | 483 LPFC_MBOXQ_t * pmb, uint32_t topology, uint32_t linkspeed) in lpfc_init_link() argument 493 switch (topology) { in lpfc_init_link()
|
D | lpfc_hw.h | 2015 uint32_t topology:8; member 2019 uint32_t topology:8; member
|
D | lpfc_attr.c | 3318 lpfc_param_show(topology) 3319 lpfc_param_init(topology, 0, 0, 6)
|
D | lpfc_init.c | 3943 phba->sli4_hba.link_state.topology, in lpfc_sli4_async_link_evt() 4022 phba->sli4_hba.link_state.topology = in lpfc_sli4_async_fc_evt() 4039 phba->sli4_hba.link_state.topology, in lpfc_sli4_async_fc_evt()
|
/linux-4.1.27/Documentation/vm/ |
D | numa | 100 NUMA topology of the platform--embodied in the "scheduling domains" data
|
/linux-4.1.27/Documentation/sysctl/ |
D | net.txt | 302 If named_timeout is nonzero, failed topology updates will be placed on a defer
|
/linux-4.1.27/Documentation/acpi/ |
D | namespace.txt | 39 data structure called the ACPI namespace whose topology reflects the
|
/linux-4.1.27/drivers/gpu/drm/ |
D | drm_crtc.c | 5588 char topology[8]) in drm_mode_get_tile_group() 5594 if (!memcmp(tg->group_data, topology, 8)) { in drm_mode_get_tile_group() 5618 char topology[8]) in drm_mode_create_tile_group() 5628 memcpy(tg->group_data, topology, 8); in drm_mode_create_tile_group()
|
/linux-4.1.27/drivers/acpi/ |
D | Kconfig | 403 detailed knowledge about platform topology.
|
/linux-4.1.27/arch/arm/ |
D | Kconfig | 1341 bool "Support cpu topology definition" 1345 Support ARM cpu topology definition. The MPIDR register defines 1347 topology of an ARM System.
|
/linux-4.1.27/Documentation/devicetree/ |
D | usage-model.txt | 44 Device Tree to discover the topology of the hardware at runtime, and
|
D | booting-without-of.txt | 1252 system in a form similar to the physical bus topology of the
|
/linux-4.1.27/tools/power/cpupower/po/ |
D | de.po | 103 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | cs.po | 106 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | it.po | 103 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | fr.po | 103 msgid "\t -t: show CPU topology/hierarchy\n"
|
D | pt.po | 101 msgid "\t -t: show CPU topology/hierarchy\n"
|
/linux-4.1.27/Documentation/power/ |
D | devices.txt | 260 The policy is that the device tree should match hardware bus topology.
|
/linux-4.1.27/arch/x86/ |
D | Kconfig | 1330 Enable AMD NUMA node topology detection. You should say Y here if 1342 Enable ACPI SRAT based node topology detection.
|
/linux-4.1.27/lib/ |
D | Kconfig.debug | 587 regions to be regularly checked for invalid topology.
|
/linux-4.1.27/Documentation/virtual/kvm/ |
D | api.txt | 2522 Note that because some registers reflect machine topology, all vcpus
|